SimplePanda
lvl.4
Flight distance : 1719062 ft
Offline
|
The 4K files from a DJI copter are not designed to be edited. They're in H.264 and they're full of b-frames and this means they're 100% designed for delivery and playback as-is. If you want to edit with them natively, you either need a lot of compute power on both the CPU and GPU or you need to convert them to an editable intermediate format like ProRes.
Your intermediates can be either full resolution (4K) or they can be 1/4 resolution (1080p) proxies... whatever works best for you. Final Cut Pro's proxy workflow is the gold standard for this (Premiere is just barely catching up to the way FCPX handles proxy workflow).
I've edited entire short films in 4K on a MacBook Pro with just an Intel Iris Pro GPU using Final Cut Pro's proxy system - 4K H.264 in turned into 1080p ProRes proxies can be edited on any MacBook going back several years without issue. You then switch back to the 4K files for final output to get a full resolution finished product. Couldn't be less hassle.
If you're trying to edit DJI 4k files on a MacBook without a discrete GPU, the proxy workflow is your best (and probably only real) approach. I'd even still use a proxy workflow even with a discrete GPU MacBook just because there's no reason to be waiting around for anything.
Hell, I still use a proxy workflow on my multi-core, multi-GPU Mac Pro in my home studio. You're just wasting compute cycles dealing with all the extra pixels when all you're really doing is deciding on cut placement.
Just my $0.02.
|
|