CTM Solutions

Adobe is planning to end-of-life the Flash Player at the end of 2020

The below notification was sent to all MediaCentral | Asset Management (Desktop and Cataloger) and MediaCentral | UX product owners.

As you know, software products reach the end of their life cycle for any number of reasons, including market demands, technology innovation, and replacement by functionally richer solutions. Open standards like HTML5 have matured over the past several years and provide many of the capabilities that the Adobe Flash Player has provided. Given this progress, and in collaboration with several technology partners– including Apple, Facebook, Google, Microsoft and Mozilla –Adobe is planning to end-of-life the Flash Player at the end of 2020. They’ve recommended that contentcreators migrate existing Flash content to new open formats.

Avid has been considering how this will impact our customers and how we can continue to provide best- in-class capabilities in our products where the Adobe Flash Player had been deployed. We have determined that a solution based on HTML5 is the best path forward. The products that are affected are MediaCentral | Asset Management (Desktop and Cataloger) and MediaCentral | UX.

For MAM Desktop users, the migration path will be to HTML5 with Chrome on both Windows and MacOS. Internet Explorer 11 on Windows, and Safari on Mac OS systems will no longer be supported. Cataloger will also move from Flash Player to HTML5.

Avid will provide the required software updates via a patch release during Q3 2020. The patch will provide what is necessary to migrate to HTML5. The MediaCentral | UX 2.10.x upgrade will be a light upgrade patch. It will not be backward compatible to prior versions, and it will not support file-based playback.

It is important to understand that those of you using older versions of MediaCentral | Asset Management will be required to upgrade to a newer version that is compatible with the patch.
Specifically:

- There will be no patch support for Interplay MAM 5.8 or earlier

- Customers on MediaCentral | Asset Management versions 2017.1 (build version 6.0) thru 2020.4 (7.4) must upgrade to the major release 2020.7 (7.5) + Q3 2020 patc

The chart below describes the migration paths from various versions.

__________________________________________________________________________________________________

_________________________________________________________________________________________________

We will be working with selected customers for targeted testing to ensure that the solution works well in a cross-section of environments. However, it is critical that you begin now to develop a plan to upgrade your Avid products to avoid being affected by the Adobe Flash Player end of life. With support and security updates no longer being provided by Adobe and the major browser providers, you could potentially be leaving yourself vulnerable to operational issues and security breaches.

If you have any questions, please contact your account manager or send an email to AVIDFLASH@avid.com 

Thanks everyone.....

Marianna

Great News!!!!!!!    We are happy to report that Avid’s Editorial Management version 2020.4 is now available as of April 23, 2020.  

This release introduces the ability to install alternative languages for Phonetic Search and the ability to install Media Composer | Distributed Processing Engine. 

Documentation:  For details please check the MediaCentral | Editorial Management v2020 documentation page for the following:

Avid MediaCentral | Editorial Management ReadMe v2020.4  

Avid MediaCentral | Editorial Management Installation Guide v2020.4 

Avid MediaCentral | Editorial Management User's Guide v2020.4

FAQ:  A list of frequently asked questions can be found here:

This version is recommended for all currently installed Editorial Management systems”.

Questions, let me know.......

Marianna

