Wednesday, January 24, 2018

Our buttons are bigger and we are not afraid to use them

eMAM has two types of buttons to streamline and automate your workflows.

Server-Side button

With the eMAM server-side button, you can set up a metadata button to trigger any type of workflow on the eMAM server from a single click. Using the workflow configuration settings, and a little programming, you set any workflow including delivery, publishing, and archive to any of the numerous API interconnected systems. Send metadata, JSON, XML, and so forth as HTTP POST. If needed, our technical team or our system integrators can walk you through the process.

Client-Side button

With the eMAM client-side button and a little bit of Java scripting, eMAM gives you the ability to interact with your desktop applications running in your MAC/PC client workstation directly from eMAM Director web interface. The client-side button can pass your media metadata to another application. For example, simple JavaScript snippet can be used to pass the asset media path and metadata to an asynchronous pluggable protocol handler to launch the desktop applications like a Video QC software. This opens up an entire range of simple integrations.

Monday, December 19, 2016

eMAM works with and adds value to Adobe Premiere Pro CC environments with team projects.

Adobe continues to innovate its Premiere Pro, After Effects, and Prelude systems with additional tools and features, including the launch of Projects for Teams (Beta).  Can eMAM work with these environments?  Does eMAM still add value in Premiere editing workflows?  The answer to both these questions is yes.

