Truly saving a project so you don't lose it
by Jeff Gerst
on
Nov 6, 2009 at 10:34:39 pm
I save projects as I work on them after pretty much every edit or 2 I do. Every once in a while the program freezes or crashes. When it does & I have to force quit, I find my latest saved version can be 15 or 30 mins prior.
I changed the autosave to 5 mins, but is there any way to ensure when I ask the project to save that it really does save it so I don't lose the progress I've made no matter what happens?
For some reason, a crash or force quit seems to wipe out the last several saves I've made as well.
Re: Truly saving a project so you don't lose it by Michael Gissing on Nov 6, 2009 at 10:40:57 pm
The auto saves do not overwrite the main project file but go into the autosave folder as specified in your scratch drive setup. In there you will find the most up to date autosave which you can open and then save over the older project file or save as if you want to be cautious.
Re: Truly saving a project so you don't lose it by Jeff Gerst on Nov 6, 2009 at 10:50:23 pm
Thx - I've been using autosaves but they were set to 30 min intervals - I changed to 5 mins.
I still don't understand why when I save the project manually with command-S that it doesn't keep that manual save of the project. If FCP crashes, I seem to lose most of my recent manual saves & have to go back to the last autosave, sometimes 30 mins (& a lot of tough keyframing, etc) ago.
Is there any way to make the manual "hard save" actually save in the event of a crash? Maybe "save all" instead of "save"?
Re: Truly saving a project so you don't lose it by Joey Burnham on Nov 6, 2009 at 11:36:09 pm
Doesn't make sense that if you are saving the project it doesn't update.
Anyways, you can change you keyboard shortcut for command+S to be Save All if you want. It's what I did but only because I hated being asked if I wanted to save all my projects when I go to quit.
Re: Truly saving a project so you don't lose it by chris gorman on Nov 7, 2009 at 5:39:14 am
Although this doesn't answer your specific question, it's a suggestion for additional safety when backing up a project. I keep a minimized window of a folder on a different drive with backups of fcp projects.
While editing I navigate to the minimized view of two folders: one is my working edit drive with the project, the other is a folder on another drive. I simply Option drag (copy) the project to the other drive.
This window arrangement lets me do it quickly and easily at brief intervals. If my project gets corrupted or the drive fails, i have a good recent project backed up on the other drive.
Makes no sense that your project is not saving when you do "save". Ya think your scratch disk got changed and you didn't notice?
PowerPC G5 DP2.3, 4GB DDR SDRAM, ATI X800XT, OSX.4.11, QT 7.5.5, FCStudio2, FCP 6.0.5 Sonnet 5 Bay SATA (RAID or JBOD as needed), ACD 23" & Sony NTSC Monitor via Matrox v.1
Sony ZIU hdv, edit w.ProRes
Re: Truly saving a project so you don't lose it by Jeff Gerst on Nov 7, 2009 at 6:50:34 am
Thx for the last 2 tips - will implement s/thing - now that I have autosave on every 5 mins & using some of your tips I think I'll at least have a better protection against losing a lot of good work.
Anytime I render anything I save right after - I'll just add your suggestions in & I should be ok.
