Hey Allen & co,
One more thing:
I noticed a *drastic* performance improvement when I quit and restart Finale compared to what I was getting during the session where the File Overwrite bug hit, despite having exactly the same set of files open as I did before. Redraws were easily twice as fast.
Could there be a problem not only with the File Overwrite bug, but with the Finale Temp Files getting bloated/corrupted over the course of an extended Finale session, causing performance degradation AND problems such as the File Overwrite bug?
Please let me once again repeat my request to do away with temp files and instead have Finale store that information in RAM -- at least as an option. (We used to be able to do that in OS 9 with a RAM Disk, but RAM disks aren't effective in OS X.)
It seems like many of the stability and corruption problems in Finale have to do with the way it handles temp files, which are a bit of an anachronism in any case. Perhaps some of these problems could be solved by using RAM instead of disk space?
- Darcy ----- [EMAIL PROTECTED] Brooklyn, NY
On 19 Jan 2005, at 08:07 AM, Darcy James Argue wrote:
Damn -- I thought I had dodged the problem, but I got bit by it anyway -- on a different file!
Here's the MacSupport note:
Hi Allen & co.,
Just an update -- when I noticed the printing problem with the last file, I tried opening a second instance of the file (without quitting Finale), which fixed the problem. However, I continued to work without quitting Finale, until just a moment ago, when it abruptly became impossible to select anything with any tool.
I went through each file one by one and manually saved it and closed it. Then I quit Finale. When I relaunched Finale, the file I had been working on when the problem with selecting things occurred had been replaced with different content. I have attached it here:
[attachment deleted]
It was originally a chorus part with piano reduction, but it's been replaced with the content of the Harp part for this piece. I don't know if you can glean anything from this file, but take a look and see if it tells you anything.
For comparison purposes, here is the most recent auto-saved version of the same file:
[attachment deleted]
Let me know if I can give you any other info that might help pin this down.
Cheers,
- Darcy ----- [EMAIL PROTECTED] Brooklyn, NY
CC: of message I sent to Allen and MacSupport, minus the attached files:
Hi Allen, guys,
Allen, I know you're going to NAMM but hopefully you get a chance to look at this when you get back.
I think I may have an instance of the File Overwrite bug in action. This is in Fin2005a. I have 22 documents open. The frontmost document -- "08 The Gallows 2005.mus" -- is *displaying* the *content* of that file (a score), but when I go to print, the file that actually prints is a different (also currently open) file -- "WitCan - 002 Percussion 2005.mus" ( a part). I have confirmed this printing error twice.
I am sending you both files in their current states. When you open "08 The Gallows 2005.mus," does it look like a score, or a part? When you print it, does the printout match the screen contents, or does it print a percussion part instead?
UPDATE: when I open a second instance of the part, it prints correctly. I'm going to save the problematic instance under a different name and see what happens.
- Darcy ----- [EMAIL PROTECTED] Brooklyn, NY
_______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
_______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
