Blackmagic Forum

I discovered an issue regarding DnxHR .mov files exported from Resolve 17.1 —these will not play in Premiere.

This probably isn't a Resolve issue, I just thought folks should be aware.

Files exported in Resolve 17.0 and earlier beta versions are fine.

There seems be something in the file’s metadata that points to the culprit – the files produced in 17.1 say AVdn and do not play in premiere (the file shows up as a .wav audio file)



When one tries to play the file, this warning pops up



The files produced before 17.1 say AVdh and work fine.



I tried downloading and installing the DNxHR codecs from Avid – no dice.

Any ideas?

Here are the Resolve export settings – I’d appreciate someone out there independently confirming this.

Hilariously I just noticed that that 1st image I posted, the VLC metadata of the file that doesn't work, is tagged as DnxHD, not HR. obviously this is impossible since the resolution is UHD.

so, I think this might be a Resolve bug.

Yes, 99% sure codec tag should say 'AVdh' for DNxHR files. Some tools use this codec tag to recognise file, others don't. Premiere seems to rely on it, so file won't load. QTX or Switch player work fine.

It's enough to change 'AVdn' to 'AVdh' in hex editor and file works fine in Premiere.
BM is not very good with regression testing. As you said- it was all working fine in previous versions.

As a workaround use MXF container, which uses different codec tagging method. This works.
Just remember that if you use DNXxHR 444 then manually overwrite levels as Full in Resolve if you plan to work with those files in Premiere.
Premiere always excepts 444 mode ( which can't be in any way overwritten) to be full range and Resolve by default export limited.
Non-444 modes will import fine in Premiere as limited range.
If you export back from Premiere non-444 DNxHR then you have to manually set levels in clip attribute as Video in Resolve. Premiere has bug which exports limited levels, but flags files as full.
2 apps, 2 simple setting full/limited and yet even if DNxHR has been here for years they still can't do it right!
Bit embarrassing for me.

I have the same problem.

Andrew Kolakowski wrote:It's enough to change 'AVdn' to 'AVdh' in hex editor and file works fine in Premiere.

Is there a known way to do that? What hex editor should I use?

Thanks.

Any hex editor which has search option (eg. Hex Friend) on Mac.
You search (as text) for AVdn and once found you change to AVdh (it's exists only once in the whole file). Change is instant. That's it.

Andrew Kolakowski wrote:Any hex editor which has search option (eg. Hex Friend) on Mac.
You search (as text) for AVdn and once found you change to AVdh (it's exists only once in the whole file). Change is instant. That's it.

I'll give it a try.
Thank you so much

Just use MFX instead of MOV.

Hi!
Just wanted to add that I had also encountered this issue and have a similar post.

viewtopic.php?f=21&t=136988&p=739944#p739944

Hope this is "resolved" (pun intended, bah bum, chuck) soon, but very much enjoying 17.1 otherwise!
Best,
-Daniel

Fix sounds crazy easy, so any next update should have it fixed.

Andrew Kolakowski wrote:Just use MFX instead of MOV.

I'm getting issues with MFX as well.

Worked for me. Older Premiere had some other issues- with 12bitDNxHR I think.
Are you at latest Premiere 14.x (or 15)?

The thing that worked for me was to import the DNXHR videos with alpha channels into Premiere 2019 and export them (one at a time) with the video setting: ProRes 4444 with Alpha Channel. It did not work using the batch encoder. The newer versions of Pr don't seem to have the export setting to include alpha channel with 4444. These new ProRes clips work fine in newer versions of Premiere.