Pro Tools and 9093 Errors

[Benny_Cha_Cha]

Another thing I’ve noticed is sometimes the session will run fine for a while and then the errors start happening. A Pro Tools restart buys some time but it happens again.

[Carl Lie]

I can say it's a given that any project I open, when I first hit play I get an error. Same will happen if I come to a part where a new instrument plug comes in.

It's extremely disappointing that you are having problems with a powerful computer. My plan was to do the same in terms of upgrading and I had the same expectations as you.

Now not so sure.

C

[Ru_C]

Originally Posted by deanrichard

This seems like something that should be reported back to the engineering team at Avid somehow. The hardest bugs to find and fix are intermittent. This might provide an important clue that could help them fix it if it's a driver conflict of some sort.

Sorry just saw this reply, yeah I think its pretty relevant to the source of the errors, but as this is a 'Hackintosh' system, I'm not sure that AVID would be interested.

[musicman691]

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

A couple of weeks ago I started reworking all my Beatles covers to bring them up to snuff. Add that in the last few months I've been working with having a console emulation on every track to make for a cohesive sound and in that I try and use as close an emulation as I can to what was used on the original songs back in the day.


In this case it's been using the Abbey Roads consoles from Waves. Specifically the TG12345. 15-20 tracks each with an instance of the TG12345. Hit play, goes for maybe 5 seconds before the cpu meter goes solid red and I get noises (not music) and 9173 error. If I remove all instances of said plugin the session plays fine. Can't just bypass it and things are okay - deletion is the only thing that works. If I use Waves NLS and use Mike's console which is a TG12345 on every track - no problem.


This is on the system in my profile where I can run 60+ track sessions no problem. I don't have any Waves V12 but a mix of 9/10/11.

[budster]

I have just built a system from scratch. MP 5.1 12 core w/24GB ram, running High Sierra, PT Ult 2020.11 with HDX 2. I had only Avid, McDSP and iZotope RX8. 9093 issues. Installed Waves 9.92 Platinium, same issues.

The errors seem to be random. CPU has plenty of room, pushing both HDX cards.

[Mark Angus]

Bumping this thread as it seem relevant to me.

Mac Studio running 12.6.1, PT 2022.5 and an Omni via Thunderbolt HD Native.

Every few days I get a -9093 on opening PT for the first time and hitting Play. Sometimes a similar error about the video engine or CPU. The only solution seems to be a full restart of the computer and power cycling the Omni. Once it works it will work all day with multiple sessions.

It feels like an initial hardware sync issue. I know the Omni is an ageing beast but it should still be reliable.

[musicman691]

Originally Posted by Mark Angus

Bumping this thread as it seem relevant to me.

Mac Studio running 12.6.1, PT 2022.5 and an Omni via Thunderbolt HD Native.

Every few days I get a -9093 on opening PT for the first time and hitting Play. Sometimes a similar error about the video engine or CPU. The only solution seems to be a full restart of the computer and power cycling the Omni. Once it works it will work all day with multiple sessions.

It feels like an initial hardware sync issue. I know the Omni is an ageing beast but it should still be reliable.

First thing to look at are the driver(s) compatible with your system? I'm talking both for the enclosure you have the HD Native card in as well as for the card itself and Omni. For that matter is the enclosure itself compatible with the ports on your Mac? As I understand it the Thunderbolt 4 ports aren't completely compatible with some earlier TB versions.

[Mark Angus]

Originally Posted by musicman691

First thing to look at are the driver(s) compatible with your system? I'm talking both for the enclosure you have the HD Native card in as well as for the card itself and Omni. For that matter is the enclosure itself compatible with the ports on your Mac? As I understand it the Thunderbolt 4 ports aren't completely compatible with some earlier TB versions.

I'm on the latest HD Drivers as far as I know, and Omni firmware. The Native card is the Thunderbolt one so is connected via a TB2/TB4 adapter.

It may be that the Mac Studio TB4 bus isn't totally happy with the TB2 connection. What's odd is that it does work most of the time!

I'm holding off an update to PT until we get a stable native version so I doubt I'll find a solution in the meantime.

[musicman691]

Originally Posted by Mark Angus

I'm on the latest HD Drivers as far as I know, and Omni firmware. The Native card is the Thunderbolt one so is connected via a TB2/TB4 adapter.

It may be that the Mac Studio TB4 bus isn't totally happy with the TB2 connection. What's odd is that it does work most of the time!

I'm holding off an update to PT until we get a stable native version so I doubt I'll find a solution in the meantime.

Your problem is that TB4 and TB2 are not compatible with each other. Go about half way down on this page for the answer: https://www.cablematters.com/Blog/Th...rds-compatible

[Mark Angus]

Possibly, although others seem to be using HD Native Thunderbolt with TB4 -

https://duc.avid.com/showthread.php?t=419509

I suspect your article above is talking about cables rather than protocols. However, it may still be a compatibility issue, just not a consistent one!