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.
Pedro Rodrigues commented
@trenthappel Using Speed Duration may result, except if you want to Warp Stabilize. You need to nest the sequence above that... lots of steps for an apparently simple feature. So not really an option for most of users. It is also possible to workaround intepreting the footage at the time of transcoding, but this feature should be enabled in the proxy workflow without workarounds.
Ryan Fritzsche commented
This is a massive bug and surely it can't be that hard to fix??!
trent happel commented
Until Interpret Footage support can be implemented for Proxy, a possible workaround is to use Speed/Duration, which is supported for Proxy.
Ben King commented
Adobe this is absolutely unacceptable that is even an issue! We have to use Proxies for the 4K-8K workflows (even on some of the faster machines) and this is causing a MAJOR issue with offline to online.
Yes. We need this basic feature!! It's really important.
I'm for it.
Bryant Coffey commented
Would love for this to also be implemented into the feature where you link the footage to proxies already completed.
Seamus OHara commented
how is this still being ignored? The workaround on YouTube didn't work for me and this really should be something Adobe fixes.. now I have to transcode all my footage from 60 to 23.976 just to use proxies which results in an extra Terabyte of storage needed. This is absolutely ridiculous..
I support this feature request! Please add this as soon as possible.
Thanks to this youtube tutorial I am able to use a workaround:
Steve Anderson commented
This seems like such an easy fix I don't even know why its taken so long. Here's the current solution that shows just how dumb this is: https://www.youtube.com/watch?v=0evKZXohM7o
This is currently the only thing in premiere that makes you think you are not dealing with a professional software.
We really need this. It's not a proxy if it has a totally different framerate than the original footage. Thank you!
yes please. !!
Espeically given that you can manually fix this - by stopping the AME queue and then interpretting the footage there, surely Premiere could be told to do this, i.e. pass on the interpret setting to AME. Doesn't seem that difficult. I presume the devs ran into some other unforeseen problem that they haven't been able to fix
Andy Adkins commented
For projects with a lot of overcranked footage (not at all uncommon) this makes proxies functionally useless.
Looks like folks noticed this over two years ago. Pretty please? Sure seems like it would be trivial to just apply the same "interpretation" to the proxy that is applied to the original. This logic works for other things - like FX, which work whether applied to original or proxy (although I can appreciate that the interpretation probably happens deeper down).
Agree, So important
I'm also voting for this. It is very important.
Right now it's impossible to edit with proxies.
A workaround is to stop the ingestion process on media encoder and interpret all footage to desired framerate.
This is very important.