dhbailey wrote:
In Windows, for many years now, the same has been possible but for some reason the good programmers at Finale haven't seen fit to make the two versions identical in that regard.

There is nothing inherent in windows that forces MyMusic.mus, MyMusic.bak, MyMusic.asv -- they could all be MyMusic.mus, MyMusic bak.mus (or MyMusic copy.mus), and MyMusic asv.mus -- that they aren't isn't the fault of Microsoft or of the windows operating system, but rather it's the fault of the programmers at MM who haven't seen fit to take advantage of the filename possibilities in Windows,
Wait a minute.  Let's assume a particular folder has three files:

MyMusic.mus,
MyMusic.bak, and
MyMusic.asv.

Yes, it is possible under currently supported versions of Windows to have a file which appears in some filesystems as

MyMusic bak.mus

However, this is an alias name. If you consult the actual directory entry of the file, or look at properties of the file, and examine the "dos name", you will see that the file name there is shown as

MyMusi~1.mus

If next an ~.asv file is created of the same file, it may have an alias name of

MyMusic asv.mus

but it will have an actual name of

MyMusi~2.mus.

I do remember (perhaps wrongly) that as you get more files with the same first characters, you will eventually get

MyMus~10.mus.

I can't say whether you continuing would generate MyMu~100; the discovery of the above caused me to take positive control of backups. When I begin a new project, I open a new folder with the composition name. The template (if any) for that work has the name 0 (padded to the left to the with as many as I think there may be editing sessions. The work performed in the first editing session is saved as 1 (again padded to the left with zeros, to maintain directory order). The second editing session begins by opening file 1, and immediately resaving it as file 2, where in all of that work is saved. Also, if at any point I decide that I may want to return to a specific point in the workflow, I will do a file save. For example, suppose I am working on a multi-movement work, and have not yet decided whether I want to do each movement as a separate file. In this case, even though it might be in the middle of an editing session, I will save the work, and begin on a new copy, renamed at the beginning to a new number. While ~.asv files will overwrite during each editing session using this method, ~.bak files will not.

ns



_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to