Blackmagic Forum

This is going out to all my Windows Resolve users who render in DNxHR.

The workaround of rendering Full Data levels in Resolve so Premiere Pro plays the files back correctly (@Video/709) is no longer in effect.

A new update to Premiere Pro now (as of (September 2018) sees DNXHR files rendered at Video levels at Video levels when imported. I just got screwed by this and wanted to save someone else the grief. (I also had included bars on my output so I would be notified if it looked incorrect but I was not notified by the editor or the client. So much for standards.)

Make sure both you and your client are running the latest version of Premiere Pro.

Are you sure it's Premiere?
It's Resolve which in one of the v15 betas had DNxHR levels flagging fixed (it now properly sets and reads levels from DNxHR MOV files).

See a full more in depth discussion of this on Lift Gamma Gain - Same subject title

https://liftgammagain.com/forum/index.p ... els.11386/

Peter C and Dwayne M - Please check it out.

Ending with

Considering Fusion Studio can render Pro Res on Windows... wouldn't it be nice if Resolve studio could? Hey BMD... Is the licensing that bad/costly? How about giving us the option and pass us the cost? I ain't buying a Mac anytime soon.

From this description it still looks like it's Resolve which got fixed, not Premiere.
It was Resolve not setting flags right and Premiere reading them, which lead to wrong interpretation.
If Premiere expects 444 to be full data this is fine. Out of 2 this is more sensible (auto) setting. Best if both tools wold read what is set in headers (and allow overwrite it if needed). Resolve should be fine now. It was reported and BM fixed it.