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.

[defaultn3vk0rzm2je0]

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.

[IvanTheEditor]

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.

[Ryan Fritzsche]

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?

[Alberto Bedin]

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!

[brdcphoto]

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.

[scrozier]

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?

[Eric5D95]

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.

[Fergus H]

Hi all,

There are two parts to this request:

1. Ensuring that proxies are created respecting changes that have already been applied to media via Interpret Footage.

2. Ensuring that changes in Interpret Footage are applied to proxies that have already been created.

The first part was done and is in v23 or later of Premiere Pro and Media Encoder. The second part is being worked on but I don't have a release data to share at this time.

Regards,

Fergus

[Fergus H]

Hi all,

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.

Regards,

Fergus

[scrozier]

Oh man this one has bothered me for years this is great news. 

[chrisb94858317]

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?

[Alberto Bedin]

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.

[Alex Elkins]

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.

[Remote Index]

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.

[Remote Index]

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

R.

[Alberto Bedin]

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 

[Ryan Fritzsche]

Please, yes.  Address this please.

[scrozier]

Bump.