Participant

Answered

Updated to Media Encoder 22.4 , now I cannot "interpret footage" (120fps proxy workflow)

Forum|Forum|3 years ago
May 11, 2022
27 replies
21647 views

As my subject line says, I updated to 22.4 and now I do not have the option to "Interpret Footage" (it's greyed out) after I send my footage from Premiere Pro to Media Encoder. If you aren't familiar with the 120FPS workaround, I interpret 120fps footage to 23.976 in PP and in ME so I avoid the 60fps issue. I have now downgraded to (22.3.1) until there is a solution. Really hurts my workflow.

Error or problem

Correct answer Zvoss

Unfortantely, I cannot.

Just downloaded the update yesterday and the fix seems to be working great. Thanks @Fergus H

C

chapnmin

Participant

@Fergus H

Hey Fergus, I am not seeing this process work in the way you describe it. I have interpreted PP footage from 120 to 23.976 fps, and then, in Premiere, I select all of that footage and hope to create proxies for it in ME. When ME opens up, all of the files are registering as 120 fps still.

S

STEVEN5C7C

Participant

Can someone please put a cheat sheet in this sthread for the percentages you need to put in for speeding up / down the footages ? or am i missing the point and that doesn't need to be done anymore ?

any video tuts on the new workflow with this new update ?

H

haydn5C5C

Participant

You don't need to slow down your footage manually anymore, once you have your footage in your project, select all -> right click -> modify -> interpret footage -> and set the frame rate to whatever your main footage frame rate is (e.g. 25fps)

all of your 50fps (x2 slowmotion) 100fps (x4 slowmotion) or 200fps (x8 slowmotion) footage will now playback in slow-motion at 25fps.

If your sequence is set to 24fps and your main footage is 24fps, shoot slow-motion at 60 and 120fps, as they are mathematically compatible (e.g. 24 x 2.5 = 60)

Once you've interpret your footage, right click all clips -> create proxies.

your proxies will now also playback at 25 slow motion 🙂

Robert Regan

Known Participant

Hi all

The new version of Premiere and Media Encoder has indeed fixed the framerate issue, and you can just create proxies without any workaround - great 🙂

Is anyone else finding Media Encoder now totally chokes their CPU when encoding? I'm encoding using Mecury with a Vega II so the system should be fairly free, but it seems to be totally killing my RAM and CPU

Can anyone else let me know if they are experiencing this?

Mac Pro 2019, latest OS, latest Premiere and Media Encoder 22.6

Cheers

Rob

Robert Regan

Known Participant

Seems to be when you create a large batch of proxies. If I try to do all my rushes, the CPU goes nuts, if I go folder by folder, it's fine.

A

APS_Chris

Participating Frequently

I don't have the option to update Priemere currently. I'm stuck on 22.5.0 with no option to update in Adobe Cloud. How are people getting this?

Joost van der Hoeven

Community Expert

Via Creative Cloud desktop app. Sometimes it helps restart your computer to trigger the updates.

A

APS_Chris

Participating Frequently

I have the desktop app (Mac), stil not there. I spoke with Adobe tech support today and they mentioned 22.6 has been released in beta to select users, with the main patch being relased to the genreal public the end of September.

Fergus H

Community Manager

Hi all,

Instead of fixing the broken workaround, we are fixing the reason the workaround was needed in the first place.

Specifically, in the next version of Premiere, if you use Interpret Footage to change frame rate, then create proxies, Media Encoder will create proxies at the correct frame rate.

The next version of Premiere will be available before the end of August. Before then, using the Speed/Duration option on the media can also be used to change the frame rate for creating a slow motion effect. It does exactly the same thing 'though in a slightly different way.

Speed/Duration takes more work to use if you have clips with multiple frame rates and you'd like to change them all to the same frame rate. For example, you've got some 60 fps footage, some at 120 fps, and you'd like to make it all 24 fps.

I do this in two ways. First, since Speed/Duration uses percent, I use one of my favorite websites, percentagecalculator.net, to calculate the percentage change I'll need. Second, if the clips of different frame rates are not in separate bins, I'll create a couple of search bins (File > New > Search bin), using Frame Rate as the search option. By doing that, I can select all the clips in a search bin and make the Speed/Duration change.

I hope this helps and thanks very much for all the feedback.

Regards,

Fergus

L

lost_art_photography

Known Participant

Thank you for the update and temporary solution!

As always, multiple ways to achieve the same goal, we all just have our preferred methods we learned and want to stick to 😂

Looking forward to the new rev

S

STEVEN5C7C

Participant

Here's a tutorial on how to work around the work around that no longer works ...

F

firsttakeaerial

Participant

Thank you! It's actually much easier that way!

R

Rowly253925525j1l

Participant

The work around is surprisingly simple yet for some reason Adobe have explained it to no one. The old work around for interpreting footage in media encoder WAS because the premiere file wouldnt match the speed correctly.

instead of slowing down your imported high frame fate footage with modify/ interpret footage in premiere, just label your different speed footage and then create proxies as it is. MAKE SURE the low resolution proxies you make are in the matching codec to the original footage (I.e. h.264)

then adjust 60fps in Speed / Duration to 40% and 120fps to 20% and you should be good. 👍

F

firsttakeaerial

Participant

It seems super choppy during playback (pre-export) when we do it this way

F

firsttakeaerial

Participant

What is the update on this?! This is extemely frustrating! Davinci, here I come!

mistyc46468861

Participant

Add me to the list of frustrated Premiere Users (what I refer to regularly as the buggiest piece of software that I own). This latest update that greys out the Interpret Footage option in Media encoder is just ridiculous. Users have been posting about this since May and its still not fixed in mid July. I rely on this feature daily. If I wasn't so invested in Premiere, I would totally jump ship to Davinci, but don't have time for the learning curve at the moment. I believe a good number if not a majority of Premiere users are in the same boat.

Robert Regan

Known Participant

I agree, Premiere seems to be far more buggy than every other CC application, I don't understand why it doesn't get more love and work better? I regularly have unexplained render errors which crash me out, I've had Adobe Tech Support login to my machine and they couldn't resolve it, they even suggested I just worked in Software Only mode for GPU, and I explained this would mean not using my Vega II GPU, which is a pretty astonishing thing for a tech person to try to suggest.

I've been considering starting a Change petition to Adobe for all users to register with Adobe how dissatisfied they are, and how strongly they are considering moving to Resolve, perhaps with the numbers laid bare in front of them, Adobe might actually give Premiere the attention it deserves, rather than lose the video editing masses like FCP7 once did to Premiere.

Who'd sign?

Thanks

Rob

S

Spencer Peck

Participant

Having the same issue. The proxy process is so frustrating. This only adds to the mess.

I'm tired of paying so much money for such clunky software. Once I'm done with this project I'm dropping Adobe and switching to Davinci. $600 a year is absolutely insane for a suite of products that constantly bug out.

Sorry for the rant, lol.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded