-
Premiere Pro Workflow for Editing Using Mixed Resolutions
We’ve recently started shooting 4K on the Canon C300 Mkii which we’re often required to combine during an edit with standard 1080p HD footage. We’re using Premiere Pro CC V10.4, which has always been great at handling different native formats and sizes, but recently it seems to have started to struggle slightly.
It handles 4K footage totally fine as long as we’re working in a 4K sequence but, since we often have to mix in 1080p footage as well, and since we always output at 1080p, we’ve been working in 1080p sequences and scaling any 4K footage down in the motion tab so that it fits. This is where Premiere starts to struggle to play sequences back.
Playback gets laggy, so the audio will continue to play but the video will freeze and jerk. The more layers of video or effects or titles we add, the worse it gets.It’s not crippling, we’ve still been able to work this way, it’s just not ideal. I’ve taken to just rendering everything a lot. It’s like being back in FCP7.
Recently Premiere introduced the new proxy feature which we thought would be the answer to our problems. We’d create proxies in a lower res for all the 4K stuff and edit using that so that we could get smooth playback again then, once the video was finished, toggle the proxies off and export.
So, we have a 1080p timeline, with 4K footage in it that’s been scaled down to fit. As expected this struggles to play back without rendering. We toggled the proxies on expecting to see the footage looking slightly less sharp but playing back fine, but instead the proxies are displaying HUGE. As soon as we hit play the image is, like, 10 times the size, so we’re only seeing the very middle of the shot and it’s STILL struggling to play. In fact, it’s struggling even worse.
We’ve tried creating the proxies using different codecs and sizes but it does the same thing. Are we doing something wrong? Is this even a valid, viable workflow we’re attempting? Or is it not really what the proxies are intended for?
If so, is there another way around the lagging problem for us?Thanks!
Mac Pro (Late 2013) running OS X Yosemite V10.10.5
3 GHz 8-Core Intel Xeon E5
