Proxy workflow - interpret footage

[Samuel Neff]

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.

[alans77677996]

Wasted hours of editing because of this. Come on, Adobe.

[mmmedia.no]

Yes please!

[theeditdoctor2]

Definitely!!!!!

[ElliotFrahsSA]

Vital.

[VideoScott]

This is still an issue and definitely needs to be addressed. The expected behavior is for this to work properly and stay in sync with the original footage. After all a proxy is a low resolution stand in for the original. It was a surprise to our remote editors who now rely on proxies. The returned edit was all out of sync without warning.

I'm very concerned this goes all the way back to 2018. I know tons of people use this feature to edit DJI h.265 4k footage (which is tough on the system) and interpret the higher speed footage lower. Same with Sony A7M3, ect...

[Anders Teigen]

An important issue. There is a workaround to halt the AME proxy creation, and change the interpret footage in AME as well. However, I experience that even if image of master and proxy clip now plays correctly when toggling proxies, the audio falls out of sync for the proxies. Checking the proxy file, it seems to be nothing wrong, so there is some confusion in Premiere how to handle the proxy files of interpreted footage.

[JonnyH92]

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.

[P0stup]

Please implement this, the extra step is silly

[russc23176629]

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..

[Tom1587]

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.

[theaveragedave]

Over 2 years later this basic need is still not met...

[chrisb94858317]

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

[HenrikBC]

Adobe, please fix this.

[CalebMcLaughlin]

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.

[Dtorroija]

this should be so easy for someone to code!!! and what a pain in the but for all of us

[Dtorroija]

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

[Sophie McDonald]

This issue needs to be fixed. So many lost hours.

[boondock]

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

[Kees Veling]

This bug just cost me two hours work

[Jan Bambach]

Please fix this. 😞

[Nicholas Dean0101]

Please fix this--it seems like something that should just work but instead we have to do a work around.

[Abe5F8D]

Can't believe this is still such a blatant issue.

[faroscin72]

Please fix this, it's becoming quite absurd!

[KisAnd]

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).

[jmvdigital]

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.