Importing DJI Phantom 4 Pro Footage into Adobe Premiere Pro CC 2017.1.2(22) v11.0 Oasis

Unfortunately, things change over time. When the promise of using any 'native' media was originally made, no one knew that totally new gear was going to be created pushing the boundaries of the codec settings so far. One of the occasional 'helpers' here has software to analyze the clip's codec/settings, and on testing one clip posted by another user, found the general I-frames were up to 120 frames apart.

Between b, p, and partial I-frames, that sort of thing requires massive hardware to handle it. At that point, the NLE is secondary.

Between hardware and choices within the structure of the NLE, there are still of course a range of ways to do anything, and some are more effective on one rig with the hardware & apps loaded on that than another. Hence there's a ton of variability on the effective use of any major app like this, even on seemingly similar machines. Let alone between media types used.

And while your point on the editor needs to be the one organizing his projects is totally valid, I'd note that the majority of professional editors do not convert anything to ProRes, Apple being the jealous kindergartners they are. We don't have ProRes available. Not only is the PC multiverse much larger than the Mac, many pros have left the Mac-verse over the last couple years. Including many colorists I know, which had been one of the most Mac-centric groups imaginable even two years ago.

Which just points out how fast things are changing now.

A major talk in the aisles at NAB this year was the idea that PrPro's team should give up the 'every native media' concept, and like Avid & BMD, specialize in working with a number of the larger 'types'. Which would hopefully get better & more reliable performance out of the app in general.

Avid editors already t-code or proxy stuff like crazy, Resolve's "optimize media" is just their way of saying make & use proxies. As the two examples most cited.

Neil

Yup, it's already copied to my HDD first before i import them under Media Browser... ..

still have the same error on 2 notebooks now... running the same version 2017.1.2.22

What other factors could have contributed to this? What am I doing wrong? Both my computers are Windows 10, i tried both with CUDA (Mercury Playback Engine GPU Acceleration) on and off... same thing...

If you're getting that sort of compression in Handbrake, it's because that app often chooses a HORRID preset to apply. It would take my 4k from my Samsung S7 phone and always convert it to 1920x1080 if I let it!

So I had to create my own preset there, to keep original media frame-size, change to CFR and you need to BOTH click the CFR "radio button" and select a specific frame-rate number, don't use the "Auto" or "same as source" settings, you'll still get VFR.

Plus I had to kick the compression settings in two places into the "placebo" range to maintain the original Mbps and image quality.

After creating a good preset, and learning to use the ... intriguing ... batch operations of Handbrake, I can set many gigs of phone media to convert overnight and be ready to work the next day.

Neil