My experience of MC 2019.12 is pretty stable except for one recurring error that crashes my system at least once a day.

I've been unable to pin down the exact cause but it seems to usually happen when scrubbing over clips with FrameFlex or Pan and Zoom effects applied. All my footage came in as UHD and I have the project knocked down to 1080p/25  

Is anyone experiencing the same and if so, any solutions? My currently solution is to force auto-save every 2mins so I don't lose everything once Media Composer goes into an unrecoverable crash

Systems specs as in my profile

Same error here in 2020.4 . When moving a clip with s a non-project-framerate from V2 to V1 

I don't know if our errors are related, but perhaps this helps - Avid support advised me to do the following:

With Media Composer closed:

- Go to C:\Users\Public\Documents\Avid Media Composer\Settings and remove MCState, Site Settings.xml and Site_Attributes. 

You can move these files to a backup folder/another location.

- Go to C:\Users\Public\Documents\Avid Media Composer and rename the AMA Management folder to AMA Management_old

- Go to C:\Users\Public\Documents\Avid Media Composer/AvidSourceBrowserCache and delete the OPFrameGenerator.db file

- Go to C:\Users\Public\Documents\Avid Media Composer/AvidImageCache and delete the files

 (you can move them to another location outside of the AvidImageCache folder)

Next, launch Media Composer and create a new Avid User Profile. 

It seemed to solve the problems I had with 2019.12. I've since upgraded to 2020.4 

and I haven't had that specific error pop up again. 

EDIT: sorry for the weird fonts...trying to post this from my phone

Corne Scheepers:

I don't know if our errors are related, but perhaps this helps - Avid support advised me to do the following:

With Media Composer closed:

- Go to C:\Users\Public\Documents\Avid Media Composer\Settings and remove MCState, Site Settings.xml and Site_Attributes. 

You can move these files to a backup folder/another location.

- Go to C:\Users\Public\Documents\Avid Media Composer and rename the AMA Management folder to AMA Management_old

- Go to C:\Users\Public\Documents\Avid Media Composer/AvidSourceBrowserCache and delete the OPFrameGenerator.db file

- Go to C:\Users\Public\Documents\Avid Media Composer/AvidImageCache and delete the files

 (you can move them to another location outside of the AvidImageCache folder)

Next, launch Media Composer and create a new Avid User Profile. 

It seemed to solve the problems I had with 2019.12. I've since upgraded to 2020.4 

and I haven't had that specific error pop up again. 

EDIT: sorry for the weird fonts...trying to post this from my phone

Corne......

Let us know if this did the trick as it did on 2 others with the same issue.  

Hope you are well....

Marianna

Thanks Marianna, will do. I haven't been on 2020.4 long enough to tell for sure, but I'll report back the moment I see a repeat of this error. So far none of the issues I had Aleksandra take a look at has resurfaced

I had the same issue. I just followed the instructions. I will keep you updated in the days to come.

We've had RTTI errors on v 8.8.x and found moving the nablet folder out of the AVX folder (with Media Composer closed) works.
nablet lives here:c:\Program Files\Avid\AVX2_Plug-ins\AMA\nablet
It would be interesting if those with the RTTI error and later MC versions could try that for a day or two and see if it makes a difference.

N Ryan:

We've had RTTI errors on v 8.8.x and found moving the nablet folder out of the AVX folder (with Media Composer closed) works.
nablet lives here:c:\Program Files\Avid\AVX2_Plug-ins\AMA\nablet
It would be interesting if those with the RTTI error and later MC versions could try that for a day or two and see if it makes a difference.

Thanks for your reply. I've had this error randomly reappear once or twice since, so I'll try this and report back 

Hello, same problem here again. Moving Clip from V2 to V1 - crash. It was an internally created BCC Pan&Zoom with a photograph, so no different framerates. I did the Settings deletion thing and deleted the cache (there were about 40 images in the folder). The error has gone (for now) and on top there is an increase in overall performance. 

Well - it is not fixed. I got the error after mapping "Add Edit" to F8 and then just audio mixing two music tracks. Before adding the "Add Edit" it worked. This is annoying.

Sadly I have to report that I'm also still experiencing random crashes.

I've been unable to pin down an exact cause, however Frameflex seems to be a likely candidate on my system. I've had a number of crashes occur when trying to trim clips with FF applied. Not sure if it is related to this specific error. My workaround currently is to turn off monitoring on the track before trimming.

Hey Corne.....

I do know that RTTI data is deep in the bowels of Windows and the C++ runtime libraries. Of course, this error could be thrown by some Avid code attempting to access the RTTI data.  RTTI = Run Time Type Information

I can check with engineering but............ let me check with the Frame Flex guys too........

I wonder if monitoring on the track has  tried to use the feature and it requires run-time type information without enabling run-time type information. Recompile with /GR    

what version are you using of MC?  2019.12?

Marianna

Hi Marianna

I'm on 2020.4. Latest version. See my profile for my system specs. The last couple of crashes were most definitely due to me having tried doing something to clips with Frameflex on them

Hi Corne & Marianna,

no FrameFlex on mine.