Buttons- Our buttons are bigger and we are not afraid to use them
eMAM has two types of buttons to streamline and automate your workflows.
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.
eMAM Workflows Using Transfer Technology for delivery to Avid
Through a direct integration with MEWS and Vantage, eMAM users can transfer media from the eMAM platform to a standalone Media Composer, In a Share storage environment and in an Interplay configuration.
eMAM Customers have an option to either use MEWS or Vantage to complete the eMAM to Avid and Back again workflow. Here are the common Avid configurations eMAM supports through MEWS or Vantage:
eMAM – now powered and driven by AI
Within DAM/MAM environments, using unstructured data when tagging assets, has always made it challenging to
search and find relevant content. The increase in supply and demand for video has made it even more challenging
to provide vital and searchable metadata to allow individuals to find valued videos as well as meaningful information
about what is found on individual frames. The labor-intensive nature of tagging media has strained operational
budgets, and far too often, has left media poorly tagged. In today’s organizations where video is mission critical, poor
tagging limits the usefulness of content.
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.
[+ Read More]
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.
- 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.
- Access: eMAM is web based, so users can access and contribute to projects from any location worldwide.
- 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.
- 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
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.