Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Gigantic Project File Sizes CS6

  • Gigantic Project File Sizes CS6

    Posted by Chris Tarroza on November 8, 2012 at 9:31 pm

    My .prproj file for the current project I am working on is currently at 271 MB. I imagine this is the reason why opening and saving the file takes really long.

    Other than about 10-15 AE dynamic link sequences, there’s nothing in my project that FCP7 couldn’t handle and I’ve never had such large file sizes with FCP.

    I’ve heard CS5 and some CS5.5 users had problems with bloated files. I have not reach anywhere near 1GB like some of them say but the file size is definitely getting up there.

    Everything in the project are assets that I need so I can’t get rid of anything.

    Is this problem something on my end or is this a Premiere thing?

    Karl Soule replied 13 years, 5 months ago 4 Members · 3 Replies
  • 3 Replies
  • Kevin Monahan

    November 8, 2012 at 10:55 pm

    Which version of Premiere Pro are you using?

    Kevin Monahan
    Sr. Content and Community Lead
    Adobe After Effects
    Adobe Premiere Pro
    Adobe Systems, Inc.
    Follow Me on Twitter!

  • Jon Howard

    November 9, 2012 at 12:08 am

    I had a similar issue. The project size got up to over 3GB. For what I was experience, I could repeat the problem by doing one or both of the following things:

    – drag and drop Premiere Pro sequences from my PP project into media encoder for batch exporting. Using the “add Premiere Pro sequence” can take longer, but doesn’t appear to bloat the project

    – enabling “use Preview files” when exporting a sequence. Going into the project file with Text Wrangler showed a huge number of links to preview files added that weren’t in the project prior to exporting with this option.

    I’ve also read that using the Warp Stabilizer within Premiere can cause project bloating. Using “Save As” used to as well, but supposedly that was fixed.

    Hope this is helpful!

    Jon

  • Karl Soule

    November 12, 2012 at 1:22 pm

    Worst-case scenario – create a new project, and import the extra-large project into the new empty one. That usually corrects the issue, and the new project is much smaller.

    Karl Soule’
    blogs.adobe.com/VideoRoad
    k soule (@) adobe (period) com
    Twitter: karlsoule

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy