Is anyone happy working with sustain pedal data in SONAR?

I remember already on Sonar 4 twelve years ago I and many reported how even muted clips sustain pedal event came through, got some really weird cut notes I did not understand first.
 
So controllers were handled differently than notes, somehow.
 
Haven't used Sonar for two years now, don't know if still something strange there.

I can think of many reasons why I might want MIDI notes muted but not continuous controller data occupying the same clip/time period.

Ah, I see what the OP was talking about. When you mute the clip, any CCs within that timeframe continue to be processed. Most users would reasonably expect CCs to be considered part of the clip, since a clip is defined as a sequence of MIDI events between two points along the timeline. SONAR reinforces that assumption, e.g. if you slide a clip any CCs within it will follow along. It would be logical, then, to expect CCs to be muted along with the clip.
 
However, it should be noted that the concept of muting continuous controllers does not exist in the MIDI spec, only notes.
 
In fact, clips and clip mutes are also not part of the MIDI spec. Those constructs exist entirely within the DAW, and can thus be implemented any way the DAW designer sees fit. So whether the behavior described by the OP is a bug or not depends entirely on what Cakewalk intended when they originally invented the clip-mute feature. You'd have to ask Greg Hendershott about that.

Steve_Karl
 
My suspicion is that the controllers that aren't being muted are in a different take than the notes and that controller take isn't being muted alont with the take that has the notes in it.

In my case that was not it. Two different takes where I muted one, and got strange cut off notes on the new take at playback. Only way to get rid of it was to drag muted clip to another track not pointing to this instrument.
I also remember Susan G acknowledged this at some time like 10 years ago when a third person mentioned something on this.
If it appeared on Features and Ideas I don't remember. It might be on forum archive still.
 
So something is common with current Sonar and those days it seems - in how controller #64 might be handled.
 
Knowing about it and no problem to work around it though.
I used to make new takes on different tracks, and instead of muting point to no instrument.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Steve_Karl

lfm
Two different takes

It might be the "takes" conscept. I never use comping. It's always seemed tedious to me.
I always stay in sound on sound and just blast away,
CTRL+Z to get rid of the last one and re do until I like it ...
... and if by change I'm note sure if I can top what I just did, I clone the track and mute it.

It was just two recordings, serving to be like takes - muting first manually, and do another recording.
 
I even did on different track, create a new track and mute the other one.
Not the named "takes" feature, looping or so.
But as long as a muted clip/track was assigned to same VST instrument, CC#64 could influence.
 
It was a coincidence that I discovered it, since one take pedal just happend to be used on a spot that cut off notes on currently playing. I think I spent an hour or so looking for other things, before thinking about muted stuff.
 
A bit strange if it still is there as OP posted - if exactly the same thing.