Instant Auto Save
Premiere Pro needs the option to save every keystroke, every edit, every change we make in our project instantly and continuously to the hard drive so that crashes will never again cause lost work.
We are actively working on this feature. I don't have a date to share yet but I'll update this message when I do.
David S commented
I really miss this from Final Cut. A great feature.
Bart N commented
@Trevor nice :-)
FYI: Avid now saves in background (2018.12). It was a loooong time coming.
Bart N commented
The auto save only kicks in when you leave the application "at rest" for a certain amount of time, normally when you edit it will not interrupt you. The "alwasy" in save as FCPX or EVS clean edit is a nice thing on a stand alone, on network systems this is a nightmare and when you add a PAM or MAM system on it it's even worse.
A background would be nice, i know Adobe i looking at this for multiple use, but i think its more easy to ask then to implement.certainly when adding graphics, dynamic linking, MOGRT files into the edit.
Some stuff like render farm, proxy creating on render machine are already done by 3dparty company's.
Bottem line : as in Avid and Adobe i accept that the auto save sometimes takes up a little bit of time. But even big projects where the project file is 500MB and larger it is ok, that mean it need to write a lot of stuff. So for me it's a nice to have.
But what i do like is the reliability of the auto-save to be better and more consequent.
Myer Pjani commented
One thing needs changing, that is saving Warp Stabilizer data into the project. Can't it be a separate file. That would cut down the size in a significant way of the project file if that effect is in use. Otherwise, consider the Prelude doesn't even have a <Save> option (it does have a Save As). So, maybe look at that for some considerations! :-)
Jef Taylor commented
This is 2019, and I find it hard to believe that this feature can't be implemented. It's implemented in FCPX, which generally performs FAR better than PP, so I'm not sure why Adobe can't do the same thing.
It can't be any worse than the current auto-save, which is unreliable at best.
Jim Simon commented
"the instant auto save is not possible for very large projects. and that post is about constantly auto-saving which will slow down project speed all together."
Both Lightworks and DaVinci Resolve have such an Instant Auto Save feature (called by different names). It works brilliantly, even on Hollywood feature film projects, and does NOT slow things down at all.
It's time for Adobe to add this to their entire lineup.
CEDRIC ROBERTSON commented
How can you write info to save while at the same time change the info it is trying to write - save?
BTW FCPX does not have a save or auto save function. It is always in a state of saved.
Kornel Krzemien commented
FCPX does save every single little thing and there is no performance penalty - it can be done then. And honestly if it saves me having to dig trough the non logically named auto save files every time something happens then I don't mind a one percent point of performance penalty, well worth it.
This. YES. Please.
Background auto-save at set intervals (with the ability to continue editing) would be sufficient for me, and solve a major pain point.
That said, an instantaneous save of all operations is a far better goal. The reasoning that it would slow down the application seems problematic given that multiple competing products are doing it, with responsiveness that is often better than Premiere's. Perhaps there are deeper performance problems that need to be rethought if it's currently not possible to support a comparable feature.
Michael Gyori commented
This request, albeit understandable with Premiere's current state, is disturbing.
1) Why should it be necessary to save your project every 5 minutes? Yes, because Premiere crashes so often, but the crashes should be fixed!!!!!, not the ability to edit while saving added.
2) Why is saving in Premiere so slow? Saving should be extremely fast. Save efficiency is terrible right now. How many calculations and data is being parsed in order to save? This needs to change.
Michael Gamböck commented
When you are working on a Team Project there is no autosave and you have unlimited undo´s.
I find PPro to be reasonably stable (not quite as stable as Avid is these days, and nowhere near the Sony 9100 that would go for several years without requiring a reboot) AND when it does crash it generally restores to the position I was at before the crash.
Resolve and FCPx aren't PPros competition in serious Post. Resolve doesn't have the uptake yet (for editing, or audio, or VFX) and FCPx never did get the uptake.
Seems like a nice feature, but I'd rather the resources went elsewhere (i.e. fixing the audio glitches with the dynamics plug-ins, making dynamic plug-ins saveable & catching up with Avid in trimming, slipping, sliding, track selection, keyboard operation, timecode overlays, subtitling)
Avid doesn't save as a background task, sadly. It does have seperate files per bin, rather than one large file for the project, so the save is much quicker, and it has settings for the period of inactivity before auto-saving and then a period for forcing an autosave.
Emilio Luis Roman commented
@Andrew I didn't even think about timeline rendering!
@Blake Alley I hope Adobe lets us know if it is possible and how long it would take to implement.
By and large, Adobe needs to embrace background processes way more. Autosave, rendering, creating proxy jobs, etc... all stop you from working and can take way more time than they should. Speed things up and let me work while they're doing it.
Blake Alley commented
I agree that auto-save should be a background operation. If that isn't possible, at least allow it to monitor what a user is doing and wait till there's nothing happening to auto-save!
Emilio Luis Roman commented
@Dmitry Larionov I couldn't agree more.
@Jim Simon that's not the same thing, the instant auto save is not possible for very large projects. and that post is about constantly auto-saving which will slow down project speed all together. I want them to make a side loaded program that runs independently so that even when PPR crashes you still have an opportunity to save. and when it auto saves the program doesn't force you to wait for PPR to finish saving.
@Steven hopefully they will fix this in the next next update.