Sonar X2a not cooperating with UAD

Is it only the Lexicon plugin or are others doing this too? I loaded some projects with the new 1176 collection plugins and they retained settings as expected. I don't own the 224 though...

This is a strange one. I am also using the most current 6.4 and 64 bit plug-ins. I'll have to try my other UAD plugs and see how they behave. Thank you Funkybot and Billy Buck for responding. Glad they are working for you.

JS, what sucks the most about this is, I've been having issues too with the new 6.4 update. I just talked to UAD support yesterday and part of his reply sort of upset me. He said "Sonar is an unqualified DAW" and they don't/won't be testing on it. My issues are way different than yours, so I'll spare you. But it's safe to say, unless we can find a way to be "qualified" once again, any issues that crop up with UAD and Sonar will probably remain issues. I've alerted the bakers about this and have been in contact with them as well with my issue. If anyone has a chance to get us off that "unqualfied" list, they may be able to. Heck, I even volunteered to beta test for UAD if they would allow me to just so we can keep Sonar in the picture. I got just about all of their plugs already, so I'd do it for the love of it to keep us in the loop.

Anyway, I have since switched back to 6.30 for what I need here. No 64 bit support of course, but everything else works perfectly. Sorry you're having problems. I'll try what you're seeing on my machine and see if it does it on the version I'm using. I can't even get 6.4 to work totally. 32 bit plugs totally lock Sonar up when I open up older projects that used the 6.3 version of the software. 64 works fine, but I can't totally commit to 64 bit just yet as I have a few old VST's and even a few DX plugs that I just can't part with.

-Danny

I can confirm the FX Chain/ProChannel issue, but everything else 6.4 related is working here perfectly so far. I'm even running Apollo, and it rocks with Sonar.

The only glitch I've found is that if I try to load more plug-ins than the DSP can handle, Sonar freezes and requires a restart. Trying the same thing with Pro Tools 10, Cubase 6.5, and Studio One Pro 2 gave error messages, but they kept working.

As to FX Chain thing, I wonder if the plug-ins living off in a separate hardware-land, instead of running native in the computer, makes a difference...maybe it's like when bouncing using external hardware, and you have to bounce in non-real time.

Danny - what's the nature of the problem? I may be able to help. I gotta say that going from 32-bit to 64-bit UA version 64 has been totally painless, and that includes installing, updating, and authorizing an internal Quad card, the card in the Apollo, and an external Satellite. I was pretty impressed it all worked so well, actually.

The lack of "qualification" doesn't mean they won't fix Sonar-related issues, but it also means that someone in tech support can't call up the database of test procedures they used for Logic, Cubase, and Pro Tools. It also means that particular person may not be familiar enough with Sonar to understand the nature of the problem.

So this forum is filled with cool people, let's see if we can help you

Danny - what's the nature of the problem? I may be able to help. I gotta say that going from 32-bit to 64-bit UA version 64 has been totally painless, and that includes installing, updating, and authorizing an internal Quad card, the card in the Apollo, and an external Satellite. I was pretty impressed it all worked so well, actually.

 
Hi Craig,
 
Thanks for asking. I'll try and give you the short version, but I'm not sure it will be possible. LOL! I've been working with the bakers on this as well, and they turned me onto what one of the dmp files had mentioned. It's definitely a code problem with the UAD 32's. But I'll lay it on you in case you have any ideas. (JS, I hope you don't mind me sharing here...if so, please accept my apology and I'll remove the post.)
 
So I install the 6.4 update. The first weird thing I notice is, there is no longer a directory choice for where you want to put your VST's. They are already pre-destined. Now, I put all my 32 bit plugs in my Cakewalk Vstplugins folder in (86). I've done that for years to keep everything tight and not all over the place. All 64's are kept in the Cakewalk Vstplugins folder minus (86)...just regular program files.
 
