[Finale] autosave
Mac - Finale 2010 - I can't find autosave (by any name) in the menu bars. Recently lost 4 hours of work when I neglected to save manually. Dumb dumb dumb! That said, I'll probably do it again when I get too involved. Need autosave, which I used to use all the time on big scores. Help! and thanks in advance. Linda Worsley ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] autosave
It's in program options, I think. On Jun 24, 2012, at 8:56 AM, Linda Worsley li...@ganymuse.com wrote: Mac - Finale 2010 - I can't find autosave (by any name) in the menu bars. Recently lost 4 hours of work when I neglected to save manually. Dumb dumb dumb! That said, I'll probably do it again when I get too involved. Need autosave, which I used to use all the time on big scores. Help! and thanks in advance. Linda Worsley ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] autosave
Yes. Preferences/Program options/Save and Print Harold On 24/06/2012, at 13:05, Ryan Beard wrote: It's in program options, I think. On Jun 24, 2012, at 8:56 AM, Linda Worsley li...@ganymuse.com wrote: Mac - Finale 2010 - I can't find autosave (by any name) in the menu bars. Recently lost 4 hours of work when I neglected to save manually. Dumb dumb dumb! That said, I'll probably do it again when I get too involved. Need autosave, which I used to use all the time on big scores. Help! and thanks in advance. Linda Worsley ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] autosave
Right you are. Thanks! Lw ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
On 7 Oct 2005 at 15:39, Carl Donsbach wrote: --On Friday, October 07, 2005 3:49 PM -0400 David W. Fenton [EMAIL PROTECTED] wrote: On 7 Oct 2005 at 13:31, Carl Donsbach wrote: The problem I have with autosave is that it is a substitute for a good habit. When I look at my undelete program's list of available file versions to recover, I have more BAK and MUS versions than ASV versions. That means I'm manually saving more often than the Autosave. So, I have good habits. Sorry, David, I hope that's not how you read me - I never said or meant to imply that you didn't have good habits. My observation is about the software, the way it is marketed, and the way too many people use it. I didn't think you were criticizing me at all. I was just saying that I think Autosave is a good thing even when you *do* have what you call good habits precisely because the backup systems we rely on to save ourselves from problems often fail together. While I Ctrl-S all the time, I'm glad that the Autosave file is there in the event that I might sometime need it. -- David W. Fentonhttp://www.bway.net/~dfenton David Fenton Associateshttp://www.bway.net/~dfassoc ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
dc wrote: David W. Fenton écrit: Now, it's possible that these things have been changed in newer versions of Finale. If so, I'd like to know. Well, I Autosave every 1 minute in Fin2004, and it's never bothered me. But then, I don't do Wagner. I turn autosave off in every application I use, preferring instead to hit ctrl-s quite often in my own autosave mode. That way I know the program won't be in the middle of doing something important when the file gets saved, and I can be sure that a step I am in the middle of is completed. I have run into too many problems over the years with autosave messing things up because it takes over whenever it is scheduled to run, regardless of what other processes may be running. -- David H. Bailey [EMAIL PROTECTED] ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
--On Friday, October 07, 2005 6:26 AM -0400 dhbailey [EMAIL PROTECTED] wrote: dc wrote: David W. Fenton écrit: Now, it's possible that these things have been changed in newer versions of Finale. If so, I'd like to know. Well, I Autosave every 1 minute in Fin2004, and it's never bothered me. But then, I don't do Wagner. I turn autosave off in every application I use, preferring instead to hit ctrl-s quite often in my own autosave mode. That way I know the program won't be in the middle of doing something important when the file gets saved, and I can be sure that a step I am in the middle of is completed. I have run into too many problems over the years with autosave messing things up because it takes over whenever it is scheduled to run, regardless of what other processes may be running. I never use it either. The problem I have with autosave is that it is a substitute for a good habit. -Carl Donsbach ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
On 7 Oct 2005 at 9:36, dc wrote: David W. Fenton écrit: Now, it's possible that these things have been changed in newer versions of Finale. If so, I'd like to know. Well, I Autosave every 1 minute in Fin2004, and it's never bothered me. But then, I don't do Wagner. It didn't become much an issue for me until I started combining my individual movement files into a single file. Three files of 368, 139 and 586 measures combined were not individually a problem. But when I started combining files like that into a single file, the Autosave became quite obtrusive. Now, certainly, my machine is old and slow compared to today's new PCs (though it never has really felt that way to me in any other program, and mostly doesn't in Finale, either, which has always seemed to me to be pretty efficiently designed from a performance standpoint), but I'm just comparing the way Finale works to all other programs I've ever used. No other program I have with Autosave interrupts user actions to save. I'm not sure if any of them reset the clock after a manual save, because their Autosave is unobtrusive enough that I don't notice. If I were working with smaller files it would certainly be less of a problem, but I still think kicking in while I'm pulling down a menu is not good design, even if it is only a short interval. -- David W. Fentonhttp://www.bway.net/~dfenton David Fenton Associateshttp://www.bway.net/~dfassoc ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
On 7 Oct 2005 at 6:26, dhbailey wrote: I have run into too many problems over the years with autosave messing things up because it takes over whenever it is scheduled to run, regardless of what other processes may be running. Would my feature suggestions address your problems with Autosave? Seems to me that it would, but I can't know how others are likely to feel about it. I started using Autosave in Finale when I had bad problems with Finale crashing. I was working with a couple of files that whenever a certain measure became the leftmost frame in scroll view, Finale would just crash. After much investigation, I concluded it was a video driver issue and since there were no alternate or newer drivers for my system, I just gave up and lived with it. I can't say that I've used the Autosave file more than a couple of times ever, but it is definitely a layer of protection that I am glad to have. Of course, I also depend on the protected recycle bin that I installed after losing some data because of a mistaken file delete. I use a program called Executive Software Undelete, which manages the recycle bin, but more importantly, takes control of the free chain, so that deleted files stay unaltered as long as possible (the free chain is the file system's list of sectors that are open for writing to; Microsoft's normal free chain is pretty random, not the last-in, last-out you'd expect, and this program makes sure that it's LILO). Using this undelete software, I recently recovered a file that I had screwed up that I hadn't edited in nearly 6 months. I was able to revert to the last version before I started my current erroneous edits because I had a choice of ever version of the file going back almost as long as the file had existed. That include ASV and BAK files, as well, along with the original MUS files. So, I could probably turn off Autosave, like David Bailey, and be OK, as the video driver problem trained me to save, save, save, save, save after almost any significant operation. Nonetheless, I still like having Autosave as another layer of protection, because my experience with backups of all kinds is that you never lose data when just one backup layer fails -- it's always when muliple systems fail that you lose the data, and that happens a lot more often than we'd like to believe. I just wish the Finale Autosave were more intelligent. If you agree with me, send in your feature request to MakeMusic. -- David W. Fentonhttp://www.bway.net/~dfenton David Fenton Associateshttp://www.bway.net/~dfassoc ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
On 7 Oct 2005 at 13:31, Carl Donsbach wrote: The problem I have with autosave is that it is a substitute for a good habit. When I look at my undelete program's list of available file versions to recover, I have more BAK and MUS versions than ASV versions. That means I'm manually saving more often than the Autosave. So, I have good habits. Why not turn off Autosave, then, and lose the annoyance of it kicking in? Because Autosave could possibly kick in at just the right time, after I've manually saved and before a crash that loses data. Also, as I said in another message, as with all backup systems, it is hardly ever the case that anyone loses data when just one of them fails. It almost always takes the failure of multiple redundant backups before you lose data. Also, with the Autosave file, you've got one more chance to get the data back. It may be useless most of the time (I've not recovered an ASV file more than a couple of times in all my years of using Finale), but it's that one time when it *wouldn't* be useless that it's there for. -- David W. Fentonhttp://www.bway.net/~dfenton David Fenton Associateshttp://www.bway.net/~dfassoc ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
--On Friday, October 07, 2005 3:49 PM -0400 David W. Fenton [EMAIL PROTECTED] wrote: On 7 Oct 2005 at 13:31, Carl Donsbach wrote: The problem I have with autosave is that it is a substitute for a good habit. When I look at my undelete program's list of available file versions to recover, I have more BAK and MUS versions than ASV versions. That means I'm manually saving more often than the Autosave. So, I have good habits. Sorry, David, I hope that's not how you read me - I never said or meant to imply that you didn't have good habits. My observation is about the software, the way it is marketed, and the way too many people use it. -Carl ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
[Finale] Autosave
One thing that can't be determined well from a demo version of Finale is how Autosave settings have been changed. I use WinFin2K3 and am constantly annoyed at how stupid Autosave is. Here are some changes I'd like to see to the way Autosave behaves: 1. always, always, always wait for idle time before saving. This means that if I'm in the middle of choosing something from a menu DON'T FREEZE FINALE WHILE THE FILE SAVES -- wait until I've made my choics, for the first point that the mouse button is not down, a menu is not active and there are no keyboard input for a certain reasonably chosen interval. 2. reset the Autosave clock after a forced save. This means that if I hit Ctrl-S and the Autosave interval is 10 minutes, Autosave should not kick in 1 minute after I've saved just because the last Autosave was 9 minutes before I saved my file. 3. perhaps, make these things user configurable. I can't see why anyone would want to be interrupted by 1), but I can understand why some would feel comfortable with Autosave on its own clock, independent of user-initiated save operations. Now, it's possible that these things have been changed in newer versions of Finale. If so, I'd like to know. Otherwise, I'll be sending in a feature request, and would suggest that others do likewise. -- David W. Fentonhttp://www.bway.net/~dfenton David Fenton Associateshttp://www.bway.net/~dfassoc ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
Re: [Finale] Autosave
David, It's much quicker now in 2006, but it can still interrupt a process (mass edit, for instance), and when it does, there's a chance that it may crash the program. I haven't been able to determine what causes this, but I have experienced crashes during times that use a lot of processing power (the middle of a GPO playback, for instance), and I think it may be that Autosave is kicking in at that moment. I repeat, I'm not sure. Sometimes people who are more computer savvy than I are able to determine causes of problems that I cannot. Otherwise, it is better now - mainly because it's so quick, but everything you say is logical, and I agree with it. It just hadn't occurred to me that making such adjustments in the way things work might be possible. I am surprised by these occasional crashes, because 2005 was pretty crash free for me. Chuck On Oct 6, 2005, at 1:44 PM, David W. Fenton wrote: One thing that can't be determined well from a demo version of Finale is how Autosave settings have been changed. I use WinFin2K3 and am constantly annoyed at how stupid Autosave is. Here are some changes I'd like to see to the way Autosave behaves: 1. always, always, always wait for idle time before saving. This means that if I'm in the middle of choosing something from a menu DON'T FREEZE FINALE WHILE THE FILE SAVES -- wait until I've made my choics, for the first point that the mouse button is not down, a menu is not active and there are no keyboard input for a certain reasonably chosen interval. 2. reset the Autosave clock after a forced save. This means that if I hit Ctrl-S and the Autosave interval is 10 minutes, Autosave should not kick in 1 minute after I've saved just because the last Autosave was 9 minutes before I saved my file. 3. perhaps, make these things user configurable. I can't see why anyone would want to be interrupted by 1), but I can understand why some would feel comfortable with Autosave on its own clock, independent of user-initiated save operations. Now, it's possible that these things have been changed in newer versions of Finale. If so, I'd like to know. Otherwise, I'll be sending in a feature request, and would suggest that others do likewise. -- David W. Fentonhttp://www.bway.net/~dfenton David Fenton Associateshttp://www.bway.net/~dfassoc ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale Chuck Israels 230 North Garden Terrace Bellingham, WA 98225-5836 phone (360) 671-3402 fax (360) 676-6055 www.chuckisraels.com ___ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
