Skip to main content
Known Participant
October 31, 2023
Question

Creating Proxies Frame Rates not working....

  • October 31, 2023
  • 2 replies
  • 838 views

I have some clips shot in 29.97 interpreted to 25fps in Adobe Premiere.

When i encode them to create a proxy i set the proxy clip in Media Encoder to 25fps but it never matches when used as a proxy??

 

What am i doing wrong?Help...

This topic has been closed for replies.

2 replies

Inspiring
October 31, 2023

In media encoder, you have to control click on the clip and change interpret footage there, too.  

 

I have been through the same mess when getting 59.94 footage for a 24fps project.  I just ended up leaving it at 59.94 and doing any time changes in the timeline.

R Neil Haugen
Legend
October 31, 2023

Anthony,

 

Use Speed/Duration, as intended for that type of thing. Then you don't have the problem to mess with proxies and Me and all ... 

Everyone's mileage always varies ...
Inspiring
November 1, 2023

Yes, that's what I've done, put would prefer to make proxies that reflect the original file's frame rate.  I've had times where it's worked and other times where it's not.  Probably user error but when you're your own assistant, that happens! 😂

R Neil Haugen
Legend
October 31, 2023

Because you are using "interpret" rather than "Speed/Duration".

 

This is something that is confusing and puzzling, but ... the two methods of changing clip playback are not interchangeable. And Interpret is perhaps more meant for cadence changes or something.

 

But again, change the speed with Speed/Duration, and then proxies work as expected.

Everyone's mileage always varies ...
Known Participant
October 31, 2023

Thanks for this, i did discover this answer. Another Premiere Pro annoyance lol

My issue is that i have sequences that are processed with interpert and now i need to create proxies i will lose the timelines as they wont be correct positions with slowing down so i will have to rebuild the whole sequence.

 

Any solutions here? Thanks

R Neil Haugen
Legend
October 31, 2023

Yea, that's a right royal pain ... oof. Sorry ... one of the many editing lessons that seem to normally be learned through Pain.

 

I work in Resolve also, and it's got many similar things. "I got to here doing X, but now ... how do I get past this?" answered ... "Ya shoulda done it by Y process ... and now, what you've done needs rebuilding" ...

 

It seems to be part of the trade, apparently. Wish it were otherwise!

Everyone's mileage always varies ...