Please add support for DNXHR 444 codec within Premiere.
Seems that DNxHR 444 files show incorrect video levels compared to both Resolve and VLC.
The ticket was founded in 2018,
now it's 2021 and nothing happens.
What is the reason for this platform if nothing happens ?!
A start would be to explain why you don't change it
or to explain that one understands full range and legal rage differently.
We will look into DNxHR import for Influx, our new free BETA is here https://www.autokroma.com/blog/BETA-For-Influx-Importer-Adobe-Premiere-Pro-After-Effects
I just tested DNxHD and it works in a .MOV ! But it also works natively in Adobe Premiere Pro 2021
Interesting, thanks for the info. I was wondering why no one was asking for DNxHR Export in Adobe (Premiere Pro, After Effects, Media Encoder). This could be added to AfterCodecs https://www.autokroma.com/AfterCodecs
Jeff Sousa commented
We just need Premiere to be able to import DNxHR 444. When exporting from Premiere, we can use ProRes. The main reason to need to import DNxHR 444 is that is the best way to export in DaVinci Resolve as a "ProRes4444" equivalent when using Windows. So if you are color grading professionally on a PC and your client is using Premiere on a Mac (most common scenario), you want to be able to render them DNxHR 444 (to avoid chroma subsampling, for instance) and you want them to be able to see your color accurately in Premiere. It's what they paid for.
Do you want export or import for DNxHR ?
greg white commented
yes please fix this
The codec is supported by ADOBE!
DNxHR is YUV Codec and accordingly works correctly
as a legal range codec.
ADOBE think, that 444 = RGB but this is wrong.
You can convert from 4: 4: 4 without losses (pixel by pixel) to RGB
but = that is not correct.
The interpretation of some ADOBE managers, which can be seen as a full-range codec, is technically wrong and not professional.
Greetings to those responsible for Lars Borg,
why is your ProRes 444 interpreting correctly?
The earth is not a disk, in our industry you work with many different tools, so you have to be able to rely on standards.
Also, why do other tools correctly interpret Full or Legal? Why can't ADOBE products do that?
Why can you set this as an artist for other tools?
Why is that not possible with ADOBE products.
We open tickets on the subject of being over 2 years,
why is there no solution?
Andrew Hunter commented
Adobe doesn't care :/ All RGB codecs seem get the data levels treatment (except maybe ProRes?)
I've worked around it by using the levels adjustment manually.
Jeff Sousa commented
Premiere is misinterpreting DNxHR 444 as "Full/Data" levels, which is wrong. Avid specifies all DNx codecs should be / are video levels. So DaVinci Resolve writes video levels into DNx clips, then Premiere misinterprets.
DNxHR 444 files written by Resolve look correct in Resolve, Assimilate Scratch, Avid Media Composer, and Mistika Boutique. Only Premiere is wrong.
This is a major bug, not something we should have to feature request. And the fact that the request is from 2018 and it's now 2020...it doesn't take 2 years to change how a clip is flagged.
We also urgently need the ability to choose between video/data level interpretation manually on any clip.
So if a new codec is developed in the future and Adobe also bungles the interpretation, we don't have to wait 2+ years for the fix.
ADOBE hat das bis 12/2019 nicht hinbekommen