Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro PPro CC exporting with variable frame rate

  • PPro CC exporting with variable frame rate

    Posted by Randall Wurster on November 27, 2013 at 2:18 pm

    I’m exporting sequences from PremierePro CC – batch encoding via Media Encoder (FWIW, the problem I’m about to describe happens whether exporting is done in batch in AME or one at a time in PPro). For this given project, I was encoding the files as ProRes, 29.97fps, and until now have had no issues.

    Now, a couple weeks (and one update to Premiere CC/Media Encoder) later, they are exporting at variable frame rates, which is causing a problem when I go to render to its final (web) destination via Squeeze. QT, and then Squeeze, reads them as having frame rates anywhere between 15-30, really random numbers. VideoSpec reads them as having a max frame rate of 29.97, a min of .039, and an “average” somewhere in between (22.757, for instance).

    I’ve seen this problem before with Animation codec, but never with ProRes. The fix then was to force a keyframe for every frame; that option is greyed out in the encoding settings in PrPro.

    As a workaround, I’m running the files [that read as variable frame rate] through Compressor, creating intermediates that have the proper fixed 29.97 fps frame rate, and those files will compress fine for the web in Squeeze.

    I’m curious if anyone else is running into this issue, or has run into this issue, and if so, have any ideas for the fix. Thanks –

    Randall Wurster replied 12 years, 5 months ago 1 Member · 1 Reply
  • 1 Reply
  • Randall Wurster

    November 27, 2013 at 2:34 pm

    FOLLOW UP: So, it actually has to do with the “optimize stills” checkbox it seems. I checked that when I was getting glitchy frames rendering out stills in the sequences.

    Unfortunately, I need that box checked as I have many stills in the project. But at least now I know what the problem is and get what that checkbox is doing.

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