• SONAR
  • X2 processes mono track as stereo with active Waves plugins in fx bin
2013/08/06 16:32:15
Guitarmech111
I am really NOT liking SONAR X2 right now.
 
I have a mono bass track recorded. I added the Bass Rider into the FX bin. SONAR changes the pan and puts a stereo effect on the track with the signal panned. When I turn off the plugin, the signal goes back to mono processing.
 
This also happens with the API-550 mono plug too. This is a one drawn wave track, not dual as you would find in a stereo track in case you were thinking of making sure it was mono. 
 
Thoughts?
2013/08/07 11:31:17
Guitarmech111
With additional research, I have found that there is still an interleave option to designate mono or stereo. I do not use the track inspector, but the interleave is in there and in the console view. I missed that. UE on that issue with another X* learning curve.
 
Here is an enhancement request I would like to see - put the interleave button BACK in the TRACK VIEW. I use the track view primarily and do not often use the track inspector.
2013/08/07 13:06:15
John
Track View and the Track Inspector are not mutually exclusive. Further the Track Inspector is customizable. 
2013/08/07 13:21:14
Guitarmech111
yeah, found that out. :) thx John.
2013/08/07 14:56:12
brconflict
Also, for convenience, the plug-ins you have from Waves should be already labeled "Mono" or "Stereo" (or "Mono/Stereo"), and make sure your track is set to Mono or stereo to match, obviously. I make this mistake often, but it's quickly obvious what is wrong.
2013/08/07 23:18:21
Guitarmech111
Thx Brian, I do use the mono plugs for the mono tracks. I just thought that since this was a mono clip that SONAR would detect that and make the audio track a mono track. I don't think that would be so hard. If I onlly choose one input for the track, that is NOT stereo, SONAR should change the interleave to mono. I am not able to think of a reason why this is not done.
 
Anyone think why this would not be a good rational?
2013/08/07 23:58:28
bitflipper
Any track can arbitrarily switch between mono and stereo regardless of the specified interleave. In fact, a single track can switch from one to the other multiple times as it navigates through the fx chain.
 
SONAR is just adapting to each plugin's requirements, some of which can only handle mono in and mono out, while others can only do stereo ins and outs. Some are hardwired to output stereo regardless of the input. 
 
So yes, SONAR does see your mono track and starts out with a mono interleave. But depending on what you put into the fx bin SONAR might have to treat it as a stereo track, and you won't even know it unless it happens to be the last plugin in the bin. (And of course all tracks ultimately become stereo when fed to a stereo bus.)
 
Waves plugins normally avoid the issue by supplying separate mono and stereo versions of each. FabFilter does that, too. But not so many others. Maybe it's not the Waves plugin that's at fault, but perhaps something else that follows? 
2013/08/08 07:40:23
robert_e_bone
Great info, Bitflipper.
 
Bob Bone
 
2013/08/08 09:15:05
Guitarmech111
bitflipper
Any track can arbitrarily switch between mono and stereo regardless of the specified interleave. In fact, a single track can switch from one to the other multiple times as it navigates through the fx chain.
 
SONAR is just adapting to each plugin's requirements, some of which can only handle mono in and mono out, while others can only do stereo ins and outs. Some are hardwired to output stereo regardless of the input. 
 
So yes, SONAR does see your mono track and starts out with a mono interleave. But depending on what you put into the fx bin SONAR might have to treat it as a stereo track, and you won't even know it unless it happens to be the last plugin in the bin. (And of course all tracks ultimately become stereo when fed to a stereo bus.)
 
Waves plugins normally avoid the issue by supplying separate mono and stereo versions of each. FabFilter does that, too. But not so many others. Maybe it's not the Waves plugin that's at fault, but perhaps something else that follows? 


Been through all that. I specifically use the Bass Rider MONO only in that fx bin. I also have the plugin properties to perform in mono mode.

SONAR did not detect the plugin and wave status to process this as a mono file. The onine help even states this:
When using a mono VST plug-in on a stereo track (interleave set to Stereo), the left and right channels will be out of sync. The left channel is processed by the mono effect, and delay compensation is applied, while the right channel is not processed and does not have delay compensation applied. The signal will look something like this:

Left channel: Wet signal (delayed)


Right channel: Dry signal (no delay)

A mono VST plug-in will work correctly if Enable Mono Processing is checked in the VST Plug-in Properties dialog box and the track interleave is set to mono.
 
This simply does not work as it would be best for a workflow. The above statement says SONAR is not intelligent enopugh to determine the track status.  I am going to call TS and get some clarification and submit a request for enhancement.
2013/08/08 10:27:08
bitflipper
Guitarmech111
Here is an enhancement request I would like to see - put the interleave button BACK in the TRACK VIEW. 



Amen to that! And the polarity button, too. This is one of the reasons I'm still using 8.5. I'm hoping X3 will have a fully-customizable track header similar to the toolbar customization feature, so you can show/hide whatever you like.
 
After re-reading your OP, it does seem that the fault lies within the Bass Rider plugin. I'd follow up with Waves as well as asking CW if they have any ideas. What you should do is create a demonstration project with just one track containing a short clip, plus the plugin and nothing else, open a support ticket and send them that project. They'll be able to tell you exactly what's going on.
 
Take a look at the plugin's entry in the registry (Software\Cakewalk Music Software\SONAR Producer\Cakewalk VST\Inventory). The relevant keys are forceMono, forceStereo, numInputs and numOutputs. These settings are based on information the plugin reports about itself when you do a scan; Plugin Manager can only trust that the plugin is returning accurate information.
 
I don't have Bass Rider, but I have other Waves mono-only plugins. They all have these settings:
forceMono = 1
forceStereo = 0
numInputs = 1
numOutputs = 1
Check and see what these values are for Bass Rider.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account