Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Poor playback with mix of rendered and unrendered clips

  • Poor playback with mix of rendered and unrendered clips

    Posted by Oliver Peters on May 26, 2016 at 11:31 pm

    I have a timeline, usually with a Lumetri Color filter on each clip. Sometimes other effects, like titles. This is all C300 native 1080p/23.976 media. Playback is usually OK. For best quality I render the timeline to present to the client.

    Then we make a few edit changes based on the review, so now my timeline is a mix of mostly rendered segments, with a few clips scattered throughout that are not rendered. So it’s a mix of green and yellow stress lines. Once I do this, Premiere gets very stuttery in any area where I’m just in an unrendered section or where playback crosses between section. Overall, playback was better before any rendering.

    This is a 12-core 2010 Mac Pro tower with Sapphire 7950 card. Premiere is set to OpenCL. Media is an OWC raid connected as USB3 via a CalDigit card. Also a BMD card to play out via SDI to a broadcast monitor.

    Anyone seen this? Thoughts?

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

    Alex Udell replied 10 years, 3 months ago 4 Members · 11 Replies
  • 11 Replies
  • John Pale

    May 27, 2016 at 1:20 am

    What are your renders set to? Is it the default iframe MPEG or something else?
    Maybe try Pro Res for your render codec/

  • Chris Wright

    May 27, 2016 at 1:25 am

    if the rendered segments are a larger file size than the native, the hd disk access speed would most likely be the bottleneck.

    also, the more luts/warp stabilizer you add, the bigger the project file size(ie. slower playback). and the more clips you have that aren’t nested, the slower the program view will be.(slower interface)

    all in all, premiere isn’t a database NLE like Avid and gets slower the more stuff you add.

  • Oliver Peters

    May 27, 2016 at 1:26 am

    I’m pretty sure it’s DNxHD because I generally use a built preset. But I’ll double-check tomorrow.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Oliver Peters

    May 27, 2016 at 1:29 am

    [Chris Wright] “if the rendered segments are a larger file size than the native, the hd disk access speed would most likely be the bottleneck.”

    Well, except that when everything is rendered, it plays fine. It’s the mix that causes an issue.

    [Chris Wright] “all in all, premiere isn’t a database NLE like Avid and gets slower the more stuff you add.”

    Yes, I’m aware of project size. But it’s really the rendered files that are the issue. Without rendering but with an equally large project – or with the sequence fully rendered – playback is the same.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Chris Wright

    May 27, 2016 at 2:12 am

    are your media cache files and footage on different hd’s? Random access speed may be the problem as MB/sec performance drops
    sharply.

    do you have a benchmarking tool?

  • Alex Udell

    May 27, 2016 at 11:22 am

    Hi Oliver…

    Are you storing renders on the same drive as the project or “Same as Project?”

    How much RAM do you have?

    Alex Udell
    Editing, Motion Graphics, and Visual FX
    Let’s Connect on Linkedin
    Examples: Retail Automotive Motion Graphics Spots
    Example: Customer Facing Explainer Video
    Example: Infotainment & Package editorial

  • Oliver Peters

    May 27, 2016 at 12:57 pm

    [Alex Udell] “Are you storing renders on the same drive as the project or “Same as Project?””

    Yes. All render files are stored on the same drive.

    [Alex Udell] “How much RAM do you have?”

    32 GB with 26 assigned to Adobe apps in the Adobe preferences.

    Render files are Avid DNX 175X.

    The AJA system test tests the array at 226 (write) /237 (read) MB/sec when set to 1080p/4GB file/DNxHD220.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Oliver Peters

    May 27, 2016 at 12:59 pm

    PS: Playback is worse at the end of the day and better first thing in the morning. So I suppose next time I should try a shut down and restart to see if that makes a difference. Could be a RAM leak within the app.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Alex Udell

    May 27, 2016 at 2:20 pm

    hmmm…

    [Oliver Peters] “Could be a RAM leak within the app.”

    that sounds logical…

    like to know what you find there…

    thanks!

    Alex Udell
    Editing, Motion Graphics, and Visual FX
    Let’s Connect on Linkedin
    Examples: Retail Automotive Motion Graphics Spots
    Example: Customer Facing Explainer Video
    Example: Infotainment & Package editorial

  • Oliver Peters

    May 28, 2016 at 10:05 pm

    I was editing more on this same project yesterday and things went smoothly. Same machine and everything else the same. The one difference was that I was largely in Premiere the whole time. The other day, on and off, I had other programs open with Premiere hidden in the background for extended periods of time. It’s possible this has something to do with it. Maybe the Mac Pro or Premiere was have trouble with how RAM was allocated to Premiere, to other apps, and then back.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

Page 1 of 2

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