Skip to main content
Samuel Neff
Participant
January 24, 2023
In Development

Proxy workflow - interpret footage

  • January 24, 2023
  • 95 replies
  • 5176 views
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.

95 replies

Known Participant
January 24, 2023
@2887809 Beware, "speed/duration" is really not the same thing. This process will create inter-images, by interpolation or interpretation of the footage, and give a dirtier result than the original video.

We all use interpretation footage here specifically to avoid that (for instance to edit together 24 fps and 25 fps clips on the same timeline, as it's usual with archives, while keeping the video quality clean and not creating any inter-frame).
jmvdigital
Known Participant
January 24, 2023
Alberto, you can change framerate/speed of individual clips on the timeline using the "Speed/Duration" option. I also keep this little list handy, which gives me the speed percents to input when I want to convert a clip to play on a 23.976 fps timeline…

Convert —> 24fps

30 FPS: 80%
48 FPS: 50%
60 FPS: 40%
96 FPS: 25%
100 FPS: 24%
120 FPS: 20%
15 0FPS: 16%
180 FPS: 13%
240 FPS: 10%
Known Participant
January 24, 2023
We need this bug to be fixed.

Workarounds add very annoying extra steps and they do not always work (sometimes we want to change framerate only on few clips, not all, during editing time)
Inspiring
January 24, 2023
It's been 4 years now?
Known Participant
January 24, 2023
@2887809 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.
jmvdigital
Known Participant
January 24, 2023
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.
Participant
January 24, 2023
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).
faroscin72
Participating Frequently
January 24, 2023
Please fix this, it's becoming quite absurd!
Participant
January 24, 2023
Can't believe this is still such a blatant issue.
Participant
January 24, 2023
Please fix this--it seems like something that should just work but instead we have to do a work around.