Pro Tools and 9093 Errors

[Stephen333]

Originally Posted by arche3

If its not Virtual Instruments. Just plug ins. You have to find the one or few that do this. I can almost guarantee its one of your plugs.

Sent from my SM-G986U using Tapatalk

Thats certainly what we thought at first, but this issue has survived fresh installs and a slew of updates to all the plugins so I feel like it would have showed itself by now. The closest we can get is that certain Acustica plugs some of the time really don't play nice on auxes downstream like the mix bus, which is understandable, but still would have that there would be a solution by now or at least some insight from Avid letting us know that was the reason for our poor performance.

We must have shared at least 4 Ktraces with Avid by now as well as sending them a session or two to show them the issues.

[Benny_Cha_Cha]

I get a whole bunch of these errors too and have on and off for a long time. I too have tried all those things on the OPs list as well. Could be plugins, idk. I’ve tried it all ways. And it’s happened to me over multiple versions of PT and two computers, a 5,1 Mac Pro and a i9 2019 MacBook Pro.

Just wanted to point out a behavior I’ve noticed. One is that I can often kick up an error if I switch to an app other than pro tools, but specifically Firefox. It seems to have to do with graphics or something else going on when I switch.

Still missing 7.4 tbh. Should be getting way more stable software for a $400/yr “it’s not a subscription, but it’s the only way to get bug fixes”.


Sent from my iPhone using Tapatalk

[Benny_Cha_Cha]

I’m also curious if anyone has upgraded to Waves 12 and if this has had any effects. I’ve often wondered if having that mix of 9, 10 and 11 is causing issues, esp since the v9 plugins are so old at this point.


Sent from my iPhone using Tapatalk

[Stephen333]

Originally Posted by Benny_Cha_Cha

I’m also curious if anyone has upgraded to Waves 12 and if this has had any effects. I’ve often wondered if having that mix of 9, 10 and 11 is causing issues, esp since the v9 plugins are so old at this point.


Sent from my iPhone using Tapatalk

We're holding off on the Waves 12 update for now as I've seen some instability examples. For what it's worth, we've upgraded our waves licenses to all be 11 after being the sort of mix you are talking about here and haven't really seen any difference in performance.

[The Weed]

I'm on Windows and updated my Waves from v11 to v12 last night. When I Trashered Preferences, Databases and Plug-ins and rebooted and opened Pro Tools I got an error - sorry can't remember what it was, but it was an OS error, not a PT error. Closed out the error, PT opened fine, all my Waves were in sessions, with the proper settings and PT played fine. Closed PT, rebooted, reopened, error, close it, PT opens and plays fine.

Then I remembered on the Waves site when updating, it mentioned not having v9, v10, and v11 active. So I went to the Waves folder in Programs (x86), made a folder called Old Waves and put everything not v12 related in there. Pro Tools now opens up with no error and all seems fine. I do have an image I can go back to if that changes anytime soon. Images/clones save so much grief.

[Stephen333]

Something else to note that I didn't mention is that we've been experiencing these types of errors for a long time now, going back to our old trashcan Mac. Of course, that didn't have the specs of our current Mac Pro but we were experiencing the same issues. In fact, even before we downloaded Acustica 9093 errors plagued us, and we thought that getting a new machine would solve all of the problems, instead of put a band-aid on them like it did. Our performance maybe slightly improved, but the same issues are still there, only now we were using even less of our machine.

[Rectifried]

Throwing ,ram cpu $$$$ ,at Protools never gives much return

[Marsdy]

I’ve been seeing it for a long time both on a Trashcan and 7.1 nMP. For me it only happens once on opening a session and less often on the 7.1. When it does happen it’s always 20 to 30 seconds in from first pressing play immediately after the session has loaded.

Curiously I’ve recently added an instance of NI Massive X to a session. Ever since, PT freezes for about a minute after loading the session. If I remove Massive X it loads fine. The point is, this session hasn’t thrown up the 9093 error once sine adding Massive X. By the time PT has finished being frozen by Massive perhaps it has gone past the moment when it would have thrown up the 9093? So I’m wondering if the 9093 could be related to cacheing the session some way or something PT is doing in the background just after a session is loaded.

[Stephen333]

We definitely have the occasional problems with sessions not caching in, but those are usually always dealt with before going to far, just to make sure that everything is optimized. Definitely another issue for Avid to look at.

[Stephen333]

Also, something else to note, this 9093 error problem rears its ugly head in a very specific way sometimes. We will have a session that is hitting the ceiling and in the red of the system usage meters (as all sessions find their way toward hitting now), but the song will be playing back pretty fine without too many errors, definitely in the world of usable, but as soon as I start either A) soloing tracks, or b) muting VCAs to effectively solo groups, the error is unavoidable. Like every time you hit play it may make it .5 seconds, or 10 seconds, or 15, but it's that error message is coming. Another interesting item of note is that when using hardware inserts the performance is actually very slightly improved, but only slightly.