I have my 32 bit plug folder included in my 64 bit scan. I believed that this was the source of my problems...however, it is not though it fixed my CLSID error message once I removed the 32 bit powered plugs from the 64 bit scan. I just copied them and pasted to another folder. The 64's worked perfectly even with the CLSID error message. But the 32's, crash city Craig no matter what I try.
 
Any old projects that I load up that were created using the 6.3 or earlier versions of the UAD software, lock me right up when the 6.4 version is installed. When I press play, I get a faded white screen and Sonar crashes.
 
If I don't include the plugs and start in Sonar safe mode, as soon as I add one and press play, it crashes. Or, if it DO press play and it works, if I move the plug to another bin or location....bang, it crashes again. This happened when they were in the new directory as well. So at this time, I'm clueless on what to try and so is the tech at UAD until they can talk it over with Cakewalk and see what the deal is. I shared the dmp file that the bakers gave me so hopefully it will tell them something. Any ideas? Thanks again..
 
-Danny

Danny - I've pretty much gone all 64-bit, but just for grins I created a steinberg/VSTplugins folder in the x86 section and moved all the 32-bit UAD plug-ins there. I tried the 32-bit plugs in Ableton Live 8.5, and they worked. They also worked in Acid Pro. However, Mixcraft 6, which is pretty tolerant, threw up an error message for several plug-ins that said "The procedure entry point ?Create@CHypSharedData@@SGPAXKPAXKKK0@Z could not be located in the dynamic link library HypGui.dll"

There was a different error message for some plugs, which is too long to include here but said something about UADPlugCallbackHanderl and not being located ni the dynamic link library UAD2DriverClient.dll.

So whatever Sonar is doing, it seems Mixcraft does it too. Feel free to quote this message and pass it along to UA.

Just an update...I tried all the things I mentioned above. Epic fail. The new software won't recognize the old plugs and the old software won't recognize the 64 bit plugs. I knew that would be the case, but I had to try it anyway. :)

-Danny

Billy Buck

I gotta say that going from 32-bit to 64-bit UA version 64 has been totally painless, and that includes installing, updating, and authorizing an internal Quad card, the card in the Apollo, and an external Satellite. I was pretty impressed it all worked so well, actually.

Yeah, the same flawless performance here as well. I am using a UAD-2 QUAD & SOLO (PCIe cards) and an Apollo QUAD via FW800. Some DAW hosts like SONAR get confused as to what to call up/use when you have installed & scanned both x32 & x64 UAD versions. Simply using installing/scanning one 6.4 version or the other (commit to x32 or x64) and you are golden. Once v6.4 was released I was all in (solely using Win7 x64 now) and fully commited to using only the x64 versions. Every WinXP x32 UAD plug-in laden project has opened and played fine in Win 7 x64. All previous saved projects with x32 UAD plug-ins get seamlessly replaced by their corresponding x64 counterpart along with all saved presets. I am actually quite amazed out how smoothly my Win XP x32 -> Win 7 x64 transition has gone. If I closed my eyes I would think I am still using Win XP 32bit (as far as UAD plug-ins go).

The lack of "qualification" doesn't mean they won't fix Sonar-related issues, but it also means that someone in tech support can't call up the database of test procedures they used for Logic, Cubase, and Pro Tools. It also means that particular person may not be familiar enough with Sonar to understand the nature of the problem.

I've talked to the UA tech guys many times in the past. It is true that they will only "qualify" a few select high profile DAW apps. There is a rigorous testing & qualification process. It is no coincidence that the (3) DAW's that UA uses to "qualify" their plug-ins are the leading developers of the plug-in formats VST (Cubase), RTAS (Pro-Tools) & AU (Logic). If their plug-ins are "qualified" on those hosts then reason has it that the rest of the DAW hosts (using those same plug-in formats) will work accordingly if they are following the specified plug-in spec.


That does not mean that less rigorous testing is not going on, in a multitude of other DAW apps. Truth be told, it was admitted to me that they actually have most every DAW available on their bench test computers and their beta testers use a wide variety of DAWs (SONAR and even REAPER). Every registered UAD user will get tech support regardless of the actual DAW that they use. 


