Well, we've done quite a few short form projects (spots) via TeamProjects with great success.
So we decided to take on some longer projects (30 min)...here's an update.
At the start it all runs pretty smooth, but once you get a 30 min sequence with 3 to 6 layers, things start to bog down.
Can't hardly make a move without Pr halting you while it saves.
I just did a Convert to Premiere Project and the file size is around 140MB.
Not sure if the TP does a full save as in a normal project but whatever it's doing it locks you out for a few seconds.
Seeing this across all our systems.
Thought I'd throw that out there for those considering doing longer projects.
Any thoughts DEV's?
We do our best not to block the user while auto-saving, but it sounds like that's not the case here. My best guess is that this is due to the complexity of the sequence you're editing, not the number of assets in the Team Project. We've seen that a few filters, in particular, store enough data that they can affect autosave performance. Are you using the Warp Stabilizer or 3-way Color Corrector on a large number of clips, for example?
Adobe Team Projects
Thanks for the response.
Good to know, a majority of the shots are ARRI ProRes LogC so there's a LUT on every shot for one thing.
Also a ton of multi-cam clips (3 to 5 cameras). Would those measure into the complexity?