Major Sustain Problem

After about 20 years of Cakewalk/Sonar, I am considering abandoning this product if I can't figure this one out...
 
I am recording a MIDI piano that I play back with one of the synths that comes with SONAR. The problem is that the sustain pedal up (Control 64 value 0) does not seem to work. The result is that a chords keep playing in the next measure where a new chord is played.
 
I attached an example where I play a chord in measure 41, then in measure 42, I lift the pedal (64 - 0 at 42:01:005+), but the chord keeps playing.  I suspect that becuase I press the pedal again soon (42:001:020), the 64 0 is ignored. But why ? Seems like a bug to me.
 
I can give more details, if anybody will be kind enough to share whatever knowledge of this problem they may have.
 
Thank you so much!
Simon
 

Have you got another take on another midi track that is muted?  

Make sure no other midi track is routed into that soft synth (even if it is muted).

I'm thinking maybe some other CC64 data is messing with you?

info incorrect  fixed

Does your controller pane include ALL controller events?

The reason I ask is that whenever I want to use CC64, I can just draw them in the controller pane i.e. they are VISIBLE. I don't see them in your screen shots.

Yes, I know they're in your event list, so the question begs, is it the correct track?

Bristol_Jonesey,
 
Thanks for your reply.
Yes, they are there. I keep them further down.
 

Ok Simon, I'd try sorting this out in a methodical way.

Does it happen in all projects or just this one?

If it's just this one then your project is corrupt - start a new project and drag/drop into the new one

If it's on all projects then start by entering just ONE note into a blank project and start experimenting.

Use a short note of about 60 ticks so that you can easily determine whether the sustain (CC64) is what you're actually hearing rather than the natural decay of the piano key.

Make sure the note you enter is right on the grid at 02:01:000 (Snap = ON!)
Put your sustain event ever so slightly before (Snap = OFF!)

Try that and let us know what happens.

BluesMeister


AnalogKid17 & lfm, please don't let this thread descend into a flame war. There's some very good information from Cactus Music & Bristol Jonesy, it would be a shame to see this thread locked or deleted.

Cactus remark is not correct, and you talk about good info.
So don't memorize that.

Lifting sustain should silence the chord from 41, even if short.
A new sustain pedal down will not make that reoccur.
The chord started at 42 should still be sounding when keys are lifted due to pedal position.
We cannot see all events after 42.01.

But as I said, it's up to synth to interpret what is coming in.
So checking what is actually arriving from Sonar can be checked with a monitor plugin.
In this way you would also know whether any other midi tracks in project might be the cause(what xiwix said).
If you know that these events actually arrive to synth Sonar is not to blame.

There are different ways for plugins to handle event which has a on/off style of status.
You can either do it in certain position only, like quarternote or whatever, in which case you might miss an off/on/off state change like this.
I think the lowest resolution I encountered is 48 ticks per quarternote which very well could miss this state change.

If plugin actually read every event it should be able to handle the above sequence, if it actually received the data.

So those are the key issues. But drama queen does not realize that yet.

EDIT: My guess is hidden clips from other takes in the track, which might be muted, but Sonar still picks pedal events from the. Very easy to miss. I reported to Cake when running S4 6 years ago, and it's still there, this treatment of pedal events(I don't know maybe other Midi CC too). So xiwix advice was very good.

LFM, please don't refer to the OP as 'drama queen'. I realise English is not your first language but that's no excuse for unnecessary rudeness.

BluesMeister


LFM, please don't refer to the OP as 'drama queen'. I realise English is not your first language but that's no excuse for unnecessary rudeness.

- Well, don't kill the messenger.

This thread's first sentence started off with rudness and then begging for help.

He is probably off bashing Sonar somewhere else.
Or he already solved it.

BluesMeister


lfm, I agree the OP's first sentence was over the top, but rude? I think we have different interpretations of the word. And if it's any consolation, the Schnauzer shown in your avatar is my wife's favourite breed of dog.

I was a bit offended by him starting off getting help with those words, otherwise I would not put the final "cut the drama".
Just a friendly tip to get full attention from all Sonar users on this forum for anybody wanting help here.

Starting off by pissing everybody off is not the way to go.

To be honest, it's you that keep maintaining this conversation and it's becoming a never ending story.
You're nobodys dad-figure here telling anybody what to write. It's really off topic.

And still you keep bumping this thread to the top all the time.

And why do you ask if he got it solved, you have nothing to offer regarding this matter.
I don't know after how many postings, you have not made a single contribution to OP's matter?

You just want to be daddy....

He solved his problem already, I'm sure, with the advice he got here.