[Jake Shaver]

Removing any blackmagic drivers seemed to eradicate the error on every computer experiencing the issue.

[Jake Shaver]

Avid has been having a little trouble solving this issue for me and I think I might have been wrong about the project jump theory. One thing that has so far alleviated the issue is installing the newest blackmagic drivers that were released on 12.24.14 and update to Avid 8.3. After we me all of these updates the computers have not had this error.

Hope this helps.

-Jake

[Jake Shaver]

Nothing official from Avid yet but we’ve pretty much boiled it down to the fact that we’re opening 6.5 projects in 8.2 because all of our freshly made 8.2 projects are running just fine.

A few things I’ve done to alleviate the issue:
If you can, rebuild the computer from scratch. I put in a brand new hard drive and started with a fresh OS build and worked my way up from there.

Remake your user settings from scratch.

Remake any old projects you’re trying to bring up to 8.2. So, start a brand new project in 8.2 with a similar name, make all new bins with similar names (I added
_NEW to everything in the 8.2 project), open all the old bins via “open bin” and move everything from that bin over.

If you have a little time on your hands and not such an abundant proejct you could even make new sequences and copy the content from old sequences to new.

If I hear anything I’ll keep this thread posted…

-Jake

[Jake Shaver]

Hi Mara I’ve started an email chain with Avid support about this exact error and nothing has been resolved yet. I’m curious if you ever come up with a solution?

Running Avid 8.2 OSX 10.9.5 24gb 133 MHz DDr3, 2 x2.66 GHz 6-Core Intel Xeon Mac Pro