Avid workspaces can be used natively by Flow
Editshare’s re-engineered MAM supports third-party storage environments and offers a subscription-based model.
EditShare says its Flow software-defined MAM will be available through a subscription-based model at the end of September. It supports non-EditShare storage environments including Avid NEXIS, StorageDNA and Amazon S3.
“The days of everyone involved in a production being in the same building, at the same time, are long gone,” states James Richings, General Manager, EditShare. “Whether you’re a broadcaster, post facility, news agency, education establishment, or a corporate media department, this new version of Flow creates flexible ways for teams to make better use of their existing storage infrastructure. With unrivaled collaboration and remote workflows at a price that works for even the smallest of teams, Flow opens up new possibilities for those working in non-EditShare storage environments.”
Avid ISIS/NEXIS - Work-spaces can be used natively by Flow for all the usual operations such as scanning, folder watching, proxy creation, copy/move, and transcode to/from.
Amazon S3 - Archive and restore to and from S3 buckets of all storage classes including “General Purpose,” “Infrequent Access” and “Archive.” In addition, users can move or copy assets between these buckets and storage classes.
Amazon Glacier - Archive to and restore from Amazon Glacier vaults.
Generic S3 - Archive and restore to and from any generic S3 object storage, such as Object Matrix.
Storage DNA - Archive and restore to and from StorageDNA defined Tape archives. Flow proxies can also be shared with the StorageDNA media browser.
EditShare Flow is available in three packages: Basic, Advanced and Enterprise. Subscription pricing starts from 19 GB/25 EUR /29 USD per user, per month (based on a 12-month commitment). Volume pricing is available.
You might also like...
EBU R143 formalizes security practices for both broadcasters and vendors. This comprehensive list should be at the forefront of every broadcaster’s and vendor’s thoughts when designing and implementing IP media facilities.
We continue our series on things to consider when designing broadcast audio systems with the beating heart of all things audio – the mixing console.
In part one of this series, we looked at why machine learning, with particular emphasis on neural networks, is different to traditional methods of statistical based classification and prediction. In this article, we investigate some of the applications specific for…
We continue our series of articles on design considerations for Media Supply Chains looking at the technology trends influencing Ingest.
We begin our series on things to consider when designing broadcast audio systems with the pivotal role audio plays in production and the key challenges audio presents.