Proxy workflow - interpret footage

I hate to be the one defending Adobe here, but proxies are designed to optimize playback. Playback smoothness is determined by the size of the video file, the complexity of the video file, and the complexity of the connection between the video file and premiere. Allowing premiere to execute an interpretation of the proxies that is distinct from the source proxies would add a step to — and thus increase the complexity of — the proxy-Premiere pipeline. When it comes to PLAYBACK optimization, symmetry between the proxies and Premiere's interpretation of the proxies is more important than symmetry between the proxies and the source footage.

When you said next version did you mean CC23 or some other next version. What is the actual status of this request. Can we get an update from Adobe?

This is again half a solution. The proxie should take the frame rate of the original file and when we choose Interpret Footage, it should change to that value.

I make my proxies at the beginning of my project without knowing what framerate I will use some clips in. There is simply no time to wait 15 minutes to make a new proxie for each clip I want to slow down.

Thx for taking a look at this.

Hello Fergus, any update about the right way of fixing this problem? Your proposed solution is not the right one.

The right solution is quite easy: create proxies WITH THE SAME FPS OF THE ORIGINAL FOOTAGE. Then Interpret footage the same way both for the proxy and the original file!

I'm still unhappy that this stopgap fix isn't actually the real solution, but... it's better than a hole in the head and I'm using it today, as noted in the release notes for Media Encoder v22.6. Um... it doesn't work. I've interpreted some 59.94 and 29.97 fps clips in premiere to 23.976, and then sent them to ME to make proxies, and ME is continuing to read and render them at 59.94 and 29.97 respectively, rather than 23.976. Am I missing something?

Hey Adobe, you LOVE to say stuff like "please be nice to us, we're doing the best we can" but when you go and do something as wildly dumb and insane as this it makes it practically impossible for us to take you seriously. You can't take 4 years to fix a SIMPLE AND CRITICAL bug in your software and tell us that you're doing the best you can. You have to do much MUCH better than that if you'd like people to not make fun of you.

Right now, this is simply a joke and a slap in the face. So don't be offended when we reply with the same. You deserve it.

Very simple issue that needed to be addressed years ago. You should be able to import the footage, create the proxies, and then re-interpret the footage any way you want while editing without having to worry about proxies and without having to re-encode them each time you want to change the framerate in which premiere is reading those files...

Please it should be as simple as Premiere reading the proxies in the same way it's reading the original file.

We need to be able to re-interpret the footage on the fly without having to worry about re-encoding proxy files.

Proxies should be an exact copy of the original file in a lower resolution, am I wrong? So why are you working on a solution that doesn't solve the issue users are having? Do you guys really think that encoding proxies with different framerates than the original file is right? Do you really think that's a solution? Please address this asap its been years of having to deal with this annoying proxy workflow. It's a waste of time.