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

Proxy workflow - interpret footage

  • January 24, 2023
  • 95 replies
  • 5177 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

nicklear
Inspiring
January 24, 2023
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
Known Participant
January 24, 2023
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).
Inspiring
January 24, 2023
Agree, So important
Inspiring
January 24, 2023
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.
Inspiring
January 24, 2023
This is very important.