So, like many on this forum, I was having the extremely hard to diagnose problem of getting -9093 errors shortly after hitting play even on small sessions. When I opened up PT's CPU Usage meter, I could see random CPU spikes even when the session wasn't playing. Then I closed the session and could still see things going crazy in the CPU meter with random spikes hitting 100%. My system is an Echo Express III-D holding a PT Native PCIe Card, UAD Octo card and a Sonnet Tempo Pro holding 2 SSD cards. I was getting these errors on my new quad core 2013 mac pro (PT 11.1.3 with OS 9.1.2) and, when I plugged in the exact same system into my 13" retina (PT 11.1.2 on OS 9) everything was fine.
There's been a number of threads about this and a number of frustrated people trying to get Avid to acknowledge that there is a problem on their end somewhere and to do a little testing instead of just blaming 3rd party plugins (or the computer running the system).
Here's a couple responses from a moderator showing quite clearly they don't feel that their own software is to blame:
Well, I think that I have found the solution - it solved it on my system but I can't say that it's "the fix" until others try it with success which is why I'm starting a new thread.
The problem, of course, could be created with some 3rd party plugins but, regardless, it is absolutely created if you have Avid's own AIR Creative Collection (their latest download of it that they list on the same page as the 11.1.3 upgrade) installed. The other problem is that if you follow JFreak's troubleshooting advice above then A) You wouldn't remove the AIR plugs because they are not 3d party and B) if you are being thorough and do put them in the un-used folder as soon as you open up Pro Tools it automatically takes them and puts them back into the Plug-Ins folder where they will continue to cause the same problem.
I came across this solution when, after trying everything and following Avid's poor trouble shooting tips (I guess they just assume that it couldn't be their fault so don't even test it) was getting no help. So, I started over and did a clean uninstall of Pro Tools and then reinstalled Pro Tools 11.1.3 (this on my 2013 Mac Pro running 9.1.2).
I then opened a session that previously hadn't been able to go more than 10 seconds without the 9093 error and it played right through from start to finish. Not only that, but the CPU meter was behaving normally.
"Great," I thought "now let's add in my plugins one by one." First addition was installing Avid's most recent Air collection and boom, hit the 9093 error as soon as I hit the space bar and, even when I closed the session, the CPU meter was going crazy again. So, I tried to move those plugins into the unused Plug-ins folder and noticed that once I opened a session, it moved them right back. So, Avid is so sure that their plugins aren't the problem that they have programmed Pro Tools to put them right back in the plug-ins folder which makes troubleshooting nearly impossible unless checking after every plug-in install as I did instead of moving plug-ins to the un-used folder as recommended.
So, I reinstalled Pro Tools and didn't install AIR and have since reinstalled all of my Waves, Sound Toys, and UAD plugins (checking between each install to see if there was a problem) and have had no more -9093 errors. Still have a few more to go and, like I said, there may very well be some 3rd party plugins that could cause this error but, in my case, the culprit was definitely Avid's own plugin bundle (which I'm more than happy to leave off of my system - I couldn't imagine using Pro Tools w/o 3rd party plugins but I'm more than happy to give up AIR Distortion in order to have a system that can actually be used to record and mix audio.
Not having AIR installed has, so far, left me with totally trouble free from this annoying issue (that you'll never solve by following Avid's troubleshooting advice since Pro Tools will always put the air plugs back into play upon start up) and I hope that it helps many of you who have experienced the same frustrations. If you try it, please report back and we'll see what sort of success rate this fix has.
There's been a number of threads about this and a number of frustrated people trying to get Avid to acknowledge that there is a problem on their end somewhere and to do a little testing instead of just blaming 3rd party plugins (or the computer running the system).
Here's a couple responses from a moderator showing quite clearly they don't feel that their own software is to blame:
Quote:
Originally Posted by JFreak (Post 2115550) Move all 3rd party plugins to unused folder and try again. If it helps, move those 3rd plugins back one at a time and find out which one is giving you trouble. |
Quote:
Originally Posted by JFreak (Post 2115557) Then I'm afraid I have no other idea but that the i5 CPU is the problem :( Modern PT really loves i7 processor... Also, 4GB memory is not enough. It will run OSX nicely but for everything else you should install more. Consider 8GB minimum for using PT with most up-to-date software. |
Well, I think that I have found the solution - it solved it on my system but I can't say that it's "the fix" until others try it with success which is why I'm starting a new thread.
The problem, of course, could be created with some 3rd party plugins but, regardless, it is absolutely created if you have Avid's own AIR Creative Collection (their latest download of it that they list on the same page as the 11.1.3 upgrade) installed. The other problem is that if you follow JFreak's troubleshooting advice above then A) You wouldn't remove the AIR plugs because they are not 3d party and B) if you are being thorough and do put them in the un-used folder as soon as you open up Pro Tools it automatically takes them and puts them back into the Plug-Ins folder where they will continue to cause the same problem.
I came across this solution when, after trying everything and following Avid's poor trouble shooting tips (I guess they just assume that it couldn't be their fault so don't even test it) was getting no help. So, I started over and did a clean uninstall of Pro Tools and then reinstalled Pro Tools 11.1.3 (this on my 2013 Mac Pro running 9.1.2).
I then opened a session that previously hadn't been able to go more than 10 seconds without the 9093 error and it played right through from start to finish. Not only that, but the CPU meter was behaving normally.
"Great," I thought "now let's add in my plugins one by one." First addition was installing Avid's most recent Air collection and boom, hit the 9093 error as soon as I hit the space bar and, even when I closed the session, the CPU meter was going crazy again. So, I tried to move those plugins into the unused Plug-ins folder and noticed that once I opened a session, it moved them right back. So, Avid is so sure that their plugins aren't the problem that they have programmed Pro Tools to put them right back in the plug-ins folder which makes troubleshooting nearly impossible unless checking after every plug-in install as I did instead of moving plug-ins to the un-used folder as recommended.
So, I reinstalled Pro Tools and didn't install AIR and have since reinstalled all of my Waves, Sound Toys, and UAD plugins (checking between each install to see if there was a problem) and have had no more -9093 errors. Still have a few more to go and, like I said, there may very well be some 3rd party plugins that could cause this error but, in my case, the culprit was definitely Avid's own plugin bundle (which I'm more than happy to leave off of my system - I couldn't imagine using Pro Tools w/o 3rd party plugins but I'm more than happy to give up AIR Distortion in order to have a system that can actually be used to record and mix audio.
Not having AIR installed has, so far, left me with totally trouble free from this annoying issue (that you'll never solve by following Avid's troubleshooting advice since Pro Tools will always put the air plugs back into play upon start up) and I hope that it helps many of you who have experienced the same frustrations. If you try it, please report back and we'll see what sort of success rate this fix has.
AIR is not part of Avid, it's a different company, hence can be issues.
RépondreSupprimer