Are you using Warp Stabilizer by any chance? I've read it can cause this same issue.
Yes I am using Warp Stabilizer. Okay would it help if I disable it? B/c now my project file size is around 1.2 gb.
I already made a new project imported in the sequence, deleted preview etc.
1 person found this helpful
There are a few threads related to Warp Stabilizer causing giant file sizes. One good workaround is to render out an intermediary file of your Warp Stabilized clip from your sequence, and then bring it back in and replace the WS clip on the timeline.
Okay thanks, I found the thread, I'm going to use the intermediary file method. Hopefully it will work.
Thanks, I will report back with the results.
No luck, I removed the warp stabilizer, saved a copy and the file size is still 1.2 gb, and on top of that it takes literally 25 minutes to save the project.
Does having a lot of effects in the project affect the file size? I have about 900-1000 edits with 3 effects per a clip (Neat Video, Colorista 2 and Unshapen Mask)
Well, the good news is the bloating has stopped. But now I'm stuck with a large file size. Sigh.
Try clearing all your rendered files and if that doesn't work try importing that project into a new one.
There's a known bug having to do with preview files & using Save As frequently - it'll double the number of preview file references incorrectly on each iteration. This will be fixed in the next update. Considering the amount of cuts with software effects, I'm betting that this is what you're hitting.
Importing your project into a new one is a good suggestion, it's likely to leave behind any preview file references.
It didn't work. The file size is still the same.
Is there any knowledge of any Conforming "issues" such as repeated conforming of the same files?
ie the conforming recycles thru the media files.
I have noticed this occuring on one of my projects.
Maybe it it is connected to the bloat issue.
CS6 - Win7
I'm only aware of one regenerating file issue, but it's not CFA files, it's the PEK file (ie what's used for displaying waveforms) for XDCAM HD MXF files, and I believe it requires that the media is in some kind of read-only state. That's also fixed for the upcoming dot.
What kind of media file is constantly reconforming for you? And is it CFA, PEK, or both?
The files were AVCHD (.mts files)
Sorry I am not sure what was actually conforming.
I cant get back onto that particular project meantime to replicate and identify anything for you.
I have dived back into CS5.5 to do that project based on bloating /save as issue you gave above.
Got a film to make and finish in 48 hours...starting in 2 hours time from now. (Competition)
I couldnt risk any issues biting me.
Best of luck, Shooternz! Will we get to see your 48-hour results?
I'm having same issue. Project has gone from about 75MB to over 3GB in the past couple of hours, with very minor changes in the actual project (I don't think i imported any new media or made new sequences - did add effects and rendered). Very frustrating.
How come no one's answered Wil's last question?
When is the update coming? We have a major commercial that is at a standstill because our project file size is nearly 6GB in size and we can't even open the project. I'm sorry this is not your fault but this is very bad on Adobe's part. This sort of elementary bug should have been discovered way, way before shipping.
Wil, couldnt SpaceCherryFilms just delete all the preview files?
I gues if there are a lot of renders thats impractical since they would need to be rerendered, huh.
Now that 6.01 has just rolled out, is there a timeframe for fixing the project bloat bug? Seems significant enough to throw your swat team at it and roll out and emergency patch.
Please keep us posted.
6.0.1 already contains the fix for the duplicate preview entries. If you open & resave your project, it should shrink back down.
3 cheers for Adobes timely fix!
Okay, I updated to 6.01 and the bloating problem is not fixed, when I use Warp Stabilizer. My new project once again is growing out of control, after using Warp Stabilizer my project went from 38mb to 640mb. I'm removing the effect before I have 5-6Gb project.
The bloating you are experienceing with Warp, has nothing to do with the bloating that Wil is referring to, Im pretty sure. I think he is referring to the "Save as" bloat that created duplicate preview files when saving in that manner. Right Wil?
Okay cool, thanks for the update Lasvideo. B/c I was very dissapointed.
I could tell. Believe me, Adobe folks bust their butts to make sure things work.
Yep, correct. The fix has nothing to do with the Warp Stabilizer, which generates a lot of ancillary data, and the longer the clip it's applied to, the more data gets embedded in the project.
Hey Will I am having this problem with file size as well. I am cutting a feature length film and the fiile size is about 1.8gb. I am NOT using any warp stabalizers. And when I tried saving it as a new project it took just as long, if not longer to save. This project was initially started on FCP 7, but I wanted to change over to CS6 for a few reasons so I exported an xml. I don't know if there are any known issues with that that could be causing it either. In desperate need of help on this one as due dates are looming and its tough to get anything done when saving takes about 30 minutes.
I was having the same issue (not using Warp Stabilizer either). My prproj file ballooned from 100MB to 1GB in a matter of days, making it almost impossible to open. I got my file down to a workable 200MB by doing the following: [Warning: be careful, this could be destructive if you don't work from a duplicate. Never do this to your original project file]
1. Duplicate your project file.
2. Open it with a text editor (right click "open with", choose "other", then choose TextEdit on a MAC. I think on windows it is ctrl+shift right click, then choose notepad or wordpad.)
3. Look for 2 pieces of code that look like these:
<PreviewItem Index="7363" ObjectRef="344492"/>
<PreviewMediaSerializer ObjectID="345345" ClassID="a3cdecce-0e72-4ad3-8b59-aa53b1b54070" Version="1">
There will be many, many instances of these. (Mine had literally Millions of entries of each snippet.) With every iteration, the entries double in size. My first pieces of each of these referenced roughly 50,000 pieces of media. The next 100K, then 200K, etc.
4. Starting at the last instance of each of these massive chunks of code; highlight them and delete. Work your way backwards (or up, as it were) and delete each progressive chunk of entries. Being careful to not remove ALL of the entries, just the later duplicates.
I suspect there are other areas that can be removed safely, but this is all I did. It made the project much smaller and I was able to successfully open it. I've been working out of it for the last 5 days and everything is still fine. The filesize has actually gone down subsequently.
Hopefully this is helpful. It might be good to save a version after every time you delete a chunk, that way if you get to a point where the project won't open, you can just try the previous saved version and so forth. I'm not saying this is the best way, just what I did to get my project back.
Just wanted to report my findings:
A five camera multicam project of one hour with about 500 cuts.
I had to stabilise most of the clips from one camera that was mast-mounted on a breezy day. The total length of 49 stabilised clips was 7:20 (seven minutes twenty seconds). The project size grew to 184MB. When I rendered and replaced the clips (a tedious process but only took about 30 minutes to do) the project size shrank to 39MB, which is about right comparing it with similar projects.
Possibly worth doing! Certainly it's faster to save, and since I save to Dropbox, it's faster to upload too.
The Warp Stabiliser did a fantastic job of stabilising the clips, almost certainly saving my viewers from seasickness.
Hope this helps someone!