This post should be titled WHY WON'T ADOBE LISTEN TO ITS CUSTOMERS? but it would probably be flagged and removed very quickly.
After scrubbing the web and the forums for a solution for using Premiere's relatively new-fangled Proxy workflow using interpreted footage, I found a great workaround/hack that definitely gets the job done. I would like to thank arodon7 for his/her post that includes this extremely useful YouTube tutorial.
For the sake of SEO, I am talking about taking high frame rate footage that you might want to play back at a slower frame rate to achieve a slowmo/slomo/slow motion effect. If you're shooting at 120fps and you want your footage to look like it's playing back in slow motion, you have to tell Premiere to treat the footage like it's playing back at the timebase of your sequence, say 23.976, by going to Clip/Modify/Interpret Footage, then entering in the timebase of your liking.
However, if you try to create proxies from these interpreted clips, Premiere sends the clips to Adobe Media Encoder flagged with their original frame rate. The resulting proxy is out of sync with the interpreted footage because it's playing back at its native speed rather than the interpreted speed, rendering it useless.
ATTENTION ADOBE-- SQUASHING BUGS AND FIXING BROKEN FEATURES LIKE THIS ARE JUST AS IMPORTANT AS ADDING NEW FEATURES.
It seems to me that given the simplicity of the "hack" referenced in the YouTube tutorial that this would be a very easy thing for your developers to fix. So why has it not been addressed? Why is there a brand-spanking new version of Premiere and do you not advertise the bugs that have been fixed? Finally, WHEN CAN WE EXPECT TO SEE THIS PROXY FEATURE FIXED?
If you're going to implement a proxy workflow, which has been used for literally decades by the pros using Avid, you should not half-ass it. I would also suggest consulting with professionals who use your product on a daily basis before, during, and after you implement a new feature so as to make sure that you're writing it correctly. I SPEAK FOR ALL OF US IN POST WHEN I SAY THAT COUNTLESS HOURS ARE WASTED TRYING TO FIND WORKAROUNDS FOR STUFF LIKE THIS AND IT. IS. MADDENING!
Thank you for reading this and taking it seriously.
A rather bizarre opening statement ... these forums are here for getting comments most that will be critical of the current state of the program, or why else would one post here? You're having trouble with the program, you post here and see if someone can offer a helpful suggestion.
A normal human part of the above is a rant now an then. The policies are simply to keep the language "clean", don't attack people in "flaming" behavior, and be respectful of contrary ideas. If you've looked through this forum much, there's been a TON of threads where people question the sanity and such of the folks of the development program. Past that, I don't know a single person who uses this app (including a few engineers I've talked with) that wouldn't want at least a few major changes to suit their own needs.
The issue with proxies and interpreted time-rate original media is a royal pain, I totally agree. The best way to move that up on the list is to file the feature report forms ... no, they never respond. But every bug or feature report gets filed on the collated lists that are constantly sent to all the managerial types.
As to when this will be improved ... that we'll never know until they announce the release info for a release that 'drops' including this.
For all readers coming to this thread ... saving you some time. Say you've selected one or more clips on a sequence/project, and used Modify/Interpret time to change the playback speed. Now you can create proxies, but they will be at the ORIGINIAL speed ... NOT good.
Now, you should have working proxies at the interpreted time setting.
And please, file the feature request for this!
sorry this is a very slow solution when you have 500 clips I have to proccess on the daily bases
If they're all in a batch, it takes a little bit of extra time over what it should be, true. But it's not like you do that bit about 'relinking' with all of them. That should only be necessary with the first file. You don't do that with all 500!
So ... after you go stop the queue, reset to the proper time, and 'go' ... you're about done. At the end, just manually relink the one file.
And yes ... this is something that should be fixed. Period.
Great write up for the solution
Wow! Thank you so much! Worked seamlessly.
Thanks ... and please go to that UserVoice link and upvote this. This needs attention ... sigh.
Thank you once again.
Just submitted the wish form highlighting the issue.
Not sure what the User voice link is... sorry.
Thanks man!! 185 Votes on this problem and counting BS!!!
Adobe please!! open your eyes and ears !!!!!