Sorry about the delay. I should mention that autodetect doesn't work well for MXF files, including AS-11, becuase of large number of subtle variations between different MXF flavors and AMA plug-ins having hard time effectively distingushing one flavor from another. In fact, recent releases of MC do not allow to use autodetect for MXF. But you should

Campbell, Are you on Mac or PC? Can you confirm that you're running 7.0.4 and not 7.0.4.2 or 7.0.4.1? In the 'Open' dialog, when you're doing AMA Link, do you see 'MXF (*.MXF)' in the 'Files of type' drop-down menu? I assume not, because that would indicate presence of MXF AMA plug-in and you don't see it listed by

Hi, I would like to take a look at your MXF files. I sent you an email asking for more information. Alexey

Please email your request to partnerprograms@avid.com . Alexey

Heff, Could you please provide more information about the issue with “HD/SD flag”? Is it Aspect Format Descriptor (AFD), Aspect Ratio, Signal Standard, frame dimensions or something else that is wrong? Would it be possible to get the exact error message from the validating application? Can the issue be detected by the DPP Metadata Application

time_t is the number of seconds since 01/01/1970. I just discovered that AMA::ConvertTime() for reasons yet unknown to me converts only date but not time. While we're looking at why and what we can do you can use something like this for conversion: aafTimeStamp_t aafTime; time_t osTime; struct tm* temp = gmtime(&osTime); memset(&aafTime

There's AMA::ConvertTime(const time_t, aafTimeStamp_t*) in amasdk/include/MetadataUtils.hpp. Alexey

Clip creation date is stored in the CreationTime property of clip's Master Mob. To display specific creation date in a bin AMA plug-in needs to set Master Mob CreationTime to desired value in AAF metadata that the plug-in returns to AMA host via IMediaContainer::GetAAFMasterClips() . Alexey

To activate profiles support the plug-in’s implementation of IMediaWriter::GetContainerCapabilities() needs to return IMediaWriter::kMultipleParameterSetsSupported flag. When user loads a profile restored parameters are passed to the plug-in via IACFParametersXML::SetValues() for processing. Right away the host will call GetParameterInfos() and

test