On Oct 20, 2005, at 6:01 PM, Noel Stoutenburg wrote:
3. I have available to me versions of the files in addition to the
files whose names I manually incremented, including every save during
a working session (not just the file as it stood at the end of the
session).
I don't really need _all_ of the versions of the all the files. Two
copies of the final version of each day's work, (one each on each of
two separate physical drives), plus two copies, plus the asv and back
up file haved proved adequate for my use. If I understand your
description of the executive undelete correctly, then besides my
intentional saves, each copy of the ~.asv, ~.bak for each file would
be saved, too. Does this mean, since I might have 30 versions of a
score, each in a separate finale file, executive undelete would save
the each of the ten ~.asv files which get made for each one? I concur
that redundancy is often beneficial, but this seems overkill.
It strikes me that it should be very easy for MakeMusic to program
Finale to create more than one backup, incrementally, to do
automatically what you are doing manually.
For instance, when you hit Save, it of course saves under the same name
in the expected directory, but it ALSO creates a .bak file in a
specified directory with the number 0001 appended to the name. The next
time you hit Save a NEW .bak file is created with 0002 appended, in
addition to the regular save. This gives 10,000 backups before you have
to recycle the names, or change directories.
Maybe 10,000 is too many. 001 would allow 1000 (well, 999 actually),
before requiring you to move the .bak files into a subfolder and
starting over again.
What do you computer-savvy types think of this suggestion?
Christopher
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
