Long auto save are expected if you have a lot of content like many iterations of Batch Groups with lot of nodes but for small projects it should not be the case. If I were you I would open a ticket with our Support team so they could collect information about your content.
1 Like
Guys guys guys. I have NO batch groups or iterations in bfx. You would all laugh at how simple this timeline is. I can’t screenshot it until the next release but its really simple. My internal 8TB SSD @ 6000MB/s is my flame storage. I often see it “saving Action” or “saving Image”
These Autosaves take at least 15 seconds. I know you think that’s not long but when you are in a client session doing on the fly changes and the auto save kicks in every 2 minutes, well it’s very annoying.
John, we will follow up off line to better understand the issue on your system.
I think the key variable is the size of the file. Batch or BFX are frequent indications because of the node trees. But a timeline with 100+ clips each with an image effect would fall into the same category.
Ultimately, what you have to look at is, how big is the file? I think they’re stored in the /projects folder, aren’t they?
I have 100+ clips in a source reel. About 10 clips in the timeline.
BFX trees are no more that 10 nodes.
You can try other strategy: Keep source clips in other library. I store all my source clips (tk, camera, renders, whatever,) in separate folders in a separate library. I don’t need at all source clips in desktops. In my desktops I keep only timelines. I can drag and drop any clip at any time. Furthermore, you can close unused libraries. All saves become faster.
1 Like
or disable protect from editing, conform on a desktop, shunt that desktop into a library, work out of the library.