On 19 Oct 2005 at 0:30, Johannes Gebauer wrote: > Today I was working on something completely differently, I was editing > a recording. I lost about an hour's work because the software crashed. > Annoying, no doubt, but nothing to get worked up about. It only > happens every once in a while, and as long as I don't completely loose > work that took months to do (which I don't because I have backups) I > live with it. Have to live with it.
Well, when you say that it prompts me to wonder if I've misunderstood the nature of this bug. Is it not the case that this bug can delete data that you *haven't* been editing, in completely different staves than your recent edits have occurred in? In that case, you *could* lose months of work -- all that's necessary is a second forced save after the bug has struck to wipe out both your Finale file and the backup copy. The autosave won't help you if it kicks in *after* the bug has struck. Unless I've completely misunderstood, this bug is not about losing the work since the last save -- it's about corruption of data that could have been created/edited months before and that has not been touched in the current editing session. This is a case of data corruption, of some kind of trashing of the underlying database. My bet is that it's related to the new implementation of temp files maintained in memory instead of on disk. That change is the source of the vast decrease in save time (and in AutoSave interruptions), but it looks like it came at a price in stability. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