Projects for Teams (Beta) is built on the current Premiere system.   Users with business licenses and enterprise licenses can now work on either a project or a team project.  Others assigned to a team project will have a notification when another user changes a project.  The system will track versions, sync changes from different users and resolve conflicts that may occur.  The project file is shared in the Adobe Creative Cloud, while the media must be available locally for an editor.  eMAM’s integrated extension panel, as detailed in the white paper (, still offers extensive features for an editor including

  • ·         Preview of all categories, projects, and assets from eMAM, regardless of location.
  • ·         Ingest, delivery, archive, and restore of selected media.
  • ·         Review and approval of sequences
  • ·         Access to metadata, comments, file versions, and history of an asset.
  • ·         Collaboration with others using the eMAM web or tablet interfaces.

eMAM is still an important addition to an environment using Team Projects.

1.       Non-technical users:  eMAM web and tablet interfaces can be used by non-technical users to contribute to projects by assigning media, making markers and subclips, and building sequences.
2.       Access:  eMAM is web based, so users can access and contribute to projects from any location worldwide.
3.       Media Management:  Team projects easily shares projects files, but it does not manage the media.   Media must be available locally for an editor to use.   If editors are in different locations, this will cause multiple redundant copies to be downloaded and stored, which will fill up valuable primary/editing storage.  eMAM only downloads or uploads non-duplicate files.   One button archive and restore limits the use of expensive primary storage while being intelligent enough to retain media used in other editing projects.
4.       Cloud ambivalence:  eMAM supports many public cloud (Amazon, IBM, Microsoft, and others) to process and store projects files, native resolution media, and low resolution proxies.   It also supports private cloud, hybrid, and on premise storage and processing.  While Adobe Team Projects are stored in the Adobe cloud system, organizations using eMAM have the flexibility to use storage and processing system and locations that best fit their security, infrastructure, budget, and other needs.

Look for upcoming improvements for Team Projects from Adobe and Empress.

Tuesday, August 23, 2016

eMAM Delivery Bundle Setup and Configuration

Required components:

1.       eMAM Vault or Workgroup

2.       Telestream’s Vantage:
a.       Vantage Transcode Pro Connect
b.       Vantage Avid Advanced Option
c.       Vantage Analysis

Technical Understanding Level:

1.       eMAM Administrator Training (Empress Technical Staff)
2.       Vantage Workflow Designer Training (Telestream Technical Staff)

Vantage Workflows:

Three Vantage workflows will come with the eMAM Avid Delivery bundle. Administrators will simply import the Vantage Workflows into the Vantage Workflow Designer. Upon importing the workflows there is no need for further setup, as the workflows are pre-configured.

Ingest: This ingest workflow transcodes original video files to H.264 proxy and delivers them to the pre-designated folder location(s) on the eMAM managed storage. Audio files will pass though this workflow as well, and a proxy .wav file will be placed in the pre-designated folder location on the eMAM managed storage. eMAM will redirect all other file types as defined in the eMAM Ingest profile.

Delivery: This Vantage workflow receives a request from eMAM to transcode the original video file (stored in the eMAM Originals Folder) into an MXF/AAF format and deliver the generated files to a predefined Avid Media Files folder. Vantage will create the necessary folders for Avid Media Composer to understand where the related files are, as defined in the AAF file.

eMAM Ingest and Delivery Profiles

Ingest Profile: Within the SuperAdmin Web UI, eMAM Administrators will create an Ingest Profile that monitors a watch folder for inbound media that triggers Vantage to process all video and audio files through the Vantage Ingest workflow. The Ingest Profile will link the ingest process with the Vantage Ingest Workflow via a Workflow ID, which can be found in the Vantage Designer application. The eMAM Ingest Profile will define which eMAM Managed Storage will be used and the locations where the Original, Proxy and Thumbnail files will be stored after the ingest & transcode process has completed.

As an option, Administrators can enhance the Ingest Profile by adding a transcode process that immediately makes an MXF Op1a from the original file. This can be set up in the Advanced Settings/ Configure Transcoders area. Click on the Edit tool for the Op1A Platform and add the Vantage Workflow ID provided by the eMAM technician. Upon ingest, an MXF/Op1a file will be added to the Original folder. When a user delivers an asset to Avid, Vantage will re-wrap the MXF/OP1a to an AAF without additional transcoding.

Delivery Profile: Using the same SuperAdmin UI, Administrators will create a Delivery profile describing the link with the Vantage Avid Delivery workflow through the Workflow ID (different ID than ingest workflow) and the location where the MXF/AAF files are to be delivered. The Delivery Profile will link the delivery process with the Vantage Avid Delivery Workflow via a Workflow ID, which can be found in the Vantage Designer application. The eMAM Delivery Profile will define the location where the MXF/AAF files will be delivered to (ex: Avid Media File Folder on Production Server) once the delivery & transcode process has completed.

Both the Ingest and Delivery Profiles will be given a custom name, which is recognizable by the eMAM Director user (e.g. Delivery to_Avid, shown above)

Workflow Steps

Users will login to the Director UI using their given login credentials.

Ingesting Assets: Users will place the Ingest Widget on their Director workspace, which will allow them to start the Ingest process. Users can select Add Files or Add Folders to the Ingest Widget. They will be prompted to select an Ingest Profile, in this case Vantage_Avid_Ingest, assign assets to Projects and Categories, and add Tags and Metadata. Once the Save and Upload buttons are selected, eMAM will begin the ingest process using the eMAM Profile settings and the Vantage Ingest Workflow.

When the ingest process has completed, the assets will show up in the Browser Widget, ready for previewing.

Delivery Process: When users are ready to deliver assets to Avid, they simply drag-n-Drop them into the Delivery Widget. Once they select all the assets they want to delivery to Avid, they Select Deliver from the Delivery Widget menu. 

The user will be prompted to select a Delivery profile, in this case Delivery_to_Avid.

Click on the Add button and eMAM will begin the transcode and delivery process using the Vantage workflow.

The final output from the deliver process will resemble the diagram below.

Avid Media Composer

Importing Media into Avid MC: Once the delivery process has completed, the Editor can open up the Avid Media folder and Drag-n-Drop all the AAF files into the Media Composer Project Bin. The AAF files will link all the MXF media to the project. The Editor is now ready to edit the media.

Once the Editor has finished a sequence, a flattened file can be exported and saved to the Ingest Watch Folder. eMAM will index the media and make it ready for review & approve, delivery to web, mobile or broadcast and archive.  

Avid Interplay

eMAM facilitates the automated process of ingesting media from the eMAM system into Interplay via the Interplay Transfer Engine. Users simply select the media they would like to use in their project, move it to the Delivery Widget in eMAM Director and select Deliver from the menu. The eMAM/Avid workflow will check-in the material into the Interplay system. Once the media is available, Media Composer and Avid Newscutter editors can begin editing the media.


eMAM can help control and manage the media editors use in their productions. Search, Preview and Deliver media at the push of a button. Finished material can be exported back to the eMAM system for use in other automated workflows like Review and Approve, Delivery and Archive to LTO, ODA or Cloud based storage.

For more information on this and other automated workflows, please contact us at or by email at  

Supporting Avid Editing Workflows with Telestream Vantage

eMAM is a full featured media asset management system, managing media across locations, systems, and workflow processes.    Non-editors can use the eMAM system from any browser or native Android or iPad to select media for editing.   With the tight integration with Telestream Vantage, the eMAM system can now deliver media, both full clips and sub clips, to individual Avid Media Composer, Avid Nexis Storage and Interplay.


Using eMAM Ingest profiles, users ingest media using a Watch Folder, eMAM Feeder or the Web Uploader. The Original files, Proxies and Thumbnails are stored in a pre-defined eMAM Managed Storage location.


The eMAM Director or tablet interface allow users to gather media to be delivered to Avid by selecting individual assets or by selecting categories with assigned assets.  Users move assets to the Director Delivery Widget by Drag-n-Drop or by selecting “Add to Delivery” from the Category menu. Selected assets are now ready to be delivered to Avid Media Composer/Nexis/Interplay. From the Delivery Widget Menu, users select “Deliver” and the pre-defined eMAM Delivery Profile to send media to the Vantage transcoder for processing. Video files are converted to AAF/MXF format and moved to the Avid Media Files Folder.

Avid Media Composer Import

Avid Media Composer users simply import the AAF file and the media assets are ready for editing.

Optional Workflow Using MXF Files and Direct Converts

eMAM and Vantage can create an MXF Op1a file upon ingest and store it in the eMAM Originals Folders. When eMAM users select assets to be delivered to Avid Media Composer, the MXF Op1a will be sent to Vantage and process as a Direct Convert (no additional transcoding) and delivered to the Avid Media Files folder.   


The complete workflow can be obtained with an eMAM Delivery Bundle, consisting of eMAM vault or workgroup, Telestream Vantage Transcode Pro Connect, Vantage Avid Advanced Option, and Vantage Analysis.   Contact us or one of our system integrators for details.   


eMAM can help control and manage the media editors use in their productions. Search, Preview and Deliver media at the push of a button. Finished material can be exported back to the eMAM system for use in other automated workflows like Review and Approve, Delivery and Archive to LTO, ODA or Cloud based storage.

Friday, August 5, 2016

Zip, Zap, Integrated.

Individuals and sometimes organizations use public cloud systems (Google Drive, One Drive, etc. ) for storing or sharing some or all of their content.   These systems are easy to use and have little or no cost, no requirements for hardware and can be accessed from anywhere.    The obvious question about content security is one for organizational IT departments to answer but their impact on asset management is in our wheelhouse.

eMAM, like other asset management systems works best if users have one interface to access all of their (allowed) content.   In a centralized storage system such as a SAN or a NAS this is easy enough.   eMAM has the ability to manage content in multiple different storage locations. This could be on premise, on remote locations, or in the cloud.   A common challenge for an organization is that if an organization has many Google Drives and other cloud systems, each of these individual systems will have separate security systems and separate integrations – this is a real nightmare to manage. 

Enter Zapier!

Zapier, with over 500 systems ( can link different systems together with a simple little “Zap”, including eMAM.  

A few examples:

·         Anything put in your GDrive creates a TRIGGER then a copy (the ACTION) of content would go into your eMAM ingest folder, or
·         You can have a delivery profile to send all clips for review from eMAM into a consultant’s One Drive account.

Note that the workflow can occur in BOTH directions – to and from eMAM/Zapier connected systems. There is virtually unlimited flexibility. The good news is that users accustomed to using certain systems can continue to do so, while the organization can still have all content linked together in one easy to manage interface.   There may be some work for an organization’s IT department or the eMAM professional services team to link each account (each with different security settings), but it is easy to setup with simple point/click logic to create each Zap: IF this EVENT happens (the TRIGGER), THEN do THIS (the ACTION).   There is no need to write any complex scripts, learn new programming languages, or integrate APIs .

We can help you to start Zapping away.