Hi Everyone!

So I've been editing a project on a 2022.12 Media composer Qualified workstation for a month with no problems and since today, I don't why, continuing on the same project it starts to hang in a critical way, I can't even open a sequence anymore.

Console shows this message:

BuildPipes Concurrency Alert - BuildPipes starting with BuildPipes in progress!

I didn't change anything in the software, nor to windows, not to the workstation hardware, nor the media in the timeline, absolutely nothing.

Symptoms are hanging indefinitely and/or taking ages to save the only open bin containing just a single sequence in it.

I've searched the forum for this error message and only found people having issues with older versions of MC (like 2022.10) reverting to even older version of MC to solve the problem, but no answer to whhy it happened or how to fix it. 

The thing is I have been using 2022.12 to edit this project without any problem so far, so I don't understand why it suddenly happens.

If anybody could help it would be much appreciated!

Hi there, 

Are you editing with a NEXIS?

Try creating a new Avid project and copying just the bins across to that new project.

Philip Kapadia:

Hi there, 

Are you editing with a NEXIS?

Try creating a new Avid project and copying just the bins across to that new project.

Hi, thank you for your reply! No I'm not. I'll try that and let you know if it changes something 🙏

woutercrusio:

I think the problems arise from not building the waveform correctly on the timeline.

Since using BM for IO's I have always used ASIO 4 all without issues.  During the install of the 22.12.1 version of  MC and probably the previous install of 21.12.7 I was offered a new program for Audio (NewTek??) Sorry I bypassed this opton and promptly forgot about it. 

My working audio Project settings/ hardware still shows as Intensity Pro 4K & 1394 Audio & Direct Sound audio.  IF You installed that new  Audio option it MAY not play nicely if, on my assumption your audio hardware did not update your audio settings to meet any new requirements.

Good luck

I have had nothing but problems since I updated to the newest version becaue of this newtek ndi.  I can use my external monitor through my kona 3G all of a sudden and I am getting all kinds of Audio errors.  

I am editing a bands live performances with 9 video tracks and 4 audio tracks.  I am cutting and almost everytime I stop and make an edit and hit the space bar to play there is like a 10 second delay.  I feel like I am losing my mind here!  

If I am reading your post right you installed the newest version without the newtek ndi?  I have never had a problem with avid or my kona 3G before this update.  Is there a way to remove it?

Philip Kapadia:

Hi there, 

Are you editing with a NEXIS?

Try creating a new Avid project and copying just the bins across to that new project.

So I did that and I'm still having the issue... :(

Todd H:

I am editing a bands live performances with 9 video tracks and 4 audio tracks.  I am cutting and almost everytime I stop and make an edit and hit the space bar to play there is like a 10 second delay.  I feel like I am losing my mind here!  

I'm also experiencing the very same deal, editing a multicam live performance.

I'm getting those messages from the console (although I only have two mono audio tracks on the timeline transcoded from a 44hz WAV file):

[02/13/23-15:59:55:496][tid:13788][WARNING] [QTFFContainerHandler] AAC precharge is less than the theoretical minimum: 0

BinManSaveAll() Individual Bin Save took 5.876893 seconds

BinManSaveAll() Entire function took 5.877617 seconds

BinManSaveAll() Individual Bin Save took 5.743263 seconds

BinManSaveAll() Entire function took 5.744015 seconds

BinManSaveAll() Individual Bin Save took 236.634482 seconds

BinManSaveAll() Entire function took 236.635202 seconds

BinManSaveAll() Individual Bin Save took 5.781071 seconds

BinManSaveAll() Entire function took 5.781737 seconds

[02/13/23-18:36:24:522][tid:17404][WARNING] [QTFFContainerHandler] QTFF 'chan' box' channel descriptions specify unsupported audio channel labels.

Local Disk Cache - PurgeDataToMaintainQuota:

Bytes Purged: 0d

Elapsed Time Milliseconds: 1

Set persistent image cache limit: 200.0 MB in C:/Users/Public/Documents/Avid Media Composer/AvidImageCache

WARNING: Requested LocateBuffer size 63488MB is the same as current size 63488MB.

EDIT: Just updated to 2022.12.1 and still do have the same problem

Any help to solve the problem would be so much appreciated...

