Here we have it, too, that MC hangs on closing / quitting the application.

We also have it on NitrisDX machines, so I doubt it has something to do with specific BMD / AJA / openIO whatever...

Some have symphony option , some don´t have it, so there is also no direct connection.

We aren´t connected to the internet and have no browsers than the built in edge.

We are on newly installed HPz840 Wkst, Windows10 Pro 64bit version 1803, 32GB RAM. Interplay / Media Central Production with ISIS 5500 storage, 1GB ethernet connections. We have both BCC and sapphire installed (not newest version) and we have Baselight Editions v5.

The only thing I noticed: the hang on closing the application only happens if the machine was in constant use for a longer period of time (the whole day). It never happend, when you only let it run for a few hours or with low workload. So the more work and the heavier the project was, the more likely it was that MC hangs on quitting the app in the evening :-)

I always knew it, the avid is alive! It just is exhausted in the evening...

Best,

Felix

I tried disconnecting my Matrox I/O box so I'm only running vanilla MC and I still get the problem.   At this point, I think every parameter has been elimated except MC, so it's got to be a bug in the Avid software.

Not sure it has an impact, but the Matrox driver is still installed?

Going on 5 months now with no sollution or a bug acknowledgment by avid..

Is anyone else still having the issie?

JRijken:

Is anyone else still having the issie?

Yes, occasionally...

But I recently updated the BM driver to 11.0.0 and need to see if there's an improvement

FWIW: I've always been on the latest BM driver while having this quirk, whichever it was; then I came across the audio loop at stop bug and rolled back to 10.9.4 in order to fix it, and have bumped into the quit hiccup only a couple of times in a few weeks.

BenoitM:

JRijken:

Is anyone else still having the issie?

Yes, occasionally...

But I recently updated the BM driver to 11.0.0 and need to see if there's an improvement

FWIW...it happened just now....BM Mini Monitor was NOT attached...

JRijken:

Going on 5 months now with no sollution or a bug acknowledgment by avid..

Is anyone else still having the issie?

Of course it's a bug.   From the multiple posts on this thread, it's apparent it happens on Mac or PC, with or without I/O cards, independent of plug-ins...and only started occuring with more recent releases.

It's happening here again, despite the fact that it didn't for a while... :-(

I just want to add that I've found 2 more threads on the MAC side that are reporting the same problem.

http://community.avid.com/forums/p/196730/880294.aspx#880294

http://community.avid.com/forums/t/184495.aspx

We are stille experiencing the same issue, there is still an unresolved case pending, and now at least 3 different threads with dozens of people reporting the same thing... All with different hardware and different software..

2018.12.2 the same.

I don't loose anything it's just won't close by itself.

Can't unload memory.

Happens 40% of the time - has to be manually bombed out.  Its ugly and really should be fixed by now.   Im on 2018.12.2 by now (so crashy - should have left well alone :-( )

Diesele

Happens with AJA attached correct?   both sides are workign on it but it takes 2 to make it right.

Marianna

Ciao Marianna, this is happening with BM hardware as well, any news on that side? I agree with Diesele that an average 40% quit failure is on, quite annoying in front of a client, especially the ad agency kind of guy, usually a FinalCut X addict. :-))

Hi M. I'm running the BM Intensity 4k card.  Thx