DNxHR 444 10 and 12 bit Support

Community Beginner ,
Jul 14, 2022 Jul 14, 2022

Copy link to clipboard

Copied

Premiere Pro has major issues with DNxHR 444. Regardless, if it's the 10 bit or the 12 bit flavor and if it's wrapped in MOV or MXF. I won't even get into the whole Full/Legal debate, as that is another topic, but you can take a look at this thread, it lays out very detailed explanations of that issue: 

https://community.adobe.com/t5/premiere-pro-discussions/dnxhr-444-doesn-t-work-properly-in-premiere-...

 

As a colorist, this presents a challenge, since for a lot of us who do not work on a Mac, exporting ProRes from Resolve is not an option and not every production has the capacity of handling uncompressed files. Be they DPX/TIFF sequences or even uncompressed MOV wrapped codecs.

 

To give you an example, I just had a project shot on the Sony Venice in 6k, client wanted to do a roundtrip workflow where I send them the graded shots in 6k for them to online and deliver. I'm sure you can see the problem of trying to render and playback 6k uncompressed media, especially in an image sequence format, for most it's unmanageable.

 

Presently, Premire Pro just straight up is not reading DNxHR 4444, but it used to. I relied on it to substitute ProRes 4444 and now I cannot. I am that it is not officially supported as it's not listed on the supported file formats page - https://helpx.adobe.com/premiere-pro/using/supported-file-formats.html ;however, I find it unacceptable that such a major and established codec is incompatible with your software.

 

I urge the Premiere Pro development team to take a look at this issue and fix it as soon as possible, as there is a massive need from countless people who rely on it every day to be able to deliver to premiere users.

 

The image below showcases that even the properties' interpretation of different DNxHR 4444 favors is incorrect:

  • MXF wrapped 10 & 12 bit files are both seen as 10bit
  • MOV wrapped 10 & 12 bit files ar both seen as 12 bit.

Screenshot 2022-07-14 at 10.33.01.png

 

Below are the correct interpretations by the software Media Info:

Screenshot 2022-07-14 at 10.55.07.png

Screenshot 2022-07-14 at 10.55.15.png

 

 

This Problem only compounds when trying to deliver files with Alpha to premiere from Resolve on Windows. Again, most productions can't handle 6k DPX/TIFF sequences and DNxHR with Alpha is not supported and does not open in Premiere Pro.

 

 

TOPICS
Crash , Error or problem , Formats , Hardware or GPU , Import

Views

98

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 14, 2022 Jul 14, 2022

Copy link to clipboard

Copied


@josemariaabreusantos wrote:

I urge the Premiere Pro development team to take a look at this issue and fix it as soon as possible, as there is a massive need from countless people who rely on it every day to be able to deliver to premiere users.


Premiere Pro User Voice

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 14, 2022 Jul 14, 2022

Copy link to clipboard

Copied

Yea, this is still an issue. Unfortunately ... and maybe time for @Francis-Crossman to pop in about this.

 

Although I've got a slug of DNxHR presets, RGB, HQX and such available here on my PC ...

 

RNeilHaugen_0-1657818651575.png

 

But it's not accepting the 4444 on yours? I guess I need to test that on my rig later today.

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 14, 2022 Jul 14, 2022

Copy link to clipboard

Copied

Well....

 

Premiere seems fine with Resolve 12- bit RGB files, unless you have an alpha channel attached ... then you get the dreaded frame-excursion warning and a black/void screen for the clip.

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 14, 2022 Jul 14, 2022

Copy link to clipboard

Copied

Are you wrapping them in MOV or MFX? 

 

For me, it's erratic at best:

 

I had to render 6k Source Res Files for a roundtrip workflow, and those weren't being read no matter the combination I tried. I get the same error you get with alpha; however, I don't have alpha.

 

But 1080p MOV wrapped 444 was working.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 14, 2022 Jul 14, 2022

Copy link to clipboard

Copied

LATEST

These were mxf ... and no-alpha, they're fine.

 

Include an alpha from Resolve ... no go.

 

And I just posted on the Premiere Beta forum, which is followed by some of the dev staffers also.

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines