Sorry to re-awaken this thread, but I am trying to write 436 via AMT 3 and I cannot get it to create a working MXF file. This is AMT 5.2.2.10098 using the data track as described in the sample MADs. I have tried with and without SMPTE ANC ID + Ber, and tried fixed 256 bytes with 0 padding and the actual CC size. Here is the MAD entry for the track <mpmad

Hi All I am trying to use AMT3 (version 5.2.2) to write an uncompressed video file to be used as an alpha channel for a video file. I have found a number of MADs that are accepted by the AMT interface, but none of them allow me to actually write the uncompressed frames. I am initially trying to setup for 'DNxUncompressed Standard Format' or

Just FYI, I did try setting it via the webservices API, but it returned this: <Error Code="INVALID_PARAMETER"> <Message>An invalid parameter was used</Message> <Details>The SYSTEM attribute group is read-only.</Details> </Error> Looks like it has to be specified somehow when creating the initial output,

Good Afternoon! I am ingesting files into an Interplay system using AMT3. The customer wants the com.avid.workgroup.Property.System.SourceFile set to the name/extension of the original file. I have not been able to find how to set this value. It does not seem to get set from the job (like the tapeName) nor the MAD. Is there a call/setup I am missing

I can confirm, it works as Bruce says, so long as you are using the 4.4.28.10055 SDK (or greater presumably)

Thanks again. Looks like your SDK is a little ahead of ours. I will see if we can get an update. Cheers, James

Thanks Bruce! You are absolutely correct, of course :), I fogot to properly scope those tags. Unfortunately, that change did not work here. We are placing the tags in the MAD before we start the AMT3 writing, at the same level and between the StartTimecode and the MaterialName tags. Is that the same as what you are doing? Cheers, James

Hi Andy Has this been released yet? I am using version 4.4.23.10046. I have added some tagged values to my MAD like this <?xml version="1.0" encoding="UTF-8" standalone="no" ?> <mpmad:MediaAssetDescription xmlns:mpmad="urn:AVID:MediaProcessor:MediaAssetDescription" xmlns:mpct="urn:AVID:MediaProcessor

Hi Martin No we never did get to the bottom of this, mostly because it stopped happening. I am not sure if it was our plugin or MediaComposer itself, but something changed during the upgrades/development, and we could no longer reproduce it. Cheers, James

We have a lot of systems doing XAVC-S linking now, but we have one OS-X system running 8.6 that is getting a 'AvidOPFrameGenerator' error when we try and link files from any Sony camera. I cannot find any information on this error, but I am beginning to think it might be an installation issue. Can anyone from Avid shed some light on this? J