brian brock
I have been assuming that the issue was because of the way Sonar doesn't have "real" mono tracks, as is also shown in the way it uses the same UAD dsp on a mono as on a stereo track.
 

Can you please elaborate on what you mean about "SONAR does not have "real" mono"?

I also turned my master bus to MONO to check the mix for volumes and emulator built up such noise, gradually increasing to max and this can be seen on the meters. This happened only in mono and just for Type N and A modes. No problem seen in STEREO channels or for TYPE N in MONO channels. Considering that QUAD curve EQ does not show the spectrum analysis for MONO channel, I conclude this as SONAR X3 updateC having problems with MONO tracks??? note that Quad curve spectrum problem seems to be limited to only mono recorded tracks but not for stereo tracks where only  interleave is selected as MONO.

The Bakers are on it. Disable the 64-bit Double Precision Engine in preferences, and reload any project you have open. Should eliminate problems with both Console Emulators and the flyout EQ spectrum analyzer  until a fix comes out.

Sylvan
 

brian brock
I have been assuming that the issue was because of the way Sonar doesn't have "real" mono tracks, as is also shown in the way it uses the same UAD dsp on a mono as on a stereo track.
 

Can you please elaborate on what you mean about "SONAR does not have "real" mono"?

I don't entirely understand it, but here are a couple of places where people more or less explain what I'm talking about:
http://forum.cockos.com/project.php?issueid=4667
http://uadforum.com/general-discussion/13059-no-mono-versions-la2a-plugins.html
 
My impression is that when Sonar has a mono track, it pretty much just uses the left side of a stereo track.  My guess is that some plugins with saturation (for example) are treating stereo instances with some kind of crosstalk between the channels, and that this is what's giving Sonar problems with Alloy 2 and the Console Emulator.

iirc this was discussed here a few versions back, resulting in the pan law options?

brian brock

Sylvan
 

brian brock
I have been assuming that the issue was because of the way Sonar doesn't have "real" mono tracks, as is also shown in the way it uses the same UAD dsp on a mono as on a stereo track.
 

Can you please elaborate on what you mean about "SONAR does not have "real" mono"?

I don't entirely understand it, but here are a couple of places where people more or less explain what I'm talking about:
http://forum.cockos.com/project.php?issueid=4667
http://uadforum.com/general-discussion/13059-no-mono-versions-la2a-plugins.html
 
My impression is that when Sonar has a mono track, it pretty much just uses the left side of a stereo track.  My guess is that some plugins with saturation (for example) are treating stereo instances with some kind of crosstalk between the channels, and that this is what's giving Sonar problems with Alloy 2 and the Console Emulator.

That's the problem in a nutshell. I'm surprised there hasn't been more of a clamoring for proper mono plugin handling on this forum since UA ditched the mono versions. Perhaps there's not that many UAD users, or the majority of UAD/Sonar don't know about this issue. It's nuts, but in a host like Studio One, I can run up to 40% more UAD plugins compared to Sonar because of the mono plugin support in the host. It's like having an extra DSP added to my UAD-2 Duo, versus trying to do the same mix in Sonar. I wonder if other VST plugins would benefit from mono processing also...
 
I was really hoping with VST3 and the improved VST implementation in X3 that we'd see proper mono handling of plugins, but alas, no luck. 
 
That said, I don't think the mono issue has anything to do with the buzzing issues in this thread.

I had the same problem.
I started removing other plugs from the pro-channel
to see what it didn't like playing with..when
I removed the tube saturator it stopped.
 
 

They said it's a console emulator. 
 
They didn't say it was emulating a working console.
 
;-)

If you disable and re-enable the Audio Engine (the little sine-wave button in the Control Panel's Time-code window), does the hum return? Or only after hitting Play and Stop on the Transport?  I ran into a situation last night where something was eating my CPU for breakfast (plug-in, likely) in a pulsating manner. I disabled and re-enabled the audio engine, and the CPU was better (not great, but down to 50% utilization). 

Same problem here. Mono tracks cause buzzing and excursions of the right-side VU meter with Console Emulator. Type N (my favorite) is the worst, but they all do it if the Trim is turned up high enough.