Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Adobe Premiere Pro Adobe Premiere CC 2017.0.1 Importing Problems with Large Project

  • Adobe Premiere CC 2017.0.1 Importing Problems with Large Project

     JD Marlow updated 5 years, 1 month ago 2 Members · 3 Posts
  • JD Marlow

    December 21, 2016 at 4:15 am

    Hi everyone,

    We’ve been experiencing something quite strange. Wondering if anyone has run into this. We have a fairly large project — around 12,000 assets. 90% of it is down-rezed dailies made into Pro Res Proxy files.

    Over the last several weeks we’ve noticed that as the project has grown, importing has become a problem. When we bring new clips in via Media Browser they import fine, but then the system will promptly began beach balling for north of 5 minutes before kicking in again and building peak files. If we try to import a second time after that, it takes no time at all, BUT the project itself becomes extremely sluggish overall — leaving us no choice but close Media Browser, save, and restart to re-gain normal performance.

    We’ve tested this on our Terrablock server as well as on a local drive. Same result. It’s not a throughput or network issue. We’ve also tested this in very small projects and we don’t see this issue at all. So it’s clearly a product of having a big project, but beyond that we’re not sure what to think or do about it. It doesn’t seem to matter what we import or what project we import from — it does this every time within our fairly large working edit project. We’ve taken steps to shrink the project, but everything in there is something we need at this point, so that’s not a great option for us. We’re running Premiere CC 2017.0.1 on a MacPro with OS X 10.10.5.

    Has anybody run into this? Anybody have solutions or suggestions? We’re open to anything.

    JD Marlow
    jd@jdmarlow.com
    http://www.jdmarlow.com

  • Chris Wright

    December 21, 2016 at 8:50 am

    all of the stabilized data gets stored in the project file, as does the luts. I recommend rendering out any stabilized shots and don’t add luts to individual clips but use an adjustment layer. Also, some people create smaller sequences as edits as well.
    You will find the project file shrinks significantly.

  • JD Marlow

    December 21, 2016 at 1:16 pm

    Just as a test, I created a project with all of our media clips in it but every single CUT sequence removed from the project. ZERO problems importing. Fast, quick, doesn’t hang up. This is definitely interesting, and at least points to how many sequences we have, or what is on those sequences.

    We have been doing a lot of individual clip color correcting in our edit. Nearly every sequence has a LUT on most clips or some kind of correction. We will do some further testing, to make sure it’s not specific effects that are bogging the system down, but this at least gives us a direction to head in.

    Thanks for suggesting this!

    JD Marlow
    jd@jdmarlow.com
    http://www.jdmarlow.com

Viewing 1 - 3 of 3 posts

Log in to reply.

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