Hi all,
I wonder if anyone is finding the autosaves are taking longer than they should. I’m on a simple job at the moment that comprises of about 10 shots on a timeline, all have an Image grade and a few action repos.
My autosave are taking 15seconds. and it’s most frustrating when doing client sessions.
With superfast SSD internal storage I expect a blink of the eye autosaves.
How many desktops do you have open? Same question with open libraries? If there are a lot of open elements, autosave can take forever.
This is just something we have dealt with for many years. We have huge batches and libraries, and some of our Autosaves can be minutes long.
Oh my god. Please someone tell me the secret to reducing this.
I always thought it was because I use action on the timeline to resize shots because we use BLGs all the time.
ummm…
biting my lip here…
I have 1 library open, no batches, about 3 reels with a about 100 source clips within, 4 timelines with about 6 layers in each (mostly supers)
I’ve changed the autosave times to 15 mins but it still does a hard save sooner than that when I touch an image or action.
What’s going on under the hood that’s taking so long when it saves.
get it out… what is your opinion on this Phil?
Do smaller projects
On linux
In the cloud
Overseas
With cloud storage
Yup… I’ll tell my client I can’t accomodate more than 20 shots, and he should send the rest to India. I like that business plan.
How would that help this issue?
Which is slower than John’s local storage.
The autosaves currently would be going to your OS drive, not your framestore. So unless that is an NVMe drive, it might not be as superfast as you think.
OS System disk on a brand new Mac is very fast, but may not cope well with many hundreds of small files with small block sizes.
John,
You can delete all the iterations stored within the Batch reel to clear up a bunch of hidden clips which may be contributing to long save times… You have to right click and show iterations to see them. If you’re cautious you can leave 1-3 iterations if you think you need to roll back.
But I do this usually at end of a job to make my archives really small and I even wrote a script that deletes iterations and unlinks every possible media. We usually soft link every element for a comp but sources invariably cache or you need to pre-render something.
Another way to speed up saves is to Close all the libraries that you don’t actively need. Flame will save the state of any open libraries.
Another thing you can do but it’s risky…When I know I have a client session and can’t afford for long saves, I will turn off Autosave by setting all the durations to 0. It’s a risk, but if you know it’s a show and tell kind of session and do “manual” batch setup saves, then you can avoid the embarrassing pauses. After session is done, remember to turn it back otherwise it will screw you later when you crash.