Bump & update

So I'm still encountering the issue.

I noticed that the program hangs for quite some time at launch while 'Loading color correction presets'

I've researched the forum for this issue and only found a thread about a user having problems with AJA IO hardware, which I do not have. There's no other hardware or I/O interface connected to this workstation.

I'm still wondering about those messages shown in the Console:

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

CATException[80000008]codecs::FillCTVideoFormat, ..\..\CAT\core\extra\ctop.cpp:208 -> CAT_EXPECT_TRUE( width && height )

MAX_INDEXES_TO_READ set to 10240

MXF Indexes in Memory changed to 524288000: Old Size 524288000

Distributed Processing - Reset SubmitQuery cache

NRCS Tool: use of Qt SSL Socket has been disabled.

In Init ARO Cmds

MTSC state = 0The single frame player will be built for a length of 3600 frames

Viewer: OpenCL and OpenGL are not compatible: No OpenCL devices

MSMRescan() took: 0.070000s

Set persistent image cache limit: 200.0 MB in C:/Users/Public/Documents/Avid Media Composer/AvidImageCache

LocateBuffer Resize from 2048MB to 63488MB

Local Disk Cache - PurgeDataToMaintainQuota:

Bytes Purged: 0d

Elapsed Time Milliseconds: 1

Set persistent image cache limit: 200.0 MB in C:/Users/Public/Documents/Avid Media Composer/AvidImageCache

WARNING: Requested LocateBuffer size 63488MB is the same as current size 63488MB.

Especially that last warning, could that be the problem? And if so, what's the procedure to solve it?

Update : Closing the project also takes ages

I have a "Closing bin window, please wait while the bin is saved" message, looping for more than 20 minutes.

The said bin is the only one open, and only contains 4 sequences.

I'm really going nuts now... :(

Can I check what you system specs are?
Your issue sounds very familar to ours, although we've had it from 22.10 and now repeating in 22.12.1
We couldnt work with 22.10 in the end and went back to 22.7 which worked fine.
We're inbetween projects at the moment so trying 22.12.1 which the same issue is happening all over again.
I've got a support case open with avid on this.
I think it's down to how it's drawing waveforms. If you turn them off, does it behave better for you?

A down and dirty test on one system (22.7) takes 17secs to draw waves on one sequence.
Identical system, running 22.12.1 same sequence, well after 30mins, still hasnt drawn even a quarter of them.

To all those in this thread,

Are you still using 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. 

AntCaladine:

To all those in this thread,

Are you still using 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. 

hi! I actually reverted back to 22.7 and was still having the issue. I'm back on 22.12.1 with the issue and still waiting for a fix 🤷‍♂️

Thanks.

Have you raised a support case via the portal about it?

I have noticed these issues as well. Closing/Saving bins went from taking seconds to minutes or never finishing. Sometimes, if I unplug my network cable Avid will very quickly come back to life, giving me a write failure error message because the nexis link was unplugged. But, at least I can recover. Other times I've had to hard power off and even a few times seen a BSOD with Windows telling me the fauling module was AvidFos.sys. These issues really started kicking off in mid to late January for me.

At this point I've rolled back Nexis to 22.9 and Media Composer to 22.7 resulting in a 70-80% improvement. Haven't had another BSOD but still get many minute long Bin saves. These bins can be very small, 50-100 clips and no sequences. Saved to a local drive takes the blink of an eye, saving to Nexis - let me go down the street for a cup of coffee. Maybe it will be saved by the time I get back.

I am also at a loss to the exact cause but am wondering if there was a Windows update that has triggered this? We have a hundred+ systems at our company. Most of these systems are under tight Windows Update restrictions which keep them 6 months to a year behind Microsoft's latest updates. None of these systems have experienced any of these issues. While we have updated the Nexis client on those systems to 22.12 we have not updated Media Composer. Those systems are still running MC 22.7.

Now my computer, which is used for release evaluations (ala let me test MC 22.12) is always running the latest updates from Microsoft. I do read the Avid Security Guideline document monthly to look for documented problems with Microsoft updates, but no issues have been documented recently.

@timetofilm what file formats are you working with? MXF ?

Think have possibly found the issue with avid support, which is a bug they found back in 21.12.6