Hello! I want to use some npm modules, such as request (https://www.npmjs.com/package/request), soap (https://www.npmjs.com/package/soap), and some other. But I have got compilation error. Can I use npm modules in plugin environment?

Hello! I want to create request to IPWS API, from plugin environment, but I have got CORS policy error. Any ideas how I can fix it? Please see screen in attachment

Hello! I want to add action to Browse App. How I can do it? There are ‘places’ and ‘filter’ properties (in action binding config). For 'places' I take ‘contextMenu’ and ‘viewMenu’. But what I should use for ‘filter ‘? If I use plugin id, action displayed only plugin window.

http://developer.avid.com/mcux_ui_plugin/clux-api/actions-api.html#Action-Binding-Config

In September 2019 I created 40 post-production suites powered by MC2019 and supported by MediaCentral Cloud Ux, Interplay Production, Phonetic Research, Remote Ingest, Avid Nexis Storage and plus from Media Composer Cloud; never as in this historical period all this has been key in getting on with the job.

In Italy, we are the largest post-production facility among private companies, excluding enterprises. We are a modern post-production company that fully responds to Avid Everywhere's request.

From day one it was immediately clear that the possibility of searching and sharing through Media Central Cloud Ux and Interplay were truly a step forward.

Media Central Cloud Ux is a young project; it has some imperfections and still requires development but there is no doubt that your team is doing well and each new version has brought new benefits.

In this wonderful world, the only discordant note is Media Composer 2019.

I don't understand why in order to introduce a more modern UX, you had to undo all the previous developments that took years to implement!!!

Given that getting a feeling with a UX is a personal objective and that one can like or dislike it, I am asking if you have ever tried and tested MC2019 before distributing it? Have you tried MC2019 in the real world? Have you ever edited a video with MC2019?

Float Panels, Bin Container and Workspace are all great but they don't function properly and they destroy the work I do.

We edit complex videos, not news, not promos. Our timelines have 10 video levels, 30 audio levels, have a duration of 100 minutes and present about 13000 items.

Have you ever tried MC2019 with this type of content?

The new features of the UX you care so much about, has made Media Composer unable to work properly.

Do you know that MC2019 cannot export an AAF in any way if its contents are complex timelines?

Do you know that MC2019 is unable to consolidate a complex timeline?

Did you know that in 1996 it was possible to make complex consolidated timelines with Avid Film Composer 7.1 without any problems and that in 2020 the software is no longer able to do them?

And the list of things that don't work is so long that the forum doesn't have enough space.

Media Composer 2019 has made our job so complicated and we have managed to get by, only because we know our job well!!

I apologize for my outburst but I really care about you and I wouldn’t want you to make more mistakes, but MC2019 must be rewritten! As it is now it cannot work properly in the real world.

In the meantime, I am forced to use MC 2018.12.10 in all my suites. And that was by far your best project.

Dear Avid,

This is a feature request regarding media indexer functionality in an Interplay media indexer NOMI HAG. In a NOMI HAG a media composer media indexer client seems to query only 1 media indexer for the media location on a Nexis storage. If for whatever reason one of the media indexers in a HAG is out of sync, for example because it crashed, there is no way for an administrator to stop the clients using that media indexer except by removing it from the server hostname setting on the interplay engine/removing it from the HAG/shutting the media indexer down. Would it be possible for the media composer/media indexer client on a media composer or mediacentral server to request the file locations on all available media indexers in case the media is reported as offline by one of them? That would make managing/updating/restarting media indexers much more easy in an 24/7 in use system with lots of clients. 

It seems that the architectural design is currently based on the assumption that all media indexers in a HAG always have the correct media location information and that querying 1 available media indexer is enough and the ability to manually select from which media indexer on the client is not needed.

Best regards, 

I'm an editor working on an archive-based documentary series (5 Media Composer cutting rooms running 2018.10.0) using the Interplay system. This is my first time using Interplay, so I'm not very au fait with its capabilites/limitations.

Given the current escalating situation with the coronavirus, I think we should be planning for working from home.

What are our options?

Would the simplest - albeit low-tech - solution be to just copy all Avid media files and projects to external hard drives and then just plug in at home? (I'm guessing there's in excess of 10TB of media.)

Can we just run plain vanilla Media Composer at home and access the media? I seem to remember there are restrictions with Interplay licenses. But if we have moved all the media onto external drives, does that restriction apply?

Any suggestions most welcome.

We have just upgraded to the newest version of MC-EM and I just tried to do a search inside Media Composer. I got some results of things I have created since the upgrade. Does EM not search all older projects? Is there something i need to do to make it search my entire "projects" folder?