Please make sure your media locations/workspaces are properly configured in Media Indexer. Set up AMT3 for IP Web Services check-in and if everything is configured correctly, things should just work.

aviduser78, a Linux version of AMT3 is available through the Avid Partner Program, currently for CentOS since this is the OS for the Avid Media Central platform. The Linux version has restrictions compared to other AMT3 platforms. An Ubuntu version is under consideration but would be targeting the Ubuntu 22.04 Long Term Support version.

Bridget Russo, this thread is 5 years old and online status computation was improved in multiple turns over this timeframe. You should always get consistent (and green) results with Media Central | Ingest. Please open a case with support if this is a reproducible issue.

cda, Avid does not support arbitrary UTF characters in network locators/file paths; UTF capabilities for file paths are limited and not consistent across products. You *may* be able to make this work by using proper locales on all machines that participate in the workflow but this would be absolutely at your own risk and expense. Avid products and SDKs

cda, what you see is likely not an error. Media Central Production expects media to reside on configured NEXIS storage paths. The //UNAVAILABLE tag indicates that the mediahas not been created under a known and supported Production Management storage location at check-in time. Please use the Avid Media Toolkit and have it create media under a NEXIS

Hi cda, AMT 2.13 was released in September 2016 and has been out of support and development for years. It is deprecated for new developments. Please use a current version of AMT3 where EWC is demonstrated in the sample app 'out of the box'.

Aurélien, ST377 states that PTNs are defined by the Essence Container specification. For mapping into the MXF Generic Container, ST0379-2 defines the PTN for the file source mob as UInt32 comprising four bytes that shall have the same values as bytes 13-16 of the KLV key of the corresponding System Element. AMT3 follows this rule so this is 100

In AMT3 there is a difference between essence description and target/encoding settings . 'DNxUncompressed Standard' is the description of a specific encoded essence format. As target/encoding format setting , only the label "Uncompressed" is supported. This works as expected on our side.

Hello Steve, For legal resons, ProRes in Avid Atom is not supported by AMT3, and currently support for ProRes in AMT is not on the roadmap.

Hi gyula, yes, a hires/lores setup with video/audio hires and lowres/proxies is fully supported by MediaCentral Production Management (formerly Interplay) and everything will work smoothly if the required metadata is correct. Note that there is not just one 'mobid' but - for masterclips - at least three (master mob id, physical source mob id