Since installing 2022.10 on our systems, we're finding that MC will hang several times a day whilst it clearly thinks about something, and then suddenly springs back to life.

It can be whilst doing anything from marking an in point, to auto save, to starting a render, it hangs for say 15secs with the windows blue cirlce whirling round, then happily carrys on as if nothing wrong and could work for hours again with no issues, or could be the same just minutes later.

As it's across all three systems, since updating. We're thinking it has to be something to do with this version. The GFX driver is the latest recommended, and all editors have created brand new user settings.

Has anyone else experienced the same?

A few things can cause this problem. 

In the past I have solved this by disconnecting offline network drives in windows. 

Also try playing around with your MediaCache settings. 

This must be on shared storage, Is this a site-wide issue or project only?

An offline or online project?

Are you able to downgrade one of the systems back to see if the issue persists? 

Try creating a new project with this MC version and see if the issue persists

Yes in a shared storage environment. Tiger tbox fibre.
We've just downgraded one of the suites, and it hasnt frozen once all day. Yet the same project in a suite with 2022.10 has frozen several times so far. 
Its a new project, newly created user settings, media cache the same in all suites.
Its very odd behaviour.

I just upgraded today and have been having this problem consistently all day.  According to the console it seems to be hanging while saving an individual bin.  Here is an example of what it says after hanging:

Exception caught in APlayer::Play - Exception: RawAudioConsumer::Execute() time out

Exception caught in APlayer::Play - Exception: RawAudioConsumer::Execute() time out

BinManSaveAll() Individual Bin Save took 25.560524 seconds

BinManSaveAll() Entire function took 25.560809 seconds

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

I am working on a Mac Studio / 64 GB ram / MC 2020.10. and I am remoting into that machine using Jump Desktop from an iMac but I don't think that factors into this.  

There were no theories to any of the above issues?

sjc_nyc:

I just upgraded today and have been hacing this problem consistently all day.  According to the console it seems to be hanging while saving an individual bin.  Here is an example of what it says after hanging:

 

Exception caught in APlayer::Play - Exception: RawAudioConsumer::Execute() time out

Exception caught in APlayer::Play - Exception: RawAudioConsumer::Execute() time out

BinManSaveAll() Individual Bin Save took 25.560524 seconds

BinManSaveAll() Entire function took 25.560809 seconds

I think this is the best clue.  Great work!  I have seen some random slow downs saving bins on 2022.7, but only when I explicitly do the save.  And on a Mac with simple DAS.  I still think it is related.

Jef

jUST SWITCHED TO THIS VERSION AND AM GETTING SLOW SAVES/HANGS too.  A Save to a 7000mbps SSD can take 15"! This on a brand new standalone system with v fast drives/M2 SSD.

I am also getting many issues with audio waverforms - its is slow to draw them and sometimes never completes them. I videoed the flurry of eventual too fst to read pop ups when it does complete a save and it stated 'Initializing Format Pane' + 'Scanning Dependent Objects'.  Its all a dealbreaker and will revert to 2018.10 on my dongle unless there is any good news...

I've given up on 22.10 and went back to 22.7 everything is so much better. 

I'll look at trying 22.12 in the new year at some point.

I commented above about this issue last month as well and today tried upgrading to 2022.12 but had the same hanging issue when saving a bin.  It was constant, with every automatic bin save.  I have reverted back to 2022.7 which seems to be fine for now.

I copied some of the console info here:

Exception caught in APlayer::Play - Exception: RawAudioConsumer::Execute() time out

Exception caught in APlayer::Play - Exception: RawAudioConsumer::Execute() time out

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

BinManSaveAll() Individual Bin Save took 27.394077 seconds

BinManSaveAll() Entire function took 27.397281 seconds

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

BinManSaveAll() Individual Bin Save took 18.815826 seconds

BinManSaveAll() Entire function took 18.816132 seconds

We now tried 22.12 and 22.12.1 and this is still a major issue for us.

I can replicate it quite quickly when waveforms are swicthed on. Switched off, it behaves ALOT better. It still happens just not as much.
But waveforms on, we can hang avid by just opening file explorer, navigate to any folder, then click back into avid and it hangs for 20secs before coming back to life.
Even tried disabling AMA management which made no difference.

We have two identical systems that behave the same, a third we left at 22.7 which is fine.

This weekend I've done a full format/reinstall of a suite from scratch which has made no difference to the hanging.

Its a head scratcher.

I had this on 22.10 but also on 22.7 where the screen would washout white and sit there for up to 30 seconds or more, waiting for something to happen.  Most of the times it did but some required a crash-kill via task manager.   Not great. 

To all those in this thread,

Are you still using 2022.10 or 22.12 and/or 22.12.1 or have you reverted backwards?

I've an open case with avid support, who are really struggling to replicate anything their side in terms of issues with it.

I've 3 systems that I can replicate faults on, almost instantly. I've sent blackbox records, mcfax reports, all from multiple systems, and even sent avid some of my mxf files, but still hitting a brick wall.

We've done all the usual suspects, new user, delete mc state, cleare bin caches, local project, local media, one system we've even formatted and reinstalled windows etc from scratch.

I think its waveform related, but might be MXF files too.

Just trying to work out whats common to us all.

22.7 works fine, but anything after that is unusable to us.

If anyone has any suggestions, or wants to raise their own case via the portal please do. 

Mine seems to have sorted itself out. Or maybe it's post handover projects and am working on projects created on the new system now? 

AntCaladine:

I've 3 systems that I can replicate faults on, almost instantly. I've sent blackbox records, mcfax reports, all from multiple systems, and even sent avid some of my mxf files, but still hitting a brick wall.

That sounds exactly like my experience reporting performance issues in MC 2020/2021 in Interplay/Mediacentral production environments.

It has taken Avid 1-2 years to acknowledge and indicate implementing all fixes in 2022.12.1 but I haven't been able to test yet.

I have asked Avid support management and L2 support to invest in Media composer hardening and error reporting improvements because the current situation looking for 'outside of Media composer' problems after sending logs, MCfax, collects etc... like pointing unsupported components, network related tests, windows updates, driver updates, delete mc state, clear bin caches, delete settings, using a local project, local media.. also formatting systems are just a waste of time and contribute to the perception of participating in a involuntary beta testing program.

I hope more users will request improvements in error reporting and collection of logs so we, together with support, can produce tangible information for the engineers to work with.

... we can't replicate... but fixes start appearing after xx months/years. 

Can I check what footage poeple are using, when avid freaks out?

We're using MXF files from FX6 and FX9 cameras.

Bizarrely MXF files from FS7 are fine.

Projects with other media like prores/mp4 seem fine too.

All works ok in 22.7.