• SONAR
  • Please Verify - Panning in Drum Replacer Not Working (Answered)
2015/07/03 18:46:00
kevo
Drum Replacer does not allow me to pan a drum sound.
Panning only affects the volume of the sound, not the panning.
Full left = full volume.
Full right = no volume.
 
I have checked to see if it was track interleave, also tried without plugins.
 
Thanks!
 
2015/07/03 19:52:15
OldTimerNewComer
kevo
Drum Replacer does not allow me to pan a drum sound.
Panning only affects the volume of the sound, not the panning.
Full left = full volume.
Full right = no volume.
 
I have checked to see if it was track interleave, also tried without plugins.
 
Thanks!
 


What about separating all the replaced sounds and rendering to a track,
then panning/merging with the original...
Or leaving them separated and clip editing(pan) the discreet clips?
 
Mel
2015/07/04 00:04:03
kevo
OldTimerNewComer
What about separating all the replaced sounds and rendering to a track,
then panning/merging with the original...
Or leaving them separated and clip editing(pan) the discreet clips?
 
Mel


Thank you for the response.
The reason I posted the thread was to see if others were having problems with panning in Drum Replacer.
 
 
Edit: I noticed the title to the thread was not clear so I changed it.
Thanks again for your response! :)
2015/07/04 00:13:00
kevo
OK.
This is what I found.
If the source audio is mono, panning in Drum Replacer does not work.
If the audio track is converted to so called stereo then panning works.
 
 
 
2015/07/04 00:15:31
John T
That makes sense. If the track drum replacer is outputting to is mono, then there's no stereo field to pan within.
2015/07/04 00:35:44
kevo
John T
That makes sense. If the track drum replacer is outputting to is mono, then there's no stereo field to pan within.


It *may* be by design but it is not consistent with how Sonar handles other plugins.
When the track interleave is set to stereo the output for a stereo plugin is stereo not mono.
If the track interleave is set to mono, then you are correct there is no stereo field to pan to.
 
This is not a big deal, but it requires an extra step that should not be necessary.
 
 
2015/07/04 05:06:49
John T
Ah well, hang on.
 
There are two different use cases here.
 
In the first, you're using an instance of Drum Replacer to replace a single item in the kit. Say a tom. And you're either only using one layer in the replacer, or the layers are being used to create a single drum output (eg, layering up three toms to create one sound).
 
In such a case, you'd generally be working monophonically, and you'd want your layers to be placed together. In which case, it would make the most sense to not use the DR panning, and instead set your panning at the level of the (mono) track.
 
 
In the second use case, you're using Drum Replacer to listen to one track, perhaps an overhead, and using the DR layers to trigger multiple items, say kick, snare, and tom. In that case, it's useful to be able to use the panners within DR to feed your stereo track.
 
 
So I'd disagree that there's an unnecessary step here. There's a flexibility allowing the above two use cases, and inevitably, there's a decision point for the user to choose an appropriate setting.
 
 
2015/07/04 06:00:42
kevo
Seems silly to make an argument about this.
IMO the plugin should be aware of the track interleave setting just as any plugin that is not strictly mono does and behave appropriately.
If cw wants the plugin to behave as it does now then the pan controls should be disabled in the plugin when the source audio is mono. It will save someone from going "what the...?" When panning doesn't work in the plugin.
 
The track interleave setting should dictate how the plugin processes it's audio output.
 
I think that is about all I have say. :)
Although I wouldn't be against someone from cw telling me I'm off my nut.
 
I am currently working on a remix of a song recorded 35 years ago. Didn't have the luxury of recording each separate drum piece on it's own track back then.
 
,..............
I posted this from my tablet so I didn't dink with organizing my random thoughts. :)
If you break the secret code without using a magic decoder ring you will probably get something cool from Craig in the update later this month!
 
2015/07/04 06:30:29
John T
kevo
 
 
The track interleave setting should dictate how the plugin processes it's audio output.
 

I'm pretty sure that doesn't happen for any plug in, as it happens. Track interleave and plugin outputs are independent of one another.
2015/07/04 07:59:03
Noel Borthwick [Cakewalk]
It is consistent with how SONAR handles clip effects. A region effect is really a special type of clip effect. The interleave of region and clip effects is gated by the interleave of the clip wave data. If its a mono clip  then panning will not work. This is also why pan envelopes will not work on mono clips.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account