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?