Skip to main content
C
chrisbrearley
Inspiring
December 16, 2020
Answered

DNx HQX, HQ, SQ & LB Data Levels being interpreted wrong by Resolve

  • December 16, 2020
  • 4 replies
  • 4264 views

Not quite sure when this happened but I know things used to be correct.

 

Resolve is wrongly interpreting any DNxHD or DNxHR HQX, HQ, SQ & LB files as FULL when they should be VIDEO, resulting in washed out files. This has not always been the case. I have pulled in a DNxHD HQX created in After Effects last year and Resolve interprets this correctly as VIDEO. DNx 444 are correctly interpreted as FULL.

 

This has probably caused us to send out potentially hundreds of TVCs with the wrong colour.

 

Colours are correct when these files are brought back in to After Effects so the issue seems to be with how After Effects has started to flag data levels which Resolve is not picking up correctly. The fact that an older file from After Effects seems ok leads me to the believe the bug has surfaced in After Effects rather than Resolve.

This topic has been closed for replies.
Correct answer chrisbrearley

I have disovered the bug has appeared in 17.5.1. If you have rendered out of AE with DNx HQX or less and have not manaully changed clip attribures in Resolve to Video then what you are seeing in Resolve will be incorrect. If you used DNx 444 then you will be ok. 

4 replies

C
chrisbrearleyAuthor
Inspiring
December 17, 2020

So I've done some more investigating, importing files rendered throughout the year to find out when the issue started. It's a very recent thing and seem to have happened in the November After Effects 17.5.1 update. Looking at the update release notes they were playing about with DNx codecs

Fixed an issue that caused QuickTime DNxHR files generated via Avid Media Composer's Universal Media Engine to import as audio-only.
Fixed an issue that caused all-black frames when exporting a comp to QuickTime with the Avid DNxHR 444 codec with an alpha channel.
Fixed an issue that caused import to fail for Quick Time ProRes files.
Fixed an issue that caused garbage pixels when exporting a comp to QuickTime DNxHR 444 with uncompressed alpha.

 

During these 'fixes' this bug has been introduced.

 

 

B
Community Expert
Byron CortezCommunity Expert
Community Expert
December 16, 2020

Make sure that both are working in the same color space, because if you interpret it well in Premiere Pro it means that DaVinci is the one that needs an adjustment of the color profile you are working with. You do this where Jose Panadero tells you in the Color Management tab of Project Settings in Resolve.

Byron.
C
chrisbrearleyAuthor
Inspiring
December 16, 2020

Seriously, guys. I appreciate your input but I have been using this workflow for over 5 years. Something is wrong.

Here is my Resolve window. I have rendered out a black solid from AE as DNxHR HQX 10-bit and dropped it into the timeline and moved it to the right. As you can see, what should be black is actaully grey. Data levels are set to Auto.

C
chrisbrearleyAuthor
Inspiring
December 16, 2020

Spot the odd one out

Jose Panadero
Community Expert
Jose PanaderoCommunity Expert
Community Expert
December 16, 2020

But are you usign color management in Resolve? I'm working on a project with some VFX in After Effects and they look correctly in DaVinci when RCM is active in Resolve.

C
chrisbrearleyAuthor
Inspiring
December 16, 2020

No but even with RCM turned on the problem still persists. This is not an RCM issue, when Resolve Data levels are set to Auto it is incorrectly choosing DATA. Manually changing it to VIDEO sorts it but I shouldn't have to do this.

If you are using a current version of AE to export your files I would double-check this.

C
chrisbrearleyAuthor
Inspiring
December 16, 2020

Further to this, MXFs created in Premiere are interprted correctly.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices