"Audio processing deadline was not met"

[Arno Peeters]

Originally Posted by smurfyou

Did you do any sort of migration or a clean install of everything?

I usually migrate but I decided this time to go clean. And I was pretty brutal, cutting out any plugin or software I hadn't used recently no matter how much I liked it. Not saying it actually makes a difference or should be necessary but a thought.

I migrated, which still was a lot of work upgrading, version-checking, housecleaning and what not. But other than that all seems fine: no other oddities on my system (at least AFAICT).

[anackman]

This error is still occurring frequently on my end. Anyone else? Happens with Arturia plugins, Omnisphere, and Addictive Drums, from what I can tell, but there have been some inconsistent moments with this error. Either way, it's a creative killer.

Would love some further advice.

[marianna]

Originally Posted by anackman

This error is still occurring frequently on my end. Anyone else? Happens with Arturia plugins, Omnisphere, and Addictive Drums, from what I can tell, but there have been some inconsistent moments with this error. Either way, it's a creative killer.

Would love some further advice.

Same exact error message as Arno is getting?

Marianna

[tope d]

Originally Posted by anackman

This error is still occurring frequently on my end. Anyone else? Happens with Arturia plugins, Omnisphere, and Addictive Drums, from what I can tell, but there have been some inconsistent moments with this error. Either way, it's a creative killer.

Would love some further advice.

I've seen a similar case.
Please check the following:

In some cases, these issues are caused by an incompatibility with certain third-party plug-ins.
>Press and hold the "Shift" key while double-clicking the session file to open it. This will result in the session opening with all the plug-ins inactive. You can then make each plug-in active one by one to see which plug-ins cause the issue to reoccur after saving/closing/reopening

> Try removing all plug-ins from the Plug-ins folder (see below for location) or simply rename the Plug-ins folder so that a new, empty one is created on the next launch:
(Mac)
Macintosh HD/Library/Application Support/Avid/Audio/Plug-ins
Move plug-ins back into the Plug-ins folder a few at a time to determine which plug-ins are the cause of the problem.

>Try the following:
1. Go to your Pro Tools plug-ins folder:
Mac: Macintosh HD/Library/Application Support/Avid/Audio
2. Move the Plug-Ins folder to the Desktop.
3. Create a new Plug-Ins folder:
Mac: Simply launch Pro Tools and it will automatically regenerate a new Plug-Ins folder with its pre-installed plug-ins. Close Pro Tools once it's fully loaded.
4. Move plug-ins to the new Plug-Ins folder in batches (instead of moving them all in one go). For example, move 10 plug-ins at a time to monitor if any specific plug-ins may be causing the crash:
Open both the new Plug-Ins folder and the old Plug-Ins folder.
Move a few plug-ins from the old folder to the new folder
Each time you move a batch of plug-ins, launch Pro Tools and verify it can launch successfully.
If it launches, quit Pro Tools and move another batch into the new Plug-Ins folder.
Repeat the process until you've moved all of your plug-ins and have launched Pro Tools successfully.

[anackman]

Originally Posted by marianna

Same exact error message as Arno is getting?

Marianna

Yes, same message, different plugin mentioned.

[Arno Peeters]

Yes, unfortunately it does not seem to be tied to one specific plugin or even a brand and certainly not always heavy consumers: it happened to me with Acon Verberate Basic, a very simple reverb plugin. The only thing I noticed is that is mostly the last plugin on a track.
I'm afraid it lies somewhere in PT's architecture, maybe specifically on M2?
Btw: I did all those troubleshooting steps and the only thing that changed is the slow loading times of the plugins and that PT feels a bit more snappy, but the error keeps occurring.

[anackman]

Originally Posted by Arno Peeters

Yes, unfortunately it does not seem to be tied to one specific plugin or even a brand and certainly not always heavy consumers: it happened to me with Acon Verberate Basic, a very simple reverb plugin. The only thing I noticed is that is mostly the last plugin on a track.
I'm afraid it lies somewhere in PT's architecture, maybe specifically on M2?
Btw: I did all those troubleshooting steps and the only thing that changed is the slow loading times of the plugins and that PT feels a bit more snappy, but the error keeps occurring.

This 9173 error has been happening with me since the last 3 Pro Tools versions they've released. It does happen more so with heavy load midi instruments for me than with straight plugins (EQ, Verb, Comp, Delay, etc), but the patterns can be all over the place.

The error just stops you in your tracks and it's very frustrating. With a client, it's even worse.

[smurfyou]

I still get it too, but as I said earlier in the thread I also got it on my Intel Mac with PT 2022 so not a recent issue nor limited to M2.

I scrub a lot and sometimes I think it's tied to that but then it will happen randomly on playback.

[Songster]

Just an FYI .. this is definitely a Pro Tools issue. I'm using a Window's 10 machine, and it doesn't matter the size of the session. it's been happening for a couple months now and never had it happen before. It also comes up with different Plugins so it's not a plugin issue.

Please help us and get this fixed.
Thanks
Nick

[Arno Peeters]

Exactly my experience. Had Avid also look into it and they finally advised me to make a new user to see if it still occurs there. I had to explain that amidst all the work I do, I don't have time to literally make all settings again (shortcuts, presets and the like).