so iM probably doing something wrong But what is the proper workflow for ingesting 60/120fps footage and using them on a 30fps timeline for slow mo?
typically I created a 30fps and interpret the 60/120fps footage to 30 and theN speed it up to the desired speed (real time or slow) the issue is the proxy is created at the Native fps.
am I suppose to just create the proxies manually at 30fps and link them?
If you mean the proxies PrPro now builds on Ingestion, you don't do squat with the PrPro proxies built on ingest ... other than use them. Have PrPro make them, make sure you've got the Proxy on/off toggle icon on the Program monitor's control set at the bottom of the Program monitor, and click it to turn it blue to playback/edit with the proxies, and toggle to grey to have the original media.
Everything you do to the sequence or clips is done to the original media. The proxies are only used for playback purposes.
It's unclear where you're having a problem. Each proxy should be created at the original's fps. If they did not match, adjustments made to the proxy could not apply to the high resolution file as well.
And, no, you are never supposed to create proxies at a frame rate other than that of the original media:
"The supported workflow allows attachment of Proxies with other frame sizes & PAR (pixel aspect ratio) combinations that are divisible by the Full Res clip (for example, 1920x1080 1.0 PAR Full Res and 960x540 1.0 PAR Proxy or 1440x1080 1.33 PAR Proxy), but other parameters such as fielding, frame rate, duration, and audio channels must match." (Adobe Premiere Pro Help | Ingest and Proxy Workflow in Premiere Pro CC 2015.3 )
I know that some go to the Effects panel, and simply turn off motion effects for their slo-mo clips during most editing processes, then simply turn them back on for full-test playback and for exporting. That should fill your needs, I think.
My issue is the footage is coming off the quad in h264 4k60 which is hard on cpu Rendering. Proxy fixed that but then the timeline is all off when I switch between.
I know there are some updates to the proxy capabilities and to some bugs in the previous release as of the release they've put out today. Does the new release help at all?
Of course, do a save-as or copy of the project before opening it in the new update, just to be safe ... always do this when first trying new updates! In case you need to roll-back.
And yes, you could transcode with the time change and use that on the timeline ... many do.
Almost two years on and still no fix for this within adobe.
Current work around is when creating proxy of said interpreted footage is to:
• quickly open Media Encoder and stop the playlist. • Reset top clip (or any clips done) • Delete any proxies made in saved destination • Highlight all clips to be turned into proxies in Encoder. •Right click and interpret footage to your desired frame rate. • click play
Now you should have proxies at the right interpreted speed. Still a massive ball ache but essential if you are working with 4K footage.
14
Replies
(Remember, proxies are a new feature. Using them is not a "long established work flow" in Premiere Pro.)
AdChoices