Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro 60p and 30p workflow – maintaining cuts at different fps interpretations?

  • 60p and 30p workflow – maintaining cuts at different fps interpretations?

    Posted by Bart Stevens on August 15, 2014 at 11:05 pm

    I’m currently editing a project that will need to be delivered in both 30p and 60p. I shot the content in both 60fps and 96fps.
    I know I could edit in 60p and speed up the whole timeline for a 30p deliverable, but I’m trying to figure out another way to give me more control.
    Is there a way to interpret the footage @60p and edit at the frame rate, and then later convert the timeline to 30p and maintain the same cuts?
    My desire is to have the control over individual cuts and do more speed changes at 30p. Basically is there a way to maintain cuts at different fps interpretations?
    Hopefully I’m making sense, and ideas are welcome.

    Walter Soyka replied 11 years, 9 months ago 3 Members · 3 Replies
  • 3 Replies
  • Shane Ross

    August 16, 2014 at 1:08 am

    [bart stevens] “I’m currently editing a project that will need to be delivered in both 30p and 60p”

    What? Two different frame rate deliverables? Never heard that one before. Why? Unless one is 720p60, as that is a broadcast standard for some networks.

    [bart stevens] “I know I could edit in 60p and speed up the whole timeline for a 30p deliverable,”

    You can? No…you wouldn’t speed up the timeline at all. You’d just output it as 30fps…keeping the same speed and timing. Just set the frame rate when you export.

    The rest of what you said confuses me. I get the speed changes in 30p…60p to 30p interprets to nice slow motion, but then what about the 60p deliverable? that slow motion won’t be as smooth.

    Sorry, I guess I’m really thrown by the 60p and 30p deliverables…

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Bart Stevens

    August 16, 2014 at 3:29 pm

    I work for a projection company, and this content will be used in two different stock footage reels. One for HFR Digital Cinema 60p 4K.
    And the other @ HD 29.97.
    Yes, a simple export at 29.97 works best for a straight conversion… over thinking that…
    I actually have dealt with this challenge several times, and I was thinking there must be a better way to approach it.
    If there is a way to develop a workflow where I can do my edit, and maintain my cuts at different project frame rates, it would save a lot of time.
    From a content perspective, within a specific clip the cut is happening at a certain frame, regardless of project fps playback.
    I was thinking there might be a way to convert a project and maintain those specific cuts at a different frame rates.
    I’m just not sure if it’s possible.
    Thanks for the feedback

  • Walter Soyka

    August 17, 2014 at 12:47 am

    [bart stevens] “From a content perspective, within a specific clip the cut is happening at a certain frame, regardless of project fps playback. I was thinking there might be a way to convert a project and maintain those specific cuts at a different frame rates. I’m just not sure if it’s possible. “

    If you cut at 60fps and use that to master both 60fps and 30fps versions, the worst that will happen is that a cut that happens on an even frame in 60fps version is delayed a frame in the 30fps version.

    If you want the cut to happen at exactly the same time in two synced playbacks, one at 60fps and one at 30fps, you should only cut on even frames in the 60fps master.

    (Of course, you should also check my guess on this, as the odd/even rule might be reversed. It should be consistent, though!)

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

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