The option also includes a DropBox uploader which can be added to a workflow enabling automatic delivery of files to a DropBox account.
You can now browse a DropBox account and use the Import tab tools to either import media into the ContentAgent’s Store Tab or to submit it directly to a workflow.
Enhancements to ContentAgent’s WAN option This feature can be added to ContentAgent’s J2K encoder option and adds the capability to create IMF packaging to meet NETFLIX delivery requirements. Simple IMF packaging functionality is now an option in ContentAgent.
CODEX HDE Decode support for CODEX HDE (High Density Encoding), a lossless compression algorithm that can reduce the size of ARRIRAW files by up to 60%, is also now included in ContentAgent’s IMG option. ARRIRAW MXF The IMG option’s support for ARRIRAW GPU decoding has been expanded to now also include decode support for MXF wrapped ARRIRAW files created by the Alexa Mini camera. Black Magic Design RAW GPU decode support for Blackmagic Design’s RAW codec is now included with the IMG option. The ability to create an Avid op-atom MXF video only file has been added to v3.12 Enhancements to ContentAgent’s Image Sequence Option (IMG) This new capability has been added to ContentAgent’s existing Avid MXF option but also requires the customer to have purchased the Avid Turbo Pack option to enable this feature. The possible values depend on the AM version and on the other properties.The ability to automate the ingest of still or animated graphics, as a matte key, directly into Avid’s Media Composer or MediaCentral | Cloud UX is now available in ContentAgent v3.12. (Optional) A JSON object with additional properties for the file import. If not given, the system determines a carrier automatically. (Optional) Essence carrier that will receive the file. If not given, the file is imported as additional file without any special handling. Can be one of: Video, Audio, Image, ImageSeq, Doc, Text, Fset, File. If not given, the system determines the usage automatically. The value can be one of: Browse, Thumb, Edit, Distr, Preserve, Aux, Any. (Optional) The intended usage of the file. Can be: asset.FILE, sequence.EDL, asset.SEASON, asset.VIDEO, asset.IMAGE, etc. The asset type corresponds to the object class in AM. The value is only used of assetId is not given. If given, the file is imported to that asset. The file must be stored in a location that can be accessed by the AM system. To use module add it to the package.json file:įull path and name of the file. Before using this exampleĪny library to work with REST. Note the file import path must be accessible by the MC|AM instance directly, which means using file shares already mounted on the server. To generate body of the ma:file-check-in call please follow structure of the call that you can find bellow in the "Structure of the import call" section. Please start with CTMS Registry to get the ma:file-check-in link as an entry point to the interface and then follow links provided in responses. In certain cases best results can be achieved using the orchestration API. the ability to add proxy media to an existing hires asset is limited. Note the default MAM_IMPORT_FILE process script might work for your needs but may require Avid professional services assistance to be modified for the exact customer needs e.g. The example relies on the default out of the box configuration, please be aware that the script can be customized for production environments to significantly change its behavior. It starts the SWoDL script, which generates a BPMN process and then starts MAM_IMPORT_FILE process. To import files using CTMS API the ma:file-check-in call is used. This example shows how you can import media files to Avid MediaCentral | Asset Management (MAM) using the Avid Media Suite API (CTMS). Example of importing a media file to MC | AM Introduction
0 kommentar(er)
