ULTRABRA
I don't see why there should be any other way than this:  at the time of release of X4, the known bugs of X3 should be given as a free update to those who have X3, and to those who then want to purchase X4 (for whatever extras it will offer) then they can do so.  But X3 users should not be forced into purchasing an upgrade to eliminate known bugs. 

It's thinking like this that will move Cakewalk to using a subscription model. Then it will be official: If you want the bug fixes, keep your subscription active.
 
Now, I've been affected by this bug a few times as well, but I'm okay waiting for the fixes in the next release because I would rather have X4 be a solid release than have the bakers spending time regression testing X3 patches and then not doing enough to ensure that X4 is a clean release.
 
Regards,
Dan

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. So this is why this has been a show stopper bug for me forcing me to stay with 8.53, obviously I would vote for a new patch for X3. We don't know how close X4 is to actually being released and even the targeted release date, that only Cakewalk knows about, may end up being delayed if the beta testers find more important bugs to fix. So an X3 patch may be the best solution.

dcumpian

ULTRABRA
I don't see why there should be any other way than this:  at the time of release of X4, the known bugs of X3 should be given as a free update to those who have X3, and to those who then want to purchase X4 (for whatever extras it will offer) then they can do so.  But X3 users should not be forced into purchasing an upgrade to eliminate known bugs. 

It's thinking like this that will move Cakewalk to using a subscription model. Then it will be official: If you want the bug fixes, keep your subscription active.
 
Now, I've been affected by this bug a few times as well, but I'm okay waiting for the fixes in the next release because I would rather have X4 be a solid release than have the bakers spending time regression testing X3 patches and then not doing enough to ensure that X4 is a clean release.
 
Regards,
Dan

In this case though, you've already paid your "subscription" by buying X3 in the first place, and then again in buying the X4 upgrade aswell.   The final version of X1, X2, X3, etc should be at least clean of the KNOWN bugs, before expecting us to purchase the next version.   

Hi Gerry and those experiencing this issue,
 
The bug here is a problem with how events are rendered in Sonar. Essentially, in some cases we're interpreting controller information that is at 0 as a note off rather than a controller event at 0. This is rare but can manifest easiest with CC64 Pedal events and effects pianists the most. 
 
In MIDI, Pedal off is CC64 with a value of 0 to 63. In cases where you are running into problems with pedal,  you can convert the CC64 off from 0 to 1-63. The Process - Find/Change feature can be used for this. Here's the procedure:
 
1. Select the MIDI clip/s that are are problematic with Pedal events.
2. Open Process - Find/Change window.
3. Click the None button at the bottom RH corner of the window to clear all fields. 
4. Click the check box next to Control.
5. Under Number type in 64 for Min and Max (this is the controller event). Under Value type 0 for Min and Max. Hit OK. This searches all controller 64 events with a value of 0.
6. The view will remain open after OK. Next under Number verify 64 is set for Min and Max. Under Value type in 1 for Min and Max. Hit OK. This will convert all pedal events (CC64) at 0 to 1. From this point pedal events will work as expected. 
 
You can save this event filter search as a preset for more convenient use.
 
Subsequently, if the problem occurs in a single area, you can use the Event List editor or PRV Controller lane to edit the CC64 event from 0 to 1 in the location this is occurring. Alternatively, in the PRV, zoom out all the way, Lasso select just the CC 64= 0 events and shift drag them up (shift is the constrain modifier so the events do not move in time) to a value greater than 0 but less than 63. 
 
Some keyboard controllers will also allow you to constrain controller events. If your controller has an edit page for the pedal, set it so that pedal off = 1 rather than 0. This would eliminate the need for the above steps. 
 
The description seems lengthy but it takes only a few seconds to perform. This should resolve the issue for you until a fix is distributed. 
 
If you have any questions, please let me know. 

Dan,
 
Thank You for shedding some detailed light on this problem and a work around.
 
Kind regards,
Rick Tucker

A CAL scriipt which could be bound to a shortcut would be
;; quick fix for CC64 = 0 bug
(forEachEvent
   (if (&& (&& (== Event.Kind CONTROL) (== Control.Num 64)) (== Control.Val 0))
       (= Control.Val 1)
   )
)

 
 

ULTRABRA

dcumpian

ULTRABRA
I don't see why there should be any other way than this:  at the time of release of X4, the known bugs of X3 should be given as a free update to those who have X3, and to those who then want to purchase X4 (for whatever extras it will offer) then they can do so.  But X3 users should not be forced into purchasing an upgrade to eliminate known bugs. 

It's thinking like this that will move Cakewalk to using a subscription model. Then it will be official: If you want the bug fixes, keep your subscription active.
 
Now, I've been affected by this bug a few times as well, but I'm okay waiting for the fixes in the next release because I would rather have X4 be a solid release than have the bakers spending time regression testing X3 patches and then not doing enough to ensure that X4 is a clean release.
 
Regards,
Dan

In this case though, you've already paid your "subscription" by buying X3 in the first place, and then again in buying the X4 upgrade aswell.   The final version of X1, X2, X3, etc should be at least clean of the KNOWN bugs, before expecting us to purchase the next version.   

In a perfect world, that would be the case. But old bugs surface every day, so that is impractical, at best. As far as I can tell, once Cakewalk begins work on the next version, in earnest (that's when the bakers largely disappear from the forums), the current version's code base is "frozen". Without having a second development team to migrate bug fixes to older versions (while excising code that is an enhancement or new feature), I just can't see them working on two builds at once.
 
Regards,
Dan
 
 

 
What makes Cakewalk's approach acceptable to me is that they offer very reasonable pricing on the upgrade if you wait for it to go on sale.  The price is such that you can consider you're buying the new goodies for a very good price and you then get the bug fixes 'for free' along with them.  At least that's how I've come around to thinking about this.
 

dcumpian
Without having a second development team to migrate bug fixes to older versions (while excising code that is an enhancement or new feature), I just can't see them working on two builds at once.
 

And that's the issue in a nutshell. Applying a bug fix to a previous version is a different process compared to building it in to a new version. For one thing, the QC process is different for separate versions, and QCing is a major factor in software development. 
 
The cost of having another development team dedicated to migrating bug fixes to older versions would raise the price of updates considerably, or require raising the software's initial price in anticipation of continuing to develop it after newer versions appear. This is why most music software companies operate the same way as Cakewalk does. The companies in this industry aren't big enough to be like Microsoft and offer patches to versions that are no longer being sold.

scook
A CAL scriipt which could be bound to a shortcut would be
;; quick fix for CC64 = 0 bug
(forEachEvent
   (if (&& (&& (== Event.Kind CONTROL) (== Control.Num 64)) (== Control.Val 0))
       (= Control.Val 1)
   )
)

Your CAL script works great. I have it set up with a shortcut. I can now select a piano track, hit the shortcut and it's instantly fixed. Great time saver! I'm glad we still have some guys like you into CAL. And thank to Daniel Cate for this workaround and good explanation of what's happening with this bug.
 
I didn't solve some Win 7 problems with my sound card until March, so when I upgraded to X3 on March 22, the latest patch was X3e. I think by that time Cakewalk was already starting to consider X4 work. Maybe that's about the time the bakers disappeared from the forum. I didn't see any other posts about this bug in the forum, so I assume this bug must have been too low on the radar to concentrate on.
 
I have a feeling if I would have had this post up in the early stages of X3 in stead of 4/27, it would have likely been addressed, especially considering that tech support was also onto this bug after I alerted them.  At this point I'm glad that Noel zeroed in on this bug and fixed it in X4 and that we now have a workaround with the CAL script. So I feel better now.