I have tried DNxHR 444 and HQ.

It looks like decoding with the DNxHR quicktime codec to the b64a pixel format is not working, the codec lists the b64a pixel format as supported. No error from the QuickTime library but nothing happens. The DNxHD codec is fine. Thanks, Guido

Hi Andy, DNxHD 1080p/60 and 1080p/59.94 are both listed in the AVID DNxHD Technology pdf: http://www.avid.com/static/resources/US/documents/dnxhd.pdf If you are saying that there is no 1080p/60 or it is the same as 1080p/59.94 then I have no problem omitting the 1080p/60 option. Thanks, Guido

Below a part of a dump from the actual AAF file where it show a StoredWidth of 1440 and a DisplayWidth of 1920. I am not sure why the AAF XML would show a storedWidth of 1920. EssenceDescription: Object of Class: CDCIDescriptor Locator: Strong Object Reference Array [1] of Locator kAAFTypeID_LocatorStrongReferenceVector [0]: Object of Class: NetworkLocator

Hi Andy, Thanks for the info. I was looking to the stored width instead of the display width which explains my issue. I have now resolved it. The XML you get when opening the AAF only has the storedWidth (1920) and not the displayWidth. The XML you get when opening the MXF file has the storedWidth (1440) but also a descriptor section with the displayWidth

When building an AMT application on OS X with the OS X 10.9 (or 10.10) SDK then the application crashes in a call to the CloseAmtFile funion. When building with the OS X 10.8 or earlier SDK I don't have the crash. The AMT sample app refers to the OS X 10.5 SDK which is quite old.

When creating a 1920x1080 DNxHD 100 file with AMT (version 2.9.0.880.1 WIndows) the created MXF file has a width of 1440 instead of 1920. See the XML below. When loading the AAF back with AMT the width is 1920. When loading back the MXF with AMT the width is 1440. AMT 2.4.0.2.1 does create the MXF file with the correct width. <?xml version="1

When I try to created a 1080p 60 fps file with AMT (version 2.9.0.880.1 Windows) the created MXF file has a framerate of 59.94 (60000 / 1001). See the used XML below. When I load back the AAF (with AMT) it shows a framerate of 60. If I load back the MXF (with AMT) it has a framerate of 59.94. <?xml version="1.0" encoding="ISO-8859