-
Backup
-
[Kevin Patrick] “Why? Why go to the trouble of having a backup feature, but only one backup? As you say, what if you wind up with a backup of your corrupted project?”
Why, would be the $64K question for Apple. How can this possibly be seen as the “next generation” of backup?
It’s like an addiction to new and simplified that defies logic as part of it’s march towards newer and simpler.Incremental save files have obvious and enormous value in dire times – it’s proven – it works.
Replacing it with a 15 minute destructive autosave that ISN’T available to the user (everything must be hidden to be simple) can’t possibly be seen as an improvement if you understand what a backup is for.
We had two projects fail and many $Ks of hours that had to be redone because there was no incremental backup.
It won’t happen again because we duplicate regularly and we’re super aware of corruption and it’s potential.If you’ve written a perfect program that removes this need then you’re truly visionary. But seeing as though the new FCP has corruption issues like no version in a decade, a simple autosave function looks pretty smart.
-
I totally agree Jim, it does feel like a very backward step. My old Fast 601/Silver had a ‘save all the time’ feature – I remember seeing a demo where, in the middle of editing, the guy pulled the plug out of the workstation. Five minutes later, booted up he was back to exactly the point when the plug got pulled. I never lost a thing editing on the Fast. We’ve not come a long way since. Apple should have given the option for added flexibility in where and when Autosave does it’s thing, it’s too much to assume everyone has a Time Machine drive attached.
Hence my reasoning for going old school in terms of backups – its a reflex action born of paranoia from years of experiencing crashes from all sorts of NLEs on all platforms. I’d say that FCP7 was the most stable of all NLEs I’ve used in terms of corruption and crashing, and prior to 10.0.4, X took me right back to the bad old days of regular crashing and potential data loss. Kind of like a bad flashback, only this time it was Media Composer circa 1996 ish rather than the jungles of ‘Nam. I have to say it’s better now though, and I hope Apple are making rock solid stability a priority.
_________________________________
Before you criticise a man, walk a mile in his shoes.
Then when you do criticise him, you’ll be a mile away. And have his shoes.*the artist formally known as Jaymags*
-
[Jason Porthouse] “prior to 10.0.4, X took me right back to the bad old days of regular crashing and potential data loss.”
We’ve been too swamped to update systems and the discussion as to whether Magic Bullet suffered in the update has also kept from going 1.0.4 but is sounds like it’s a real stability improvement.
I still think that carefully managing project size is the single contributing factor to lack of corruption.
But even Apple admitted to me that imported graphics (as of 1.0.3) were a bit of a wild card. -
I was hoping I was missing something.
One continuous over writing backup? So if my project gets corrupted and I don’t realize it in the 15 minute widow, I now have a duplicate of my corrupted project? I would like to understand the logic behind this.
I guess I’ll stick to my duplicate projects process.
-
[Kevin Patrick] “One continuous over writing backup? So if my project gets corrupted and I don’t realize it in the 15 minute widow, I now have a duplicate of my corrupted project? I would like to understand the logic behind this. “
Don’t try and understand something that’s not there (logic) but yes, that was the “solution” in 1.0.3 to the problem they created in 1.0.
There’s one backup every 15 minutes that overwrites the previous. But remember, even that backup is meaningless unless you actually have a project corruption that won’t allow you to open the project – which is rarely the case I’m sure. Most corruption happens and grows while the project is available, so by the time it was unopenable, yes, the backup would be corrupt as well, in most circumstances.
It’s simply stupid.
Which I suppose fits with Apple’s new obsession with simplicity.
-
[Kevin Patrick] “I guess I’ll stick to my duplicate projects process.”
I will keep backing up also.
I thought it was interesting to watch though. It wasn’t theory, he opened up the file and destroyed it.
Then he recovered the file.
I’m tempted to try it with a test file.
Either way I feel a little better about it now. If I’m backing up and it’s backing up I like my odds a little better.
-
[Jim Giberti] “It is crazy not to have it, and the 15 minute, hidden autosave is unfathomably misconceived.
TimeMachine is the only reliable autosave you have.
Why?
“
Who knows?! OVer the years, being able to go back 3,4,5, maybe 6 autosaves to a version of the project that wasn’t corrupted wasn’t often essential, but when it was essential–a couple of times a year–it was ESSENTIAL.
Reply to this Discussion! Login or Sign Up