Premiere Pro and Proxy/Interpret workflow

[beis300]

In the previous version of Premiere when I interpreted original footage from 60 fps to 30fps and then created proxies, I would be able to simply highlight all the files in Media Encoder (before they start processing) and interpret them all to 30fps. It would all be fine and dandy in the edit and frames would totally match up with original and proxies in the sequence. 

NOW...  for some unknown reason the interpret button is greyed out when proxy files get loaded into Media Encoder.   I thought to myself...  oh great, maybe they finally were able to sort this out and automatically adjust the interpreted FPS in proxy files...  but NO, it looks like that feature has simply been broken and frames dont match up as proxies are at 60 fps VS originals (interpreted) at 30fps...

how to fix? 

[R Neil Haugen]

Don't interpret the original footage.

Use the Time/Duration controls to set the footage to the speed you want. Then make proxies.

Neil

[beis300]

Do you mean like manually setting the speed of clips to say 50% speed kind of thing to convert 60 FPS to 29.97?   That kind of works BUT also now all the warp stabilizer clips need to be nested individually...  still feels like such a primitive work-around ... it seems like such a dumb problem to have...  

[Kevin-Monahan]

Hi Beis300,

Check out this video. It explains the concept of achieving smooth slow motion for 60fps (and greater) frame rates really well.

Thanks,
Kevin

[Warren Heaton]

For the Premiere Pro Proxy Workflow to work as expected, the frame rate of the Proxy should match the frame rate of the Full Resolution clip.