Cheers,


Billy Buck

Same here Billy....UAD 64 is perfect for me also. I'm trying my hardest to eliminate my use for 32 bit. I just can't seem to find plugs that are as good as some of my old DX and the VST's that aren't 64. It's hard to believe that in this day and age that I'd not be able to find replacements. But I get certain sounds out of these that I just can't get out of anything else. If they didn't make that much of a difference, I'd ditch them in a heart-beat. But alas, I'm stuck for now until I can figure something out. :)
 
-Danny

Anderton


Danny, what are these plug-ins you find so essential? I'm curious.

I soo knew someone would ask and embarrass me into telling. LOL! j/k
 
I use this reverb from Anwida Soft which is DX....incredible for drums and has one of the best gated sounds I've ever heard. The cool thing about this verb that is unlike others is when you crank it up and make it 100% wet, you don't have to use as much "send" level as you would anything else. So in turn, it doesn't raise the level of your instrument at all. You know how you sometimes have to really jump on a send to hear the effect you want and it raises the level? This doesn't happen.
 
Some old Beat Model suite that has some very cool pieces in it. They sound VERY analog which I normally don't go for, but these do it in a good way without the ugly coloration and saturation we get out of today's "so called" analog pieces.
 
The first version of Clone Ensemble. Totally love it moreso than the latest one. Neither are 64 bit. This gets used on just about all my back-up vocal tracks.
 
The old Q Sound plugin suite. I really get some good results out of these mixing them with other plugs just a touch to create sounds within sounds that I just can't get elsewhere. I'm surprised they still even work.
 
Antares Mic Modeler....I don't believe they even make this anymore, maybe they do....could of sworn it was D/C'd. Whatever the case, I love it and have all the mic models for it. Yeah I know it's probably just some form of eq or IR type of deal, but whatever it is, it can make a huge difference on things just by adding a model to your tracks. Works on everything.
 
An old Blue Tubes bundle that sound better than the updated one. The multi delay plug is off the hook.
 
PSP Stereo pack....not sure what they did to the new one I bought, but I hate it compared to the old one. You can dial in the exact same settings you used on the old version into the new version and it sounds completely different. Smaller, not as effective enhancing stereo feeds like the older version I bought. The new one just sounds sterile and...well, sort of too digitally imaged if that makes sense.
 
ARC 1 version 1.1.1...the only version of this plug that keeps the correction for me upon loading a saved project. I have this weird anomaly that I think only happens to me and one other person. Any version of ARC 1 over 1.1.1 will not hold correction. I can do the correction procedure on all of them, it's the plug that fails. I'll explain...because this is too easy for people to miss and it could be happening to some and they don't even know it.
 
So I use, lets say 1.3.1 which is the latest...and I'm forced to use it now because X2 crashes horribly with 1.1.1. I load up a project, save it. The next time I open that project, I press play and notice I'm getting my un-corrected sound. I open the plug to see if it's enabled because it's giving me the sound of disabled. When I double click the plug in my master bus bin, as it opens...it IS enabled and THEN applies the correction sound as it's being opened. I've had a support ticket with them for 3 years that is still open to this day because they can't figure it out. Now here's the weird thing...
 
I recently played drums for Frank Tanton (notnat on the forum) and when I open the project I did with him, ARC literally behaves correctly upon opening. It plays the correction as it should. But all other projects (it doesn't matter what version of Sonar I use) do not play my correction until I double click the plug in the bin and then it kicks in AS it opens. So this was my reason to stick with ARC 1.1.1.....plus I just like it better than ARC 2. But I'm screwed now with ARC 1, so I may have to go to 2 since I can't find a version that will hold correction. It's so weird man!
 
The above are game changers for me and actually, part of how I get the over-all sounds I get on my recordings. I've tried to substitute them whenever possible and have come up with fair results....but they just aren't strong enough results to write them off in my opinion. The ARC 1 thing is driving me crazy currently.
 
-Danny