Autosave issues and Premiere pro is not very pro –rant

[Gary Bingner]

Andreas, I feel your pain.

I just switched to Premiere Pro from Final Cut about a month ago. I was used to Autosave being there on FC7 to save my bacon in those rare instances of a crash.

Tonight, I had my second big crash and it was a whopper. Even though I thought I was saving occasionally, none of my saves worked…and neither did autosave. I LOST FIVE HOURS OF INTENSE EDITING.

I’m not going to ask for advice. This is my first post and I’m already struck by the high level of snark that has been coming your way. But suffice it to say, Premiere Pro broke my heart tonight. I’m guessing the spinning beach ball of death has something to do with my iMac not being robust enough. But the fact that I had NO Auto Save files for over FIVE HOURS is very confusing to me.

Good luck figuring it out. I have to spend the night redoing a project I was about to finish. I may be shopping for a newer Mac this weekend.

[Andreas Ahston]

I know how that feels. Thanks for your comment. I miss the old final cut too.

[Ryan Patch]

Andreas –

I am seeing this AutoSave problem as well. Don’t let the haters get you down. Although it’s our responsibility to save consistently, and although you shouldn’t be crashing consistently, the AutoSave should work.

Please report the AutoSave issue to Adobe on the bug form so they can get it fixed.

R

[Matthias Noe]

It’s been this way since a couple of versions and Adobe doesn’t seem to bother. And there are a couple of instances that can occur where the editor is not really to blame: e.g. when he is relatively new to the job and so caught up in the tunnel that 1 hour passes like 5 minutes, or when even the work of 5 minutes is hard to rebuild sometimes. It’s just a frustrating experience and it’s totally avoidable if the software did what it promises to do. Period.
I just had the case that I had two sequences named the same in my project(I had re-imported another cut that I had saved seperately) and all of a sudden, the one I was working on just turned into the older one with the same name. So abruptly I had two identical sequences with the status from 2 days ago and no undo could bring back my work. And OF COURSE the most recent Autosave (every 10 minutes is my setup) is an hour old. A freaking hour! And there was nothing I could do. Yes, I could force the habbit to save every 5 minutes but isn’t that something that Adobe clearly can and simply should automate for us editors? They even claim to do so but from version CS3 or so on this bug is like a huge middle finger to everyone who foolishly thinks that the promised auto save works. It just should work. Period.

MY SYSTEM:
OS: Windows 7 | 64Bit | Ultimate
Motherboard: Asus | P8P67 DELUXE
Processor: Intel | Core i7-2600K 3400 1155
GPU: ASUS | GeForce GTX760 | 2 GB
RAM: G.Skill | Ripjaws 16GB 1333-999 | 4x4GB
System-Drive: ADATA | Internal SSD, 128GB | ASP900S3-128GM-C | Sata
Monitor: Eizo | 23 L FS2331-BK