New UAD 6.3.2 on SONAR X2 - Anybody Try It Yet??

Thanks for the heads up. Works with no issues here on XP 32 bit and X2

Yea, I ran into problems on XP 32 bit & X2 works in a new project but crashes many older projects right when launched.   Rolling back here too
 
 Edit: rolled back and all is well.  The crashing projects were also crashing in X1 as well as X2.

I've installed the latest UAD 6.3.2 and all is well on my DAW. FWIW, v6.3.1 worked fine as well.
This is using SONAR X1d Expanded (build 535) on WinXP (SP3) 32bit DAW. Trying out the plug-ins
and my first impressions are the SHMC is nice, but I don't have a real one to compare it too. Not so sure
it is something I really need. I am finding the Precision K-Stereo plug-in from Bob Katz more useful for my 
purposes. I was trying to wrap my head around it and then I found this UA video with Bob Katz explaining 
and demonstrating the K-Stereo ambient recovery process. It has helped me to understand it a lot better:

http://www.youtube.com/watch?v=Xb4IzTXHorY&feature=plcp


Cheers,

Billy Buck

Middleman


It works under 32 bit it does not work under 64 bit. I guess they figured since Sonar is providing their own 1176, LA2A and other similar plug ins, they don't have to support Cakewalk anymore for future plugins. Shame on Universal Audio.

Maybe they're saving the 64bit working versions for SONAR for the 64bit versions of the plugs that will be released this past summer.

yorolpal


Yup...it's a race between UA and SoundToys to see who can be the last company on planet earth to go 64bit.  I'm still betting on SoundToys.

Maybe IK should get some of that stuff Lance Armstrong allegedly used?

Hey guys,
               Speaking of UAD v6.3.2 have you all read the release notes. I was pretty shocked to find that UA has decided to stop including the mono (m) versions of all new plug-in releases (including the current release). To wit:
 

Mono VST versions are not included for new UAD plug-ins:
 
The monophonic VST versions of UAD plug-ins that can be optionally installed — those with "(m)" in the plug-in name — are no longer developed for new UAD plug-ins. This is a result of the platform transition to 64-bit plug-ins. The mono VST versions of prior UAD plug-ins can still be optionally installed for session compatibility.
 
Note: The standard (stereo) VST plug-ins do not consume more UAD DSP when used on mono tracks.

What is UA thinking? No more (m) versions on new plug-ins or any of the forthcoming x64 plugins? I just checked the latest v6.3.2 and the extra DSP usage when using the standard UAD versions on mono tracks is the same as it ever was. I have verified this in both SONAR X1 & REAPER 4.31 (Win & Mac versions). I am sure there are other DAW host apps (Live, Studio One, etc. come to mind) affected by this as well. Most of my tracks are mono, so in order to use the 64bit versions or any new plug-ins, I will be using up to 40% more DSP than when using the exact same plug-ins in my current WinXP (32bit) DAW. I can't say I am very pleased with this current turn of events!    
 
So how can UA state that using the standard UAD plug-ins uses no more DSP than using the (m) versions on mono tracks?
 
 
Standard FATSO on a "Mono" track in SONAR X1d: Note both left & right channels on FATSO being used and 40.5% DSP (typical for a stereo version with tranny enabled)
 

FATSO (m) version on a "Mono" track in SONAR X1d: Note only left channel on FATSO being used and 25.5% DSP (typical for a mono version with tranny enabled)
 

 
So as SONAR/UAD-2 users, I am wondering what are your opinions on this latest UAD development?