Proxy workflow - interpret footage

Thanks for looking at this one! I don't believe it's the right fix. For most people proxies are made as part of the ingest settings. In other words they are made before the footage is interpreted.

The ideal fix is that when footage is interpreted, the proxy that already exists of the footage gets interpreted too.

Many thanks

This is unacceptable, a major known oversite and critical to make the Proxy workflow remotely usable with Offspeed footage.

Relying on Speed/Duration can make roundtrips with Resolve a nightmare 😉

I see this is in progress! It's about time. Thank you for prioritizing this critical issue.

It's 2022 and I still can't work with off-speed proxies.

This is a critical issue. Fix it already!!!

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…

Still there for me, AME 15.4.5

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?

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.

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