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.

Ingest

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.

Delivery

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.   

Package

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.   

Conclusion

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.

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 (https://zapier.com/zapbook/) 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.

SGL FlashPack - The complete turnkey archiving system.

Click below to access the PDF brochure

Solution Brief: Proactive Archive with eMAM and XenData

Click below to view, download or forward the solution brief in eMAM viewer.

User Roles for a successful eMAM implementation

POC –   Point of Contact for eMAM system

This is the business contact for an organization for any legal or accounting issues.   They may or may not be have other roles below.  POC must maintain communication channels between the different internal staff and the eMAM teams to coordinate activities.   They should play a similar role with system integrators, hardware, and software vendors.   

SuperAdmin: 

This person is a Hardware/Software systems administrator. This person must have a working knowledge of Windows Server, basic knowledge of Microsoft SQL server, and networking experience. This person must have administrator access and knowledge of how to create and share volumes on the storage device used by the eMAM system.  If eMAM is implemented in an Active Directory/LDAP environment, then this person will also need to have knowledge and permission to create LDAP/AD users.  This person  should be the main IT administrator for the transcoder, archive software, and other systems that will be implemented with eMAM.

Unit Admin:

This person has a leadership role for one or more groups of business users.  He/she should set up and manage the metadata structure, user accounts, and categories/projects, and assign metadata sets to users and groups. This person will decide what ingest and delivery profiles users and groups use.  He/she must work closely with the Super Admin to effect changes in the system as needed.  This person must work to train and support the users in their unit.

Users:

This person is the production operator of the system. This person will have only the rights and permissions and access to the select categories of assets given by the Unit Admin(s).  This person may be an ingest operator using eFeeder, a person with view only access to videos, an editor using an editing software such as Adobe Premiere, a librarian who is responsible for entering in metadata, or an Archive/Restore specialist.  A power user is licensed for all of the user roles in the systems.   A basic user has access to only browse and share functions, with no access to ingest, archive, media management, or the tablet interfaces.

Others:  

Individuals not defined as users in the system cannot look at the content in the system in any way unless a user shares with them through a social media link, through an eBIN email, or an external review/approval link sent by email.