As posted in http://community.avid.com/forums/t/196903.aspx , AMT3 support for custom metadata as TaggedValue is expected for the next release. If AMT3 is co-located with a MediaComposer installation, by default it will attempt to load the AMA plugins installed under the shared C:\Program Files\Avid\AVX2_Plug-ins path. We are checking whether there

Hello and sorry for the long delay. Regarding the ability to set custom metadata (TaggedValues), this is currently being worked on and we expect to have support available with the next AMT3 release, 3.12. At this point I don't think there is a way of reverting back to the legacy compression labels for writing (which are still supported for reading

Hi Simon, MobIDs follow a specific narrowly defined format and are generally UMIDs as defined by SMPTE 330:2011. You should not have to create them yourself, the AMT SDK will do this for you you unless you override this mechanism by specifically providing MobIDs (which is only meant to be used in very specific cases where typically it was also AMT that

I used the following command line from the demo to extract a MAD (note the paths have been truncated): PS ...\MediaProcessor_4.4.22.138_win_vc12_x64\bin\Release> .\MediaProcessor.Demos.exe 3 AVID_MASTER_CLIP "...\Media\OP-Atom\Avid\XDCAM-HD_50_1080i_25ndf_16x1pcm_16bit_48kHz_TRANS_2s" C:\temp\XML\ ======================================

Raphael and James, the AMT3 package includes MediaAssetDescription.xsd (in the Documentation folder) which fully documents all supported values and properties for a MAD. Usually the easiest way of creating a MAD is to have an Avid product such as Media Composer create the desired media and extract a MAD from there as demonstrated in the Getting Started

JamesTV, AMT is not intended to create AAFs with a higher complexity than master clips, specifically there is no support for creating composition MOBs (sequences). The purpose of the AAF generated by AMT is to describe media assets comprising multiple Avid Atom media files, typically video, audio and data tracks. Creating such AAFs can be a rather complex

Hi Rich, for historical reasons the operating point has been treated as being part of a different family of formats and because of this it has not been supported in AMT, and appears in Production Management/Interplay as generic 'MPEG2-422HL 720p 24'. We have logged a feature request for adding this to the list of formats supported in AMT3.

BTW, the problem showing in the error messages does not seem like it is settings related, rather this appears to be an incomplete installation. For successfully performing an AAF checkin using Interplay Web Services and working with the media, you need at least the following items installed and configured: Media Central Production (Interplay) Engine

Tsachi, as mentioned in my posting to a similar question, please use a toolkit such as SOAPUI to validate that your Interplay Web Services instance is operational and that you have valid credentials etc at hand. You can do this in SOAPUI or similar tools by executing the CheckinAAF() SOAP call in the IPWS Assets realm. You can use SOAPUI to exercise

Simon, we recommend to explore 'Interplay Web Services' functionality with a tool like SOAPUI (https://www.soapui.org/) to ensure you can successfully perform elementary operations such as check-in. The AMT3 notification mechanism for SOAP talks to the same API but with AMT as an intermediate layer which can make it difficult to understand even