MEDIA ENCODER - INTERPRET FOOTAGE NOT AVAILABLE (GREYED OUT)

[pacoans]

I need to create proxies for different framerate and until now I just interpreted footage both in premiere and then encoder again just before starting the proxy creation queue, to avoid the usual glitch in playback on premiere.

But not Interpret footage in Media Encoder is not available anymore, only shows up as grey.

Please help!

[Richard M Knight]

Does it show up if you only have one item selected?

[pacoans]

No

[R Neil Haugen]

The engineers always say use Speed/Duration on the original clip rather than interpret to a different frame-rate.

Then the standard proxy creation (normally) works. So that might be worth a try.

Neil

[LaLune]

Great work around until you try to stabilize anything and Prem gives you the old "stabilizer and speed cannot be used on the same clip". I wouldn't want a timeline full of clips that have been speed adjusted with the amount of Warp Stabilizers I dump on things lol.

Good work around for now though, cheers.

[Stitch Films]

Hey mate, 

Did you have any luck fixing this? I'm having the same issue with the new version of the program. No issues previously. 

[LaLune]

I'm having the same issue re the greyed out "interpret footage" in Media Encoder. No warning of this change happening and no guidance on the alternative solution accompanying the new update (cheers). What I've noticed is it seems that Media Encoder will now default to exporting proxies using the frame rate stated next to the clip in Prems project window, meaning if you have interpreted your 50p footage to 25p, it will now state 25p next to the clip ofcourse, and then when you select that clip and choose "create proxies" it will export the clip at 25p (BUT NOT AT A 25p INTERPRETATION FROM THE NATIVE FRAME RATE) just at 25p by skipping frames, so you get real time playback, which is not what you told Premiere to do with the frames. It's very annoying because they were so close to doing something very smart here - ie. automatically export proxies in line with the frame instructions you have already given that selected clip in the Premiere project - aka 50p clips interpreted to 25p for slow mo would be exported as 50p clips interpreted to 25p for slow mo, which is the only way you would ever want your proxies to be anyway, identical to the full res clips your are editing with (obviously). Why didn't they just do that..? Instead it looks like they've made an automatic function and blocked out the manual option for us to interpret the proxies frame rate, but then kooked the automated function.

Changing speed duration instead of interpreting in the Prem project would be an ok work around but then every time your try to put a stabilizer on one of those clips Prem is going to tell you you can't use speed and warp stabilizer on the same clip. The other issue is if your shooting was jumoing to and from say 50p and 25p all day do you really want to go through the footage folder and identify every time a 50p clip appears, selected those clips only, and then apply a speed change? Vs simple selecting all clip and conforming them to the same timbase (ie. interpret to 25p)?

If anyone one figures out what Adobe have done here I'd loooooove to know too.

[R Neil Haugen]

As the engineers have noted, you cannot create proxies correctly from "simple" interpreted clips. I know that for many things that seems to work better, but ... you can't fight the engineering code. You lose every time. I understand the frustrations!

A speed change can be a very heavy effect, most users don't simply realize how 'heavy' it can be at times. And Warp ... that's the most demanding tool in the app. Combining any pairing of heavy effects is simply asking for issues. Whether it's Warp & retiming, Warp & Lumetri, or several others.

So the best practical process if you're going to Warp something is to either do it first, then do a full render & replace the clip, or ... do the other effect, render & replace, then Warp.

Personally I get Warp R&R'd and outta my hair right off the bat. Then I don't have any reanalyzation or other issues. Simply a practical thing.

Oh, and same thing if you've got Neat noise reduction going. R&R that puppy ... just to save sanity.

Neil