Avid Media Composer is not (always) frozen
Tuesday, November 17th, 2026Avid Media Composer is a complicated application that does all sorts of complicated things, and its user interface only surfaces and explains some of its functions to the user as they happen. Sometimes a background task will take minutes or even hours to complete, and the user interface will hang while waiting for a completion message from a background task, and then come back to life once that task finishes. One way to tell whether Media Composer is actually hung and should be force-quit, or if it’s actually busy and you should wait, is to spy on its filesystem activity. On macOS, I’ll usually run this command in a large Terminal window off to the side, just to be able to see what Media Composer is up to:
sudo opensnoop -v -n AvidMediaComposer
If Media Composer is alive and working, you’ll see messages scrolling by that indicate files and folders the application is accessing. Anyone walking by your edit bay will see this and think you’re hacking the Matrix.
So for example, if you’ve opened a large collaborative project after a vacation, and Media Composer sits there with the message “configuring audio waveform cache” displayed on screen for minutes (or hours), and maybe your mouse pointer has even turned into that spinning color wheel animation that bodes ill — run that command and watch what Media Composer is doing. In the case of that “hang”, you’ll see in the output of that command that Media Composer is not sitting idle but is scanning every bin and folder in the project repeatedly.
In the case of that particular situation, you’ve just gotta let Media Composer continue what it’s doing. If you force-quit, remove the MC State, or all the other normal steps I’ve tried, Media Composer will go right back into that same state when relaunched. It just has to finish whatever it’s doing, which typically takes from 5 minutes to 3 hours.
That’s the TLDR;, the short summary. I wrote up a much more detailed and speculative version of the same in an email a while back, and am going to excerpt it here in case any of the information in it is of use to anyone.
The very very long version from an email
Please note: This lengthy writeup may contain some information that is speculative or inaccurate. I reserve the right to be wrong.
I have good news and bad news about the “configuring audio waveform cache” bug. The good news is that after years of fighting this bug I’ve figured some things out. The bad news is that I’ve found no satisfying workaround and the best thing in most cases seems to be to plow through and let Media Composer finish what it’s doing when it sits there on that message. But that’s an oversimplification and I’ll give you the more involved explanation which includes a note on what can bring on the bug and even a terrible workaround.
Two assertions about this bug that I’ll open with to court controversy:
• The bug is not exclusively related to the use of Mimiq (I’ve seen it on bog-standard machines just connected to a Nexis).
• And most counterintuitively — it has nothing to do with the audio waveform cache. I enjoyed being informed of this one recently after spending way too much time over the years trying to figure out workarounds related to that cache.
My current understanding of the issue starts with how Media Composer opens a project. I’ll start there.
The Project .avp file
A project on a local drive has a project_name.avp file at the root of the project directory, and this gets opened when the project is opened. Nice and simple.
In a collaborative project opened on a Nexis however, this single .avp file won’t do, as there might be 10 or 15 users all trying to open and write to that same file all at once –chaotically clobbering whatever project settings and caches are stored in that .avp file. Instead of everyone opening the same .avp file, each user gets their own folder at the root level of the project workspace named after their computer’s name, and inside this folder is stored that user’s .avp file, audio waveform cache, MCState, etc.
I heard an Avid Tech call these folders “user bays” once. I don’t know if that’s the official term but I’m going with it. So for example the machine Sharon-WFH gets a user bay folder named “Sharon-WFH” at the root level of the project workspace, and inside it you’ll find Robocop5.avp. In this example, every user bay contains its own Robocop5.avp. There was a time that I thought Media Composer simply copied the main .avp file into each user bay, but that would be too easy. They’re not copies, they’re individually built, and that building is the pain we’re here to discuss.
The slowdown
When a user opens the project, Media Composer does a bunch of maintenance tasks, including updating the audio waveform cache (the source of that progress bar). After the waveform cache is finished, it starts updating or building that user-specific .avp file. If the project has been opened fairly recently, this process of updating the .avp file is so fast that the delay isn’t very noticeable. But if the project has a ton of folders and bins and hasn’t been opened for a long time (or ever) on that computer, the delay can be considerable. It can appear as if the application has frozen, and I’ve seen it take 5-180 minutes to finish this task. All the while, the “configuring audio waveform cache” message is displayed –not because the audio waveform cache is being configured*, but because that task’s message isn’t cleared before starting the subsequent, .avp building step in the process of opening the Project.
A fun Terminal command to spy on Media Composer
One thing I always like to do when Media Composer is stuck in this frozen-looking state is to run this command in a macOS Terminal, to spy on Media Composer’s filesystem activity. It’s interesting and is also a way to be reassured that the application is indeed doing stuff and is not actually frozen (even though it shows up as “non-responsive” in activity monitor). It’s been helpful for this specific bug.
sudo opensnoop -v -n AvidMediaComposerWhat is Media Composer doing during that delay?
Beats me! What I can see it doing when I run that Terminal command is that it seems to be scanning through every folder and bin in the project, and then it scans through them again, and again, and eventually it finishes up and opens the project. My guess is that the .avp file contains some sort of representation related to every bin in the project. It’s gotta be a fairly small representation though, as a .avp file for an 800+Gb project might be under 40Mb. I’d love to know why it has to scan through all those bins and why it does so multiple times.
When is a delay most likely?
As previously stated, one is most likely to run into this problem when opening a project that has a lot of bins and folders, and if it’s been a long time since the project was last opened on that computer. This can happen on machines connected to any shared storage that are running Media Composer with collaborative features. In fact we ran into it today opening a large project for the first time on a couple of our computers connected to a Nexis, with no Mimiq in sight.
This also occasionally seems to occur seemingly at random every few months on every one of our machines, Nexis or Mimiq. I think Media Composer must decide on occasion to do a more full refresh of the user-specific .avp file, but I don’t know its pattern.
When might a delay be more likely on a work-from-home system?
I would imagine that if this scanning were to occur on a project accessed via LucidLink storage, that it would likely take much longer to scan and build the .avp file than if the project were on local media (or locally-shared SMB shares) or a Nexis, depending on internet speed and how LucidLink’s caching is configured. It could even be that the scan takes enough extra time when files are accessed via this current method that the delay wouldn’t be noticeable on other storage. But I’m just speculating as I have no actual LucidLink experience. There may be some Goldilocks range of project sizes at which the user won’t notice the same scanning process delay happening on local storage but would very much notice it on a LucidLink drive.
There’s also other unrelated weird things that can happen on home networks that can trigger this problem. This might be a rare case but I’ll relate it just in case you run into something like it.
One of our editors (name changed to protect the innocent) kept running into very long “configuring audio waveform cache” delays every few days, even though she’d clearly recently opened the project. She’d still have to wait 90 minutes or so before the project would open. It was only happening to her, and only on her WFH machine. After a week or two of trying to catch this problem as it happened, I finally noticed that she didn’t just have one user bay folder, she had 5 or 6 of them. Instead of just a Sharon-WFH folder at the root level of the project, there was a “Sharon-WFH (2)”, “Sharon-WFH (3)”, on up to “Sharon-WFH (5)”. Each of these folders was its own user bay containing its own .avp file, and each represented her having to wait a very long time while that particular .avp file was compiled from scratch. The reason this happened is that her computer name had changed multiple times.
My guess is that her computer would crash or she’d reboot, and her home router would hold onto the DHCP reservation for her prior computer name for too long and the name would be unavailable. For example her computer would be named Sharon-WFH, and then after a reboot macOS would probably greet her with the message ‘The name of your computer “Sharon-WFH” is already in use on this network. The name has been changed to “Sharon-WFH (2)” automatically’. She’d hit OK on this and think little of it, launch Media Composer, and when she’d open the project Media Composer would see no user bay folder named “Sharon-WFH (2)” and would get started building one and doing its long process of scanning everything to build that user-specific .avp file.
I haven’t seen this computer name issue show up on our work network, so I speculate that it might be related to particular home router equipment and thus is probably more likely to be correlated with Mimiq use even though it’s not itself actually caused by Mimiq.
Failed workaround attempts (many from before I had much understanding of the bug)
• Force-quit and relaunch media composer – it goes right back to the same delay when next opening the project.
• Rename the user bay – back to the same delay.
• Delete MCState and Settings – no effect.
• Copy over searchDBs from someone else’s user folder – back to the same delay.
• Turn off or disable phonetic indexing – not a bad idea since we aren’t using it and it’s cpu intensive, but it had no effect on this.
The path not taken
• I did once suggest that if we had a smaller project with fewer bins this delay would be reduced, but our team finds it useful to work in a more comprehensive project and it hasn’t cause other problems.
Partial workarounds
• If needing to just access a bin, perhaps for a screening that can’t wait for that whole .avp building delay, one can make and open a small or new project rather than the main project. That’ll open quickly, and then just open the specific needed bin(s) from the Finder. One doesn’t have a main project open to open bins that live within that project — and locks still work.
• This one didn’t fool media composer for long, but allowed our editor to get into the main project quickly. Here’s my documentation (paraphrased from my Avid forum post) of this convoluted partial workaround procedure just in case a desperate measure is ever required:
1. I made a copy of the project on another workspace
2. Deleted almost every bin and folder in it so there would be less to scan
3. Deleted the user bay folder
4. Deleted the computer name folder in that project’s AvidSharedData
5. And aimed Media Composer at that project instead of the real one.
It spun up, recreated those folders, did its ‘configuring waveform cache…’ delay but scanned a much smaller number of bins and folders multiple times before finishing, and then it opened the project. I copied the newly-created user bay folders back into their spots in the original project and aimed media composer at it and lo and behold it opened and seems to be working.
This workaround has limitations. The delay was back within a day or two when Media Composer realized it needed to update the .avp file. I don’t know if this process will always fool Media Composer as I don’t know how often it checks or how it determines that a .avp file is out of step with a full project. And it’s possible that using a user-specific .avp file that was created from a smaller copy of a larger project will be missing some information that’s actually important (it’d really help to know just what’s in those .avp files). The editor didn’t report running into any issues.
The real solution
The real solution, or what we’ve settled on, is that we let Media Composer do its thing and finish whatever it feels it must finish. None of the workarounds we’ve found stick, and if we don’t let Media Composer build that user’s .avp file to its satisfaction it always notices and decides to pick right back up and start building it again. But we now know to anticipate this delay and build that into our plans. For example, we have a screening tomorrow and will be using a machine on the Nexis that hasn’t previously opened it, so we opened the project on that machine a day in advance, expecting that it would be stuck at ‘configuring audio waveform cache’ for a couple of hours – and that did happen. But now that it’s gotten through building its .avp file, it’ll open the project without delay tomorrow and probably uneventfully for the next couple of months.


