What is the function of 'Delivery' feature in eMAM?

What is the function of 'Delivery' feature in eMAM?

       Delivery feature helps users to deliver assets to a specified delivery location based on the type of Delivery profile selected. Users can deliver the asset to appropriate locations or destinations with transcoding to the appropriate format/codec with metadata.. They can then use 'Delivery' feature to send the content from LTO to the respective delivery folders. eMAM has a powerful transcoding feature. User can choose the file format, eMAM transcodes on the fly and for delivery in multiple locations in multiple formats.. eMAM can pre-configure delivery profile destinations with XML side cars with required metadata and other parameters. Playable links to proxy copies can be sent as eBIN messages, as shareable URL links, sent to social media and publishing sites, or HTML player code for website insertion. With approval, eBIN and eSHARE recipients and eMAM users can download in any of the pre-selected formats available.

       Our delivery service can deliver original files and/or transcoded files to any Local, Network or FTP locations. This covers most of the video servers, SAN, NAS, DAS and NLEs. Archived assets must be restored to the online storage prior to delivery operation. Multiple assets can be selected as a group for delivery. Selected assets are added to delivery queue. eMAM users can deliver an asset, category, and clip to a specified delivery location. 

       eMAM Director:      

  1. Drag and drop assets from Browse widget to the Delivery widget.



  2. Click Deliver from the widget’s pull down menu to select the appropriate Delivery profile for the selected assets.
  3.        Click on Add button.



  4. Monitor Delivery queue under Dashboard widget to know the status of jobs delivered.        
     

       Note: ATEME delivery profiles support Stitch and delivery of files as shown below:


 
Based on the preset xml attached to the ATEME profile, eMAM will validate it and will throw an error if the files do not match the xml standards. If the files selected for delivery fail the validation, it is highlighted in red. Users can drag and drop the correct files before final stitch delivery.

 



    • Related Articles

    • Bug Fixes eMAM 5.4

      Bug Fixes in eMAM 5.4 BUG ID DESCRIPTION 5.3.1_18NOV2021 11889 Storage DNA API change to handle "404 not found" in the response. 11899 Schedule metadata is not getting updated for PATCH api/v1/assets/{AssetId}/AssetMetadata 11708 PFR is not working ...
    • eMAM 5.4 Release, April 2023

      EMAM, Inc. is excited to announce the release of eMAM version 5.4! This new release includes several key features and enhancements to help you manage your media assets more efficiently than ever before. In addition to the key features, eMAM version ...
    • eMAM Cloud Platform - Production (eCP-Production)

      eCP-Production Deployment About this Guide This guide is intended for IT infrastructure architects, administrators, and IT professionals who are planning to deploy eMAM system (PAAS) on AWS Cloud. Overview eMAM Cloud Platform - Production ...
    • Release Notes eMAM version 5.4

      Release Notes eMAM version 5.4 EMAM, Inc. is delighted to announce the release of eMAM version 5.4. This latest update includes several new features and enhancements that will help our users to be more productive and efficient in their video ...
    • eMAM Publish Server Spec Guide

      Refer the attachment for eMAM Publish Server Spec Guide