Participant

Question

DNXHR 444 doesn't work properly in Premiere! Shame.

Forum|Forum|9 years ago
March 17, 2017
6 replies
8071 views

Hi there,

Since Premiere still doesn't have a proper RAW decoder, you must go over Resolve with Cinema DNGs. I exported the DNGs to DNXHR 444 and imported the files into Premiere: The footage looks washed out! I tested out various scenarios (incl. .mxf) and its definitely a Premiere problem!! The footage looks correct Resolve.

Is there a way to fix this? If not, Adobe should really address this!! Other DNX formats work fine (e.g. HQX, LB etc.).

Cheers

This topic has been closed for replies.

A

Andy 1968

Inspiring

Could this solve the problem for you?

https://youtu.be/nN2XlWWd26Y

Waldorf & Statler

Inspiring

No!

R Neil Haugen

Legend

Hey there Waldorf, nice to 'see' you again!

Looking up the Apple pdf, they do say their 4444 codecs can be used either for RGB or Yuv.

And knowing how Mr. Borg looks at this, I would have guesstimated he'd go with RGB. But I see from some comments in the AE forum, Ae may be running YUV with this? I've not worked with this in Ae.

Now, inconsistency would be nothing new ... sigh. So, you're getting a legal range from ProRes 4444 in Ae? Sigh.

Neil

Everyone's mileage always varies ...

Waldorf & Statler

Inspiring

Hey Neil,

When they look up the Apple PDF, they say that their 4444 codecs can be used for either RGB or Yuv.
That would be ok for me!
Then ADOBE would have to interpret it correctly either way.

It's a little strange that Lars Borg has an AVID codec
absolutely wants to interpret RGB full range, although the designer of the codec sees it differently.

For an Apple Codec, where it could go through full range,
but he only uses legal range although the designer says both are ok.
Strange. Politics?

This point also leads to mistakes that can be avoided if you work with different tools and with several companies on a project.

Waldorf & Statler have long recommended packing test charts in front of them when exporting from tools, with which it is easy for the artists to then determine whether your material is interpreted correctly.

It's a shame that ADOBE cannot change the attributes for full and legal.

Have a nice evening

Charles Waldorf

R Neil Haugen

Legend

Hey, agreed. Although I've found that rather than hunting for 'reasons', it's often more accurate to just realize people tend inconsistent more often than not, once something is done one way by someone along the line (even if meant as just 'I'm getting this working for the moment while we puzzle details out later ... ') it likely gets stuck as "the" action, and stasis is the nature of many codewriters.

Makes things difficult for users at times, but ... humans have been humans for millenia, and we don't have a fix for that in sight.

Neil

Everyone's mileage always varies ...

R Neil Haugen

Legend

Waldorf & etc. ...

DNxHR 444 is an RGB format/codec, which typically means full range. DNxHQ on the other hand is in YUV.

I've seen numerous posts on other non-Adobe forums on how to get proper DNxHR 444 out of Resolve, which includes manually setting it to Full range in Resolve. This way the files from Resolve go into both Premiere and Avid correctly without needing futzing in the 'receiving' app. For it seems most Resolve users, the correct export has been done since I think about 15.1 without needing to change from 'Auto' levels, but some still occasionally report troubles.

So ... there may be some diffence of opinion on this, but ... offhand, I don't know of any RGB codec that is legal range.

There are Lumetri presets that ship with Premiere for conversion from full to legal and legal to full, of course.

Neil

Everyone's mileage always varies ...

Waldorf & Statler

Inspiring

High Neil,

AVID call the Codec DNxHR 444 and not RGB! Correct?

444 is an YUV CODEC! The conversion between 444 and RGB can be pixel by pixel,

so some people say or mean 444 and RGB are the same, but that ist not correct.

I think Blackmagic now this litel different, so you get at automatik the correct legal range version!

Greetings

Waldorf

R Neil Haugen

Legend

I was just looking at an Avid doc that stated DNxHR 444 is RGB, unlike the HQX which is YUV. Here's a chart from Avid ... showing RGB Chroma Subsampling for DNxHR 444:

I've just been through several forums from Lowepost to Reddit and Avid ... the accepted tale is that DNxHR 444, as an equal 4:4:4 codec, is full RGB, unlike the rest of the DNxHR codecs, all 4:2:2, and which are YUV.

So I'm fairly comfortable with saying Avid apparently considers this an RGB codec.

Neil

Everyone's mileage always varies ...

Waldorf & Statler

Inspiring

The Problem is not Resolve!

The Problem is a wrong interpretation from legal and full range in ADOBE Premiere and AfterEffects.

DNxHR 444 is a legal Range Codec, but the devoloper from ADOBE have a problem to understand this.

We have been reporting this problem for over 2 years, but so far the problem has not been resolved.

E

excited_Genie16B8

Legend

The Cineform exports from Resolve work fine in Adobe software.

R Neil Haugen

Legend

Resolve has some different settings for internally handling/using color spaces & settings. Occasionally some of the ones people use that seem to work with Resolve do not work with PrPro. That might be an issue (small probability, but there).

Neil

Everyone's mileage always varies ...

Waldorf & Statler

Inspiring

Sorry Neil, your Answer is not correct. The Problem is, that ADOBE have a wrong interpretation for Fullrange and Legalrange at DNxHR 444. Your Answer is from 2017. ADOBE have it not fixed to 12/2019.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded