How can we improve Premiere Pro?

← Premiere Pro

Proxy workflow - interpret footage

Please make the "interpret footage" feature pass down from hi-res native footage to attached proxies. For example, if native camera footage is interpreted from 60fps down to 23.976fps, then the 60fps Premiere-generated proxies should be interpreted that way as well.

190 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Samuel Neff shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

51 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • TB54 commented  ·   ·  Flag as inappropriate

    @Justin VanAlstyne I'm not sure to understand: "interpret footage" is the only way I see to modify the framerate of a clip without creating or calculating new frames - it's perfectly clean (to go from a 25ps footage to a 24fps one, for instance). Slowing down with speed/duration will create those inter-frames, whatever the chosen way.

  • Justin VanAlstyne commented  ·   ·  Flag as inappropriate

    Andreas is correct. I was mad about Premiere's inability to create proper interpreted proxies… but after some research and further learning and experimentation… the CORRECT WAY to handle this is to simply create proxies at the native FPS, and then when placing that footage in your sequence, simply slow it down with speed/duration. This works much much better and more reliably.

  • Andreas Kislinger commented  ·   ·  Flag as inappropriate

    I was also disappointed, that this is not working.
    But what I found out at my computer (I9-9900K, RTX2080), that speed/duration is working way better and fluently as "interpret footage".
    With interpreting footage I was not able to view a simple 4k50p video in full quality, when slowed down. (200mbit/s)
    But with speed/duration this is possible, also when a LUT is applied.

    Just for information, that this is my "work around".
    Also I become faster and faster with some single clips, which shall be stabilized (nested clips).

  • Christopher Hill commented  ·   ·  Flag as inappropriate

    Yes, please! Super annoying to have to duplicate clips and create separate proxies (or the myriad other workflows to work around this problem).

  • Diego Torroija commented  ·   ·  Flag as inappropriate

    You really owe us this basic functionality cmon man!!!

    this is a super frustrating problem when you have 1000 clips for example vey slowwwwwww.
    this should be so easy for someone to code!!! and what a pain in the but for all of us

  • Caleb McLaughlin commented  ·   ·  Flag as inappropriate

    I'm surprised this isn't fixed yet. Yes, there is a workaround, but it certainly doesn't help if you recorded proxies in-camera.

  • Chris Bretz commented  ·   ·  Flag as inappropriate

    Why is this still an issue 2 years later? Please fix Adobe! It's a basic Professional feature that needs to work.

  • Russ Clapham commented  ·   ·  Flag as inappropriate

    Agreed. Ive just found out that the slo mo shots I interpreted from camera speed 50 to 25fps have been replaced with incorrect footage when Ive exported it.. very embarrassing. Work around for me is to delete the proxy files and only use the full res. You can't even make a proxy from an interpreted shot - it failed on media encoder and I had to restart the queue in the morning,, v frustrating..

  • TB54 commented  ·   ·  Flag as inappropriate

    This is turning me mad and making me very late for my edit right now - and even if you can match the framerate threw the Media Encoder trick, audio won't follow, so it's still useless.

    That's exhausting and making edit of projects full of archive nearly impossible, please fix this.

    EDIT: for those who have this problem but must use proxies anyway, here is a (pain-in-the...) solution: create your proxies manually. That means:
    1) Go in Media encoder, import your video files, and create "proxies" by converting them into a lame codec (like ProRes Proxy for instance), while keeping the SAME RESOLUTION and audio tracks distribution (2.0 / 5.1) than the original files (very important).
    2) Put the converted files in another folder.
    3) Then, in your project, relink all your files to those proxies. At the end, when you must export, relink your elements to your original video files. Complicated, but it works, and allows you to interpret footage as you want.

  • Jonny Havens commented  ·   ·  Flag as inappropriate

    The workaround works but it's a silly extra step. I hope Adobe isn't just letting this go because there's a workaround their users have figured out.

← Previous 1 3

Premiere Pro: Editing

Categories

Feedback and Knowledge Base

(thinking…)