Hi,
I haven't quite worked my way through all of this thread, but I have similar pedal problems. I mostly use Vintage D. Find I have to go in and move pedal points in the piano roll, usually involves sliding the pedal 'offs' back a bit all the time. Particularly noticeable when you lift the pedal just before you play the next chord, then in piano roll view the 'off' doesn't happen before the chord, but just after you've played the chord, so at the point where the next chord happens, the sustain pedal is still on. Very annoying.
I think as well that I've saved a project and when I reopen the project, the pedal points have moved again.

gmp
 
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.

Thats a bit harsh. Every software product on the planet has bugs and and 8.5 had far worse bugs than any of the X series. You probably just didn't notice them in your workflow.
 
I agree that it is an important issue - I fixed it a few weeks ago. It was a silly bug caused by some code that was misinterpreting a MIDI CC message with a value of zero as a note off message (because of a fault MIDI status bit check). This was leading to genuine CC's with a value of 0 (like CC 64 pedal events) being dropped. Its very hard to spot this bug normally since you wouldn't notice a CC with a value of zero being dropped since typically you get a sequence of CC's rather than a single event as occurs with CC 64. Also to compound the problem, it would only occur in certain cases depending on the duration of prior notes. This is why it wasn't obvious and not noticed earlier. 
 
While fixing this I also addressed some other related issues dealing with CC's in cropped clips and controller search back. that dated back to over 15 years ago - so much for the theory of 8.5 working fine :) Anyway pedal and CC rendering should be improved in the next version...

Noel Borthwick [Cakewalk]

gmp
 
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.

Thats a bit harsh. Every software product on the planet has bugs and and 8.5 had far worse bugs than any of the X series. You probably just didn't notice them in your workflow.
 
I agree that it is an important issue - I fixed it a few weeks ago. It was a silly bug caused by some code that was misinterpreting a MIDI CC message with a value of zero as a note off message (because of a fault MIDI status bit check). This was leading to genuine CC's with a value of 0 (like CC 64 pedal events) being dropped. Its very hard to spot this bug normally since you wouldn't notice a CC with a value of zero being dropped since typically you get a sequence of CC's rather than a single event as occurs with CC 64. Also to compound the problem, it would only occur in certain cases depending on the duration of prior notes. This is why it wasn't obvious and not noticed earlier. 
 
While fixing this I also addressed some other related issues dealing with CC's in cropped clips and controller search back. that dated back to over 15 years ago - so much for the theory of 8.5 working fine :) Anyway pedal and CC rendering should be improved in the next version...

 
This is such good news, Noel. I'm so happy you fixed it and also found a few more related issues. Sorry for any harshness, I've just been very frustrated not being able to use X3, and was beginning to wonder why it wasn't being fixed. I see now from your response that it wasn't an easy one to find. Thanks again, already you've restored my faith! I'm so glad you're still around I remember you back in the early days of Cakewalk. I look forward to X4.

Noel Borthwick [Cakewalk]

gmp
 
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.

Thats a bit harsh. Every software product on the planet has bugs and and 8.5 had far worse bugs than any of the X series. You probably just didn't notice them in your workflow.
 
I agree that it is an important issue - I fixed it a few weeks ago. It was a silly bug caused by some code that was misinterpreting a MIDI CC message with a value of zero as a note off message (because of a fault MIDI status bit check). This was leading to genuine CC's with a value of 0 (like CC 64 pedal events) being dropped. Its very hard to spot this bug normally since you wouldn't notice a CC with a value of zero being dropped since typically you get a sequence of CC's rather than a single event as occurs with CC 64. Also to compound the problem, it would only occur in certain cases depending on the duration of prior notes. This is why it wasn't obvious and not noticed earlier. 
 
While fixing this I also addressed some other related issues dealing with CC's in cropped clips and controller search back. that dated back to over 15 years ago - so much for the theory of 8.5 working fine :) Anyway pedal and CC rendering should be improved in the next version...

 
With all due respect, this is a serious issue so why are we waiting for the next version?  I would hope that this would be released as an update/bug fix as soon as the beta team gives the go.
 
Kind regards,
Rick
 
Edited for formating

> this is a serious issue so why are we waiting for the next version?  I would hope that this would be released as an update/bug fix as soon as the beta team gives the go
 
As one who has encountered this bug in the past (but not reliably reproduceably), I trust Cakewalk to weigh the reporting frequency of particular issues against their dev/test/ship timeline and decide whether to devote resources to issuing a patch release ahead of the X4 release.
 
It sucks because based on release history, there is no way an update for X3 will be released once X4 is out. The path to bug fixes will be through X4 upgrades, not retroactive patches.
 
Speaking for myself, if I got to vote on which way to go, I'd vote for the X4 path.
 
 

stickman393
 
It sucks because based on release history, there is no way an update for X3 will be released once X4 is out. The path to bug fixes will be through X4 upgrades, not retroactive patches.
 
Speaking for myself, if I got to vote on which way to go, I'd vote for the X4 path.
 

This is exactly the same thing that happened to the folks who chose to stick with X2 when X3 was released. If they did not spend the money to upgrade they were stuck with the X2 bugs that were/had been known issues as I recall.
 
I hope to upgrade to X4 but, at this point, I have no idea what changes that brings. I see things on the Forum that speculate about a subscription vs. a purchase, things about the license potentially requiring internet connection. I would not support either of those. We have No real info from Cake to dispel those rumors but it would be nice.
 
I do know that two of the questions I answered on the survey was about subscriptions and my internet connectivity.
I don't see much cake can add to the existing product that would interest me except fixing the bugs they know are there and already have fixes for.
 
If this becomes a 'Buy a Bug Fix' then fine with me but get them out to the folks as soon as they are ready to go, not wait until the next version release...

I've had these same issues --- I had put it down to user error (LOL), and its DEFINITELY something that should be released a free update.   Went thorugh the same issues previously when left with bugs in X2 and being forced to buy X3.  I won't do it again.

Thanks for the update Noel. Being a keyboard player this has been quite an annoying issue and I for one am glad you've found it and look forward the fix.
There are a number of other threads that have discussed the issue of fixing known bugs in an update or rolling them into the next release, I guess it's just a matter of timing.
 I do understand the frustrations of those users that have had to wait for this to happen, there have been two projects of mine that have had quite a bit of extra editing time put into them to overcome this issue. But I also understand the difficulty of undertaking an update to X3. If I have to wait until X4 then so be it, you have increased my appetite for said update.

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. 

My guess is that the bug fixes have already been built-in to the X4 code now. Highly unlikely there is a separate patch that would work with X3 code. Again, just a guess on my part...
 
If Noel or someone from Cake would like to clear this up it would be Greatly appreciated.
 
Kind regards,
Rick