Proxy workflow - interpret footage

Any day now. 

Another current project with thousands of clips from different origins with different framerate... I forgot the hell it was in Premiere Pro to deal with interpret footage and proxies, and the dozens of hours lost on a bug this dumb. I have the feeling everyone lost hope on this.

Bump. 

Please, yes.  Address this please.

Hello Fergus,

may I ask you an update about this topic? Editors are still getting crazy about this. This is not working as it should work. I'll try to summarize:

• We don't want to use speed/duration because speed duration doesn't work in source monitor. Also, you can't apply speed/duration to multiple clip already in the timeline because the in/out will be changed.
• We need to create proxy always using the same fps of the original footage (not interpreted).
• When we interpret footage in Premiere, it should change both in the original footage and the attached proxy.
• Even if the proxy is created after the footage has been interpreted, it should be created with the original fps and then interpreted in the same way as the original footage.

This feature has been requested hundreds of time by a lot of editors. It's really important now with 4K-6K-8K 10-12 bit footage.

Is there the possibility for you to implement it? It should be quite easy. @Fergus H 

For clarity, my post above was originally made in relation to this thread:

https://community.adobe.com/t5/premiere-pro-discussions/interpret-footage-vs-speed-duration/m-p/13784050#M463398

R.

For Adobe,

I'll add this to make clear (in summary) that for me there are two issues here:

1. The limitations on proxy workflow, which Adobe has given no further information on, and which should frankly be addressed so that proxies can be used without limitations to interpret footage, channelization, etc.

2. The poor documentation around interpet footage / speed - a more fullsome explanation of how Premiere Pro effects these functions and a comparison of their strengths and weaknesses would benefit those users with more exacting needs.

R.

I don't get why Adobe's people find this so difficult to comprehend. There aren't 2 parts to this problem. Just make sure 'interpret framerate' applies to both proxy and original. It's that simple. We don't at any point need the proxies to be in a different framerate to the originals.

Hello. You said that "This issue will be fixed in the next version of Premiere Pro: whatever frame rate entered in Interpret Footage will be used by Media Encoder to create proxies."

However this is WRONG.

The righe sentence should be:

This issue will be fixed in the next version of Premiere Pro: whatever frame rate entered in Interpret Footage will be used to interpret proxy the same way of original footage. Proxy is always created using the original footage un-interpreted fps.

This issue literally steals hours and hours of my life so it can't be fixed fast enough. Any idea when the new update will be implemented?