-
Huge Project File Size with XAVC?
Hello, folks,
I’m editing a project with F5 XAVC footage in PP for the first time. Not huge really, about 300 clips, three hours of footage. I have two timelines with a fair amount of that footage in, one a window burn and the other a utility timeline for getting interview transcripts.
The thing that’s weirding me out is the file size – it’s a GIG! I can’t imagine where all that data is coming from. Does anyone have an idea?
I’m on a beefy PC with plenty of horsepower and 64g of fast ram, good drive speed, but the project saves are still irritatingly slow.
THANKS!!
-
5 Replies
-
Have you been using the warp stabilizer? The stabilization data is stored in the project file, so it can make the project file very heavy. I’d recommend doing your stabilization in its own project (or in After Effects), then render stabilized intermediates to use in your main editorial project.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Wow, nailed it! I had warp stabilizer on a two minute walk and talk, didn’t really even need. Project file back down to 1.5 MB. Wow.
THANKS!!!
-
Upon further reflection, this is a tricky question – what to do with the data? It can’t go next to the media very well when I’m using XDCAM media in XDCAM file structure. But it doesn’t really make sense to have it in project file since it’s so big and i have a copy with every autosave. It’s not super-valuable data, can easily be recreated. Like a render file. PP should work on it though, because that was no fun.
-
[Adam Derstine] “Wow, nailed it! I had warp stabilizer on a two minute walk and talk, didn’t really even need. Project file back down to 1.5 MB. Wow. THANKS!!!”
You’re welcome — glad you got it sorted.
[Adam Derstine] “Upon further reflection, this is a tricky question – what to do with the data? It can’t go next to the media very well when I’m using XDCAM media in XDCAM file structure. But it doesn’t really make sense to have it in project file since it’s so big and i have a copy with every autosave. It’s not super-valuable data, can easily be recreated. Like a render file. PP should work on it though, because that was no fun.”
I agree that storing it such huge amounts of data in the .prproj file is not ideal. I think that the warp stabilizer data should be stored in a separate cache file alongside media folders (not in them) or alongside the project, and should be treated as an asset by Premiere.
If you want to see the behavior changed, may I suggest filing a feature request [link]?
In the meantime, as a workaround, doing your stabilization in a separate project more or less achieves this same objective of retaining but isolating the big stabilization data.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Also, this will be something that the forthcoming Render and Replace feature will really come in handy…
Dennis
Reply to this Discussion! Login or Sign Up