Macbook M1 Pro

32 GB ram

Avid Media Composer 2022.4 (also tried running the previous version).

OSX 12.3.1.

Machine was working fine yesterday. Today Avid fails to launch. The icon bounces a couple times in the tray and then stops. No splash, no error nothing.

Tried:
Re-installing

Fresh Re Install

Deleting all cache and library files and then Reinstalling

Re-installing from avid link and DNG from the downloads resource centre.

Tried disabling and re-enabling the license.

We've launched both from avid Link and from the media composer itself.

Please help

Have you ever been able to launch Media Compser on this machine? Or has this only stopped working after an OS upgrade for exmaple?

Just to make sure Avid is activated in Avid Link?

It's been working before. We saved went home, and the next morning the software would refuse to work. I'm yet to be able to make it work on the M1 machine again. At the moment we're backing it up to re-install the OS in hopes that this might be the issue. I'm also running absolutely nothing on the macbook aside from avid to prevent any sort of poison in the well.

Made sure avid is indeed active in avid link and also tried openinig from avid link. Also tried a clean re-install of avid link.

Also tried fixing all volumes on the Mac thinking it might be a permissions issue.

Tried getting rid of the com.avid.mediacomposer... file in the library of the mac as well.
Both media composer and avid link have full write permissions on disk.

At the moment I also just heard of doing this fixing of the volumes in recovery mode might have an effect, and then opening avid through opening the project as opposed to the application.

Bit desperate on this one so any ideas i'll try :)

Will keep you posted, and appreciate anything else anybody has to offer.

Found a solution on another forum

https://community.avid.com/forums/t/205700.aspx

Deleting the file under User>Shared>AvidMediaComposer>Avid FatalErrorReports

We managed to launch after that. Hope this helps people!

It looks like this is becoming a common problem, there are numerous threads mentioning this now.

To solve the problem delete the following folder:

 /Users/Shared/AvidMediaComposer/Avid FatalErrorReports.

Thanks for the update. 

Are you able to create a support case? If this issue can be re-created it can be logged and fixed. 

https://www.avid.com/learn-and-support/contact-support

I did have a support case open and mentioned it when I found the solution, but I'm not sure if it was investigated further or not.

The response from support was:

I am glad that the issue has been resolved. There are some instances wherein Media Composer is tricked or stuck from the previous error. By deleting the contents of the fatal error reports, Media Composer does not have anything to scan in that folder.

Many thanks for creating that support case.

Could you give me the support case number so I can escalate this?

Let's face it this shouldn't really happen under any curcumstance...

Sure, case number 04417817

I've scheduled in an email. Thanks

Hi all:

Just experienced the same issue on my Mac Studio.  Deleted the folder, and MC launched, no problem.

Thank goodness for this forum and all the folks sharing info!

Best, JIM. 

Glenno:

Sure, case number 04417817

This case is closed, as the customer was able to launch.  The fix is to delete the fatal error reports folder.

I'm sorry. But no. NO!

The FIX is not delete the AvidFatalErrorReports folder. The WORKAROUND is to delete the AvidFatalErrorReports folder.

Understand there is an issue in Media Composer that is creating an entry in this folder that is then preventing subsequent launches of the application. The FIX would be to figure out what in Media Composer is creating an entry that later launches of Media Composer are hanging up on. Only Avid can create the FIX. We, the users, can only employ the workaround.

My rant of the day.

Will follow up. 

Just echoing what I saw from the support case 

I've been told this issue has been resolved by engineering in the latest version of Media Composer (currently working on 2022.5)

The fix for this particular version (2022.4) is to delete that folder. 

Hope that's okay