I am seeing a crash Unhandled exception at 0x00007FFA8BCDDB8E (ucrtbase.dll) inside FTF.dll at the end of processing with MediaProcessor_4.4.33 vc142 The media files are in the final locations so it is something happening after that. I can supply a dump file - is that the best way to move this forward? Thanks Nick

When using AMT to transcode (or re-wrap) we use the WriteAmtTrackSample method and pass in buffers of audio and video data. A change in AMT 2.11 was that the audio buffers needed to be equivalent to a frame of video in duration otherwise errors in the audio MXF files to do with how the duration is described crop up. Thus with that issue identified we

Hello, Something we are struggling with having now updated to SDK 2.11 from 2.10 is that we get an error message when encoding any JFIF resolutions. These worked just fine in SDK 2.10. It appears to work in SDK 2.12 which implies something has been fixed, but SDK 2.12 drops encoding of some formats so using that is not ideal. Specifically when we call

I am an AMT licensee and I'm still not sure that there is a clear list of what DNX formats are supported in the SDK documentation. If anyone can tell me where to look please do so. Thanks Nick

The AMT.xsd in SDK 2.8 only lists 145 and 220 as valid bitrates, yet the XML examples included use 36, 100, 145, 220 and 440. The tag name is also stated as 'mBitsPerSecond' in the xsd but dnxhdMbitsPerSecond in the XML examples. I assume the latter is correct. If I wanted to make DNX185 what would I put as the bitrate? Likewise 175, 115, 110

In the AMT SDK the supplied output xml for DNX145i has different widths for 25 vs 2997 - is this a mistake? e.g. dnxhd_1080i_2997_145.XML - stored width is 1280 dnxhd_1080i_25_145_0a.XML - stored width is 1920 Thanks Nick

Another question on this topic: When would I use <userBinAttributes> tags vs <UserComments> ? Thanks Nick

Hi I'm making 35:1 JFIF and have tried all sorts of combinations of input xml parameters, but whenever I load my AAF into a 25i PAL project the raster dimenstion comes up as 720x1152i. Is this something I should worry about? I'm presenting 720x592 YUV frames using an input XML of <?xml version="1.0" encoding="utf-16"?>

Ok thanks I have that working now. I have some more questions, but I'll post them under a new topic. Nick

I'm trying to generate DNXHD clips using AMT but want to create some custom metadata fields of my own. The XML examples imply that doing <extendedAttributes> <User1>my metadata</User1> <User2>more metadata</User2> </extendedAttributes> in the supplied output XML would do the trick, so User1 and User2 would be