Hello,
Since a couple of months I have a serious problem with my Universal Audio (UA) plugins when using Cubase Pro 14. When I use them in a project, so when I insert UA plugins on a track, Cubase crashes. I tried a lot of things on the UA side. But maybe (a setting in) Cubase (14) is the problem. Can someone please help me with this serious issue?
Thanks in advance!
Best regards,
Marcel Engelbertink
Music Producer & Sound Engineer
Crazy cats Music Productions
Welcome to the forum! If you could post the crash dump file that would be great. Also please let us know what OS/version youâre running, and which UAD type of UAD (UAD-2 vs UADx) and ensure youâre only using the VST3 version as UAD still installs VSTs without asking you. Also, there was a UAD update yesterday (11.6.0), so that may be something to look at depending on the OS.
Thank you so much for your quick response! I use Windows 10 Pro and the UAD-2 Satellite and UAD apollo x4. I installed yesterdayâs UAD update and unfortunately the issue persists. The popup that appears says: âOne or more UAD plug-ins have been disabled. A UAD device is not responding (code -38)â.
AH, these are coming from UAD, not Cubase; itâs not an actual âcrashâ then, but rather, UAD giving you a code -38. I see Drew at UAD has already asked you to open a support ticket with UAD, so thatâs the direction you should indeed take.
Thanks!
1 Like
Yes I will open a support ticket with UAD, weâll see. Thank you so far!
Upgraded to Cubase 14 Pro today. And the same happened to me. Hope this will be solved soon!!
You opened a UAD ticket as well?
No issues here with UAD PCI cards Octo and Quad on Win 10/C14.0.20. Must be a Satellite/Apollo issue Iâd assume.
Yes, I did
same issue for me today on Cubase 14. And also C13. The issue happened immediately in C14 but in 13 I was able to load one plugin at first.
error 38 is a computer/os problem. look at this page:
Itâs not a computer/os problem.
Itâs a UAD communication problem. If any UAD device loose contact error -38 pops up.
To troubleshoot, open the UAD panel and open the System Info tab.
If one device is greyed out it means itâs not connected.
This is a far too simple conclusion and suggestion in my opinoin. I never had the problem and now two people have the same âcomunicationâ issue after installing ubase 14. Of cousre I checked all kinds of settings in Cubase and UAD software and replaced my thundebolt cables, checked de UAD connect app etc. All suggestion from UA are not helping until now. I start to believe that it is a combination of UAD and Cubase 14 that causes the issue.
This âsolutionâ is not helping.
so I would try to roll back to the installation before the UA update since all was working. should hopefully be the easy fix.
if you open your device manager in Windows it should list your UAD cards, and report back error code 38. When you get an error in the Windows device manager for your uad cards it is not related to Cubase. Yes Cubase will crash when you try running plugins - but UAD is causing it obviously, there is no magic button in Cubase to help that. I have PCI-E cards with my Windows setup, no problems with latest updates. I run Satelitte with my MAC, no issues.
so until you get rid of the error 38 uad plugins cant run within cubase as there is a communication problem between your hardware and software. remember UAD plugins run of the cards via cable. the UADx plugins however should run just fine as they are running from your computer.
other than the UA troubleshoot page I really do not have any suggestions for a solution for you.
Iâm sure it seems that way, but @shagazulu indicated it started happening on C13 as well. Cubase is simply going to use the drivers it is presented with, just like any other DAW (LUNA has more direct integration as expected, of course). The concurrent behavior youâre seeing is most likely (in my opinion) related to a Windows Update. The fact that itâs actually the UAD software/driver giving you this message is what tells you the issue is somewhere between the UAD devices and Windows. I think the fact that Drew also directed you to open a UAD ticket (rather than one with Steinberg) supports that.
I know itâs frustrating. Folks in the Steinberg User Forum will try to help, but youâre probably going to have to be patient with UAD support. It can take some time.
Your sig indicates that youâre an engineer at a production house - is it possible for you to test the hardware on another system; possibly one with Cubase installed as well? That could help point you in the right direction. But 'twer I you, Iâd look at the Windows Update history and see if you can pinpoint when this started happening and if it coincides with a WU. Rolling back that update may be a good test as well.
Also, if indeed on Windows, ensure youâve run basic maintenance with:
sfc /scannow
dism /Online /Cleanup-Image /RestoreHealth
(two different commands, each taking some time to run)
Just that could help clear up issues.
I had a similar issue and it occurred when a UAD plugin was loaded along with Nomad plugin. A code 38 is a memory issue when the memory is not cleared properly. It can also be the result of a driver issue sometimes caused by an incomplete install or uninstallation. In my case it was one plugin that conflicted with UAD.
This has nothing to do with Cubase.
If you have a UAD device with plugins loaded in a Cubase project and that device doesnât respond when you load the project you get the Error -38.
This shouldânt be crashing Cubase so something else is probably happening too.
I would check cables and contacts on you UAD devices.
This error will also happen in Reaper and Studio One.
Is your sattelite USB or Firewire? I ask because Firewire is not supported in the 11.60.0 version.
Shoot, sorry, I need to clarify. My issue is happening with UADx plugins⌠and on an older Win10 machine with and older CPU. So I think itâs a compatibility issue. I just thought Iâd see if they run on this old machine, and they donât⌠which is odd since so many things, if not most or even all, do. Windows is amazing like that. MACs not so much.
So disregard this comment:
Yesterday I disconnected the UAD-2 Satellite (thunderbolt) from the chain. UA advised me this. So I only used the appolo x4. Until now I have no problems or crash issues with UA plugins anymore. Thatâs good news because I can work with my UA plug ins now.
So I assume the UAD-2 is the problem ⌠but what problem? I asked UA if they have any further idea or suggestion. To be continued âŚ
1 Like