-
Davinci Windows DNXHD FCP XML
I’ve got a couple issues with my new Windows 7 Davinci machine.
1)The DNXHD Quicktime files will not open properly in Adobe Premiere 5.5 Mac, VLC, Compressor or MPEGStreamclip. They DO work in FCP and Premiere 6.0 Windows.
2)The FCP 7 XML gets an error when importing to FCP 7 or Premiere 5.5 Mac.
Is this a known issue, bug, or maybe there is a workaround?
Any help would be much appreciated!
Cheers,
-Alan -
7 Replies
-
Are you rendering files with audio? There is any issue with multitrack audio in prp5.5 and earlier.
Colorist | Online Editor | Post Super | VFX Artist | BD Author
-
No, I’m not. The files import into all those applications, the video is just very messed up, I’ll try to get a screenshot probably by tomorrow.
-
I can confirm bizzare behavior with Dnxhd files in premiere pro cs 5.5 on windows. They look purple or blue. Same files opened in cs6 look and work fine. It does not seem to be a resolve issue though. DNxHD files made by other apps suffer the same fate in cs5.5.
-
Interesting, I just noticed that the issue in 5.5 may be contained to DNXHD 444 I just tested it with DNXHD 36 and it looked fine.
This is what DNXHD 444 looks like in premiere 5.5:
And while playing back:
Obviously though, for workflow, I’m much more concerned about the broken fcpxml workflow. I had hoped that it would be easy enough to get clients to install the DNXHD codec on their machine and I would be able to continue just as I was when delivering prores. Now it seems that may not be the case.
-
Do you have the latest version of the DNxHD codec? The 444 flavors were only added with mc v6.0.
Colorist | Online Editor | Post Super | VFX Artist | BD Author
-
My thinking as well, the screen captures seem to resemble a decode failure similar to for example Single-Link / Dual-Link confusion.
jPo
“I always pass on free advice — its never of any use to me” Oscar Wilde.
-
Okay so that clears up why DNXHD doesn’t work with those apps, they don’t have support for 444.
Now I really hope I can figure out why the XML won’t work from my windows machine. I should do a test this week rendering uncompressed QT files and see if that makes any difference for the XML. I’d rather not move to an uncompressed workflow. Most of my clients have no need and in fact don’t want uncompressed deliverables.
Reply to this Discussion! Login or Sign Up