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.

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.

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.

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

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.

Just uncheck 64bit Double Precision Engine in Preferences.
 
This is what Cakewalk have suggested, and all these issues go away.
 
They are working on it.

I realize Cakewalk said they are working on fixing the problem, I just wanted to add that I also have a severe case of this problem with x3c. First thing I noticed when I loaded a project in Sonar after the x3c update was that loud, ugly buzzing/whining sound and quickly figured out it was coming from the CEs... and btw the buss CEs do it too on my end, as far as I can remember, but a lot quieter. You can make the buss CEs output the noisie louder by ramping up the input gain on the buss and pressing the tolerance button...
 
It would be very nice to have this fixed... Otherwise we have to untick 64bit double precision engine... or use x3b... or go back to Sonar x2

Same here. When I turn the 64-bit engine off the buzzing stops, however there is still some weird behavior with the console emulator on mono tracks (the right meter is dead. I don't know if this is a graphic or an audible bug).
 
Today I discovered via a plugin that, when not playing anything, there is heavy activity not on the 2bus but on all the other hypothetical surround outputs (I don't have surround). I have a hunch this might be related. 
 
Looking forward to X3d! Problems aside, I have to say I'm greatly enjoying X3!

> Please please please fix!  It's making projects un-listenable
 
You made no mention that you disabled 64 bit precision engine. If you haven't there's your fix until X3D.

Appears you have since edited you post... OK thanks. If this is a different issue from the OP (I'm not sure) probably best to start a new thread.

Is anyone else getting the right side meter going dead when they un-tick 64 bit engine?  It takes away the pegged meter and the squeal, which is nice, but then the right hand meter of the CE only responds to stereo tracks, not mono.

sanderblom
Also, I've tried re-installing several versions of Sonar but the problems remain in older versions too. So that might indicate the trouble is caused by something that remains on/in the computer or register that isn't overwritten. 

Wow! By older versions of Sonar you mean X3? Or before that?

It's a bit of a bummer, even more so because I bought a top notch Dell i7-3770 4x 3.4gHz with 16GB ram computer, especially for running X3, and a new sound interface (Steinberg UR28M) thinking I'd never have any digital troubles again. Fool's hope of course! ;)
 

...Because turning off 64bit DP does eliminate the OP topic?