System unusable after upgrading to 9.6.0 AND going back to 9.5.2

System unusable after upgrading from 9.5.2 to 9.6.0 AND going back to 9.5.2

Hi everyone.

I'm in big trouble with my system right in the middle of an important project. Everything was running fine until I installed the new UAD software 9.6.0 to try the new plugins. After doing this, the whole DAW was slow, lots of UAD plugins not loading and a bunch of error 38's as shown in the image.

The sessions are reasonably sized but they all worked flawlessly before I upgraded, and in total I have 24 Shark cores split between two octo-core Satellites, an Apollo 8p and an Apollo Twin Quad MkII.

I then tried rolling back to 9.5.2, cleared Logic's plugin cache and let it rescan all the plugins again. The big problem now is that even with version 6.5.2, I started getting a bunch of errors. Every project takes ages to load because I get a error 38 popup for almost every UAD plugin that Logic tries to load. After finally the session finishes loading, most of the UAD plugins are disabled.

I'm sure all this had something to do with installing 9.6.0 because 15 minutes before everything was working fine. What really bugs me is that going back to version 9.5.2 didn't solve the problem.

Can anyone please help me with suggestions because at this time, this problem is really killing me...

Sorry to hear this. Your situation is not being widely reported nor did it show up in testing. So it must be something unique to your setup.

Start a case.

https://help.uaudio.com/hc/en-us/articles/210253543-Contact-Support

Hi. I narrowed this down to a single channel on a session containing an Ocean Way room sim plugin. Whenever I enabled the plugin on this channel everything would fall apart, even after quitting Logic and opening another session. I had to turn off the hardware and reboot the computer, but every time I re-opened this session, the same thing would happen again.

I deleted the track and re-created it with the same plugins and now it’s working. The weird thing for me is that whatever this session did to the system it remained even after quitting Logic, the console, etc. Only after turning the UAD stuff off then on plus a reboot, would everything go back to normal.

I have been using this system for three years and this was the first time that something really weird happened...

Anyway, thanks Drew, everything seems to be back to normal now.

Have you done a full power cycle of your Apollo units? I had the exact same thing happen with the 0.9.6 release on my setup and have had it happen in the same way in the past. We have almost the exact same setup (except I have an original Twin Duo instead of a quad). If you haven't done this already give it a shot as it cleared it up for me. I shut the DAW, powered down all the Apollo units for a minutes or so, then powered the Apollos all back up, waited until they fully powered up, then booted and re-installed 0.9.6 and everything has worked fine since then. Incidentally I had the issue with both OWS and a Fairchild 670.

Hope this helps. This is the 2nd time (3rd time?) I've had to do this dance after running an update. I'm wondering if there's not something in the process that's forgetting about or somehow losing the path to one of the units (in my case one of my Satellites would sit at 0% always until I did this power cycle dance).

I am also having issues with my arrow since the update. I posted it in the forums already:/ I personally think UAD needs to separate their software. One to update the console and firmware and another to download the plugins we own. And within that program the ability to download each plugin that we want to demo/buy individually. It is ridiculous to have to download a 2gb file every time an update occurs and then have to reorganize our plugins, etc.
I'm getting these two errors and can no longer use my arrow as an interface

Replied in your thread.

I'm also having an issue with DSP heavy plugins. The SSL E strip and the Oceanway plugins. The last update seems to have made the issue worse.

I had to do a complete reinstall of my OS :/ Now things seem to be working. But that really stinks

Dallon426, your problem is different from what everyone described. But it sucks, for sure. Hope you can get it fixed.

Hi Gerk. By a full power cycle, do you mean hardware reset? I did this for all devices on my setup to try to get this thing fixed, but I don’t think that made a difference. Everytime I loaded the problematic session with the Ocean Way plugin, all hell broke loose, I couldn’t load any session afterwards even after restarting Logic. If I remember correctly, only a reboot and power on/off of the UAD stuff would things get back to normal. I just deleted the track on the problematic session, re-created it and everything seems fine now. But now I’m wary of doing updates of the UAD software. Unlike you, this was the first time this happened.

No not a hardware reset, just a power down, wait for a bit and power back up again. Once I've done that then even any tracks that had been problematic for me would fire up again fine, both OWS and Fairchild 670s were the killer ones for me. I've had this happen several times now right after running a UAD update. Because it's not widespread I think it's something that's a (very far in the) corner case. Given that our setups are almost identical (aside that you have a quad Twin and I have a dual one) I think we just have the perfect storm to make it happen. I've also tried to recreate it on demand to do a bug report with UAD but I haven't been able to recreate it on demand, even with literally the exact same situation -- I always make a clone of my system before I run an update. In my case both of the last two times this happened I restored from my clone and ran the update again ... but it didn't trigger the same issue. Of course at that point I had already power cycled my hardware so that might be another thing required to trigger it.

At this point I honestly think UAD should just include some information telling users that it's probably a good idea to do a full power cycle of any external Apollo units after running a software update ... I know that I'm going to keep following that procedure for myself.

Hello Drew

I am having the same problem but this time to a solo. Just tried 9.6.0 after having a system that gave me no real problems for years. Now, I keep getting

Driver Not Installed Correctly


I followed directions 3 times to no avail. I haven't dared tried opening Protools (10 HD) after seeing what has happened to others.

I have a mixing project that has to be completed....

Evens1 said:

Hello Drew

I am having the same problem but this time to a solo. Just tried 9.6.0 after having a system that gave me no real problems for years. Now, I keep getting

Driver Not Installed Correctly


I followed directions 3 times to no avail. I haven't dared tried opening Protools (10 HD) after seeing what has happened to others.

I have a mixing project that has to be completed....

Click to expand...

Can you post a screen shot of the error? What OS?

Answered via PM.

Likely: https://help.uaudio.com/hc/en-us/ar...-Installed-Correctly-Driver-Version-Mismatch-