How Fusion sees Avid DnX differently..???

Hi All,
Need help. This link below takes you to two small test files. Both Direct from Avid on a PC Win10 Bars with audio.
1) DnX175
2) DnX 175x

When you import as footage into Fusion v9.0.1 PC Win10
Then hit 3 to send it out to my Pro Monitor using a Decklink extream 4k and looking also at it with BM SmarView
they not only import with the wrong levels but they imports looking different from each other.

I really need a workflow using Avid DnX so saying try another codec won't help right now. But I am looking into other options.

Link to test files: https://www.dropbox.com/sh/fy38dfurocuu ... bHVVa?dl=0

**Update: Resolve see both files correctly.

Thanks!
Evan

Hi,

It looks like these files are encoded with different levels (the sub black bar can not be recovered on the 175 file) - are you 100% sure your level settings on export out of avid are the same?

If they are the same I would go for the x version because of increased bit depth but also it is not clipping sub black and super white. I don't know why they are different though... As for monitoring have you experimented with the 'Output pixel format' in the decklink global settings in Fusion? try the 10 bit RGB option as that may account for the levels shift you are seeing on the external monitor/scopes.

What workflow are you aiming towards? Reason I ask is because i'd rather stay away from quicktime and opt for mxf instead - same codec just different wrapper (and one that has not got a history of playing silly buggers with video levels of files!)

Paul

Thanks for the reply. Yes they were made the exact same way just 175 vs. 175x.

I am going to use mxf op1a but for given a client a archival file the QT avid codec is easier for them to understand.

Maybe, but you have to tell them that QT framework on the PC is dead.

BTW, all developers struggle a bit with the implementation of QT without Apple's outdated code. In After Effects 2017 you can generate DNxHD/HR in a QT wrapper, but even the 10 bit formats don't show "billions of color".

Resolve is a bit ahead, since you can also use the MXF wrapper.