Is it possible to get any support from the Avid moderators on this topic? This is proving to be a blocking issue for us, and a severe regression over AMT v2. Quite simply, just as Martin describes above, when using DescriptorType = TapeDescriptor is it impossible to set the Clip Name. It does not follow the source MaterialName it is always set to the

I would also appreciate any information on this - we have the same / similar problem in that we would like to specify the disk label and source file / source path details. As we have an intermediate process between the source media and the AMT process - we need to override the values from those of the source media AMT actually uses to files that are

Looking for some help here - all the documentation shows that AMT v2 supports JFIF 10:1 - but I only seem to able to find an XML file for 10:1m. Changing the name to be as below (e.g. S instead of M) does not work, nor does removing the extension entirely. Does anyone have thee example XML file for AMT v2 for encoding to JFIF 10:1? <AmtMediaAttributes>

Raphael, Yes I agree that there is an XSD present in the documentation folder - but its seems only partially populated. For example, we need to know the syntax for the different video and audio codecs - but the XSD does not contain this. below we an see this for the colour space example; <xs:simpleType name="ComponentOrderType"> <xs

Andre, Further to Rich's comments - it would be really appreciated if Avid could release the XSD to go with the MAD XML structure - as an XSD is referenced in the XML, but I am unable to find an online location for it. This would go a long way in us understanding how to leverage the MAD XML structure - and I am sure would stop alot of stupid questions

Andy, Thanks for the reply - and did not mean to say the implementation was not entirely pointless, it would just be incredibly useful for Avid to offer support within the toolkit for AAF generation for multiple assets. However - back to AMT3 and what is there today, I am strugging to generate a MAD XML directly from the tool for a OpAtom asset (e.g

We are assessing the use of AMT v3 in our implementation - and are very keen to try and make use of the AAF generation capability that it includes. However, the example only supports a single file per AAF - which is a bit pointless as the whole idea for AAF is to connect multiple files and present them as a sequence. Is there any way to provide mutilple

We are assessing the use of AMT v3 in our implementation - and are very keen to try and make use of the AAF generation capability that it includes. However, the example only supports a single file per AAF - which is a bit pointless as the whole idea for AAF is to connect multiple files and present them as a sequence. Is there any way to provide mutilple

Vadym, Thanks - will ensure I post there in future. I am confused by your comment regarding the format not being valid for JFIF - Avid Media Composer creates JFIF files with the Rec. 709 colour space - and so how can it not be valid? I believe I am using the latest AMT - but will double check this also.

Using our AMT integration, I am trying to get it to produce a JFIF with the colour space flagged as Rec. 709. This is because the source media was a HD asset, and although the JFIF is SD, of course the colour space needs to reference the HD standard. When we take a JFIF file created by Avid, it is correctly flagged as Rec. 709 when created from a HD