So, I insert a bus and place a UAD 2 duo reverb in this bus. I get the settings to where I want them and "save". Next time I open this project I have to re-install the Lexicon 24 reverb (even though it is still there, but not working) and re-adjust my settings.

Anyone else see this? It happens whenever I save and close Sonar, then re-open.

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...

That is an odd one. I can't repro here. The UAD Lex 224 is working as expected.. I am using the latest UAD v6.4 and the UAD x64 plug-ins exclusively (no x32 UAD plug-ins installed/scanned in SONAR) & SONAR x2a.

Best,

Billy Buck

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.

I should have been more clear in my first post. I am inserting any UAD 2 plugin (64 bit) into a Pro Channel FX Chain, and saving as a preset. After closing Sonar and re-opening I have to click the blue button for the plug-in off and on again to get the plug to work. I'm not sure why this is the case for me, but if anyone could verify this I would appreciate it.

My work-around is to just place the UAD plugs in the bus FX Bin instead of the Pro Channel FX Chain. They open and function properly in the Bus FX Bin.

Thank 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

Thanks for your input Danny. In light of your problems I don't feel so bad now. I can work around my minor issue, otherwise, 6.4 is working fine for me. I'm aware of the "qualified" issue with UAD, however, in previous threads they did state they do work closely with Cake, so, I'm hoping they won't abandon us completely. Thanks Danny, and have a Merry Christmas!

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

Nah don't feel bad, you're not alone. LOL! I'm afraid to try what's not working for you...as I couldn't wait to get my hands on this Sonar update due to the custom chains we can make in pro channel. I've had X2 installed on one of my other machines so I could get used to it. I didn't put it on my good recording boxes until the first patch as that's what I always do. So in a sense, X2 is brand new to me again. I do way different stuff on my real recording boxes than I do on the little service boxes. (as I like to call them)

So it's really gonna suck if I get the same issue as you when I try that. I still think it's something with those plusg in the 6.4 bundle JS. I mean it can't be perfect, this is their maiden voyage into the 64 bit realm. I just like to know what happened to the 32 bit plugs. They have definitely altered something in the code. As soon as I bring one in, press play or move it around, bang...that faded white screen and Sonar crashes. Then I was getting a 64 bit plug issue too at first. I kept on getting a CLSID message that Sonar couldn't make up its mind what plug to use and it gave me choices. The 64 bit plug worked no matter which I chose, but the message popping up was driving me crazy.

I sorted all that out though....the only remaining problem is the excessive crashing with the UAD 32 bit plugs. They told me the same thing....they'd be working with Cakewalk to sort it out. That works for me if they can fix it. Ah thanks man, you have a Merry Christmas also. :)

-Danny

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