If you hit a note on your piano. It first sends a "note on" message out of your midi cable to X3, and as soon as you lift you finger off the note it sends a "note off" message. Both messages are recorded, but in the event list all we see are the note on messages. So it's possible this bug is more of a note off problem than a sus pedal problem. Both problems sound very similar with sustaining notes.

 
Interesting thread.  Forgive me if I missed this (I've been following from time to time, but not every detail).  What model of MIDI controller or keyboard are you using for input?  The reason that I ask is that I've always had more similar problems - over many Sonar versions - with controllers that transmit true Note Offs.  This opposed to the "legal" Note On with a velocity of 0 as a Note Off substitute.
 
I've always suspected that keyboards with a Note Off variable release value tend to muck up the works in Sonar.  Never proven.  I have a number of KBs and MIDI controllers here, and by far the instances of "stuck notes" happen more often in the true Note Off devices.

b rock

If you hit a note on your piano. It first sends a "note on" message out of your midi cable to X3, and as soon as you lift you finger off the note it sends a "note off" message. Both messages are recorded, but in the event list all we see are the note on messages. So it's possible this bug is more of a note off problem than a sus pedal problem. Both problems sound very similar with sustaining notes.

 
Interesting thread.  Forgive me if I missed this (I've been following from time to time, but not every detail).  What model of MIDI controller or keyboard are you using for input?  The reason that I ask is that I've always had more similar problems - over many Sonar versions - with controllers that transmit true Note Offs.  This opposed to the "legal" Note On with a velocity of 0 as a Note Off substitute.
 
I've always suspected that keyboards with a Note Off variable release value tend to muck up the works in Sonar.  Never proven.  I have a number of KBs and MIDI controllers here, and by far the instances of "stuck notes" happen more often in the true Note Off devices.

I use a Yamaha P200 88 key Piano as a controller that I've used for 15 years and I have 2 midi interfaces I can use - MidiSport 2x2 and MOTU FastLane. I've had every Cakewalk version since DOS and X2, this is the first time I've had a severe problem. Maybe some intermittent ones in the past.

I use a Yamaha P200 88 key Piano as a controller

Well, there goes my theory.  Transmits 9nH v=0 as Note Off.

b rock

I use a Yamaha P200 88 key Piano as a controller

Well, there goes my theory.  Transmits 9nH v=0 as Note Off.

I appreciate you putting forth any theories. At this point I'm grasping at straws. This is baffling.
 
Have you tried to load my CWP or BUN file to see if it's happening with you? If you find that you do have the problem and then try it in X1 or 8.5 you'll see the problem goes away.


 
Here they are
https://onedrive.live.com/?gologin=1#cid=C256E2DAE26B22A5&id=C256E2DAE26B22A5!105

brundlefly
Gerry, good news, sort of... 
 
I am able to reproduce the problem with the first of the two new bundle files you posted. And more interestingly, when I dragged the MIDI clips out of the project and imported them into a new one started on my machine, the problem persisted with the "bad" clip.
 
I've now edited them down to a point right after the second pedal up where the bad clip continues to sustain notes that end both before and after the pedal up, while the good one stops sounding at the last note off after the sustain up. And this persisted after I applied trimming, and even after bouncing to clips.
 
Where it got really weird, though, is when I exported/imported the "good" and "bad" bounced clips a second time; now they both misbehave on playback, and neither the first nor second pedal up are honored.
 
And finally, if I open the clip as MIDI in X1 or 8.5 and insert a synth, it plays properly. But If I do this in either X3 or X2, the pedal ups are not honored. So for me, whatever this is is goes back to X2 in terms of playback.
 
I'll be comparing preferences between my SONAR versions and experimenting other clip modifications to see if I can nail this down a little better for a Problem Report to the Bakers.

I forgot to ask you. How was this new bun file? When you opened it did Truepianos automatically load? Were you then able to hit play and the unmuted midi track played back? Or did you have to make adjustments?
 
This is important, because I want to upload an example to Cakewalk that works to show the problem without any need for fiddling around. This way they'll see this as a bug, especially after they open the same file in X1 and see the problem go away.

Yes, Cakewalk TruePianos loaded right up, and the project was pretty much ready to play except that the output of the synth track was set to None rather than defaulting to Main Outs 1/2, and the audio tracks were set to Out 3/4 instead of 1/2. SONAR warns that the synth track is assigned to a "silent bus" so its not a problem and doesn't affect the ability to reproduce the issue.
 
Incidentally, I would not slip-edit the clips down because they will want to see the whole thing, and might be inclined to suspect that the slip-editing is causing the problem otherwise.

brundlefly
Yes, Cakewalk TruePianos loaded right up, and the project was pretty much ready to play except that the output of the synth track was set to None rather than defaulting to Main Outs 1/2, and the audio tracks were set to Out 3/4 instead of 1/2. SONAR warns that the synth track is assigned to a "silent bus" so its not a problem and doesn't affect the ability to reproduce the issue.
 
Incidentally, I would not slip-edit the clips down because they will want to see the whole thing, and might be inclined to suspect that the slip-editing is causing the problem otherwise.

Good to hear, yeah the outputs are not a problem. The reason I'm giving a shorter example is so they can hear the problem quickly and A-B it to the good track and then load it into X1 and see that the problem has gone away. I'll explain why the example is short, so they don't jump to conclusions about slip editing. Yet even if they question the slip editing, it still shows there's a bug, since X1 plays it back just fine.
 
So when you think back, do you think you've had any sustain pedal issues when you've recorded pianos and played them back? I know initially I just tuned it out, thinking I did something wrong or it was a rare anomaly, yet when I kept seeing it occur, that's when I zeroed in on it.

In thinking back, I may have seen this once. But it only affected one note in a ~4-minute performance, and when I moved the pedal up a few ticks earlier the problem went away and I promptly forgot about it. I think I haven't encountered it more often because the "piano" sound I work with most often is from layered hardware synths that aren't affected by this soft synth buffering issue.

Has this bug been addressed?  I'm seeing it in X3 when entering pedals by hand and playing through Dimension Pro.  Some pedal ups are ignored, and I can't always fix it by adding another pedal up before the last note off.
 
 

lstorrow
Has this bug been addressed?  I'm seeing it in X3 when entering pedals by hand and playing through Dimension Pro.  Some pedal ups are ignored, and I can't always fix it by adding another pedal up before the last note off.
 
 

Cakewalk is aware of the bug. I worked with Tech support on the phone for a good while twice and he acknowledged it was a bug. I've used Cakewalk products since the DOS days and the X series is the first one that had show stopper bugs that were not addressed and fixed.  X1 and X3 have had show stopper bugs, so I'm still using 8.53.
 
There's no way I'll have a client in my studio and play a perfect piano part only to find there are sus pedal errors that I have to fix and waste studio time. I just hope it's fixed in X4. I'll use their trial version first, since I've lost my trust in their integrity.