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.
Bray Moloney commented
It's 2022 and I still can't work with off-speed proxies.
This is a critical issue. Fix it already!!!
Alexander Schmidt commented
Here too, the option to interprete footage has gone with the recent update to AME 22.4. It's still available when manually dragging footage into AME. However, that's a workaround for the workaround. So please fix this once and for all, Adobe.
Is it really so hard to make AME use the same setting for footage interpretation as premiere (automatically) when handing the footage over? Years have passed…
James Taggart commented
Still there for me, AME 15.4.5
David Broughton commented
It now seems the workaround has been disabled? I cannot right-click > Interpret Footage in AME anymore.
Hopefully this means there has been a fix? Does anyone have info on how to interpret proxy footage to match interpreted primary footage?
James Taggart commented
Would be great to know when this will be fixed.. I have 1000's of proxies with the incorrect frame rate. I suspect the speed effect work around will cause conform issues when we go for final post.
@Andy Adkins and @TB54… as long as your math is exact, it should divide those frames up evenly. For my specific camera and workflow, I can shoot in 59.94 fps and use speed/duration to drop it to 40% and plop it on a 23.976 fps timeline. 59.94 goes into 23.976 exactly 2.5x. But if say your original clip was actually 60.0 fps going onto a 23.976 fps timeline, then the math gets trickier and you might have some frame changes. BUT, the same thing would happen with "interpret footage". You can't cleanly interpret 60.00 into 23.976 without dropped frames.
Andy Adkins commented
@TB54 it seems like speed/duration using frame sampling actually does give you the same final results as interpreting to a different framerate although I do remember when it wasn't this way. I was curious and just tested it out. I duplicated a 60fps clip, interpreted one to 24 then dropped it in a 24 timeline. With the second I dropped it in the same timeline as 60 and slowed down to 40%. Going through frame by frame they look identical. So it does appear to be sampling the "correct" underlying frames, which was not always the case.
This is good, however, it isn't really addressing the problem at hand and there are other workflow considerations at play here.
@Justin 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).
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%
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)
Jean-Philippe Gagnon commented
It's been 4 years now?
@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.
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
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).
Please fix this, it's becoming quite absurd!
Abe Kislevitz commented
Can't believe this is still such a blatant issue.
Nicholas Dean Chafin commented
Please fix this--it seems like something that should just work but instead we have to do a work around.
Jan Bambach commented
Please fix this. :(
This bug just cost me two hours work
Christopher Hill commented
Yes, please! Super annoying to have to duplicate clips and create separate proxies (or the myriad other workflows to work around this problem).