The MediaCentral Platform is the workhorse that is integrated into the Interplay environment and gives access to content from 'remote' users.The MediaCentral Platform is the core server that allows users to access content via LAN or WAN when using either the Media Composer Cloud option or from a web browser when the MediaCentral UX option has also been added.This has since been renamed the MediaCentral Platform. Avid Central is the name first given to the remote access system.
MediaCentral simply gives users remote access to content that lives on a Avid Interplay environment. There's also 2 videos (below) which are a detailed guide to how you can use MediaCentral within a Post Production environment, and while a couple of years old, the videos are still relevant. I have discussed this in a previous post here.Īvid's Craig Wilson published a Post on MediaCentral within Post Production on Avid Blog which is nice simple explanation too. Avid are also allowing servers to be visualised when demand on the systems is relativity low. To facilitate this in a cost effective manner smaller systems that run on single physical servers can be used in these cases. Edit suites can also be taken onsite / set and selected material be submitted back from the set to the Interplay as well as allow access to content already on the Interplay. In some cases, where producers and directors need to review edits and shots, the MediaCentral UX interface can be invaluable and also allows content to be kept in sync and even have simple edits prepared on set for use by the editor back in the facility. There is more and more demand for Post Production workflows to offer access from remote sites. Systems that are used in News rooms environments can become very complex with multiple servers used to create a single operational Interplay with high reliability and availability. Media Composer systems are also made part of the Interplay environment and rely upon information from the Interplay Engine, Media Indexer and Look Up Server in order to locate content and create edits. The Interplay framework is made up of a number of services and applications that run on all systems within the Interplay workgroup. The Look Up server maintains a table of all computers and systems on the network to ensure content and features are delivered in a timely manner. It informs users on editing systems and the Interplay engine, where constant can be found for use or indeed it is available to use. This is also where the system is configured and managed from. The Media Indexers role is to track content on nominated Workspaces on the central storage system. The Interplay Engine houses a database that manages and tracks all content that exists on the system. MediaCentral works hand in hand with Avid Interplay, it also works with Avids MAM but lets not get bogged down in that right now so for those who are unfamiliar with Interplay here's a quick overview to help you understand where MediaCentral sits within the Interplay design.Īvid Interplay is Avid's Asset Management system and can be purchased as either Production Asset Manager (PAM) or as a wider Media Asset Manager (MAM) The most common Interplay is the PAM system and it is deployed as a number of servers (Physical or Virtual.)Įvery Interplay on the face of the planet is made up of an ISIS or NEXIS shared storage system at its heart, which is where all the video content is stored.
Ma圎dit went behind closed doors at Avid as project Morpheus and went through a rebirth into Central in 2012 and later being re-branded to MediaCentral. Most editing on an Interplay system, at the time, would be carried out on either Media Composer or NewsCutter, b ut the idea of being able to use a web interface through something like MAXEdit was too tempting to overlook. At the time of purchasing Max-T, Avid Interplay had been around for 3 years and offered limited editing through it's thin(ish) client 'Assist.' Assist was a great tool but it still needed installation and set up on qualified workstation and GFX card owing to the playback engine being used from Media Composer, therefore it made it quite expensive to deploy on larger sites.
0 kommentar(er)
