Don't expect Cakewalk to answer support requests on this forum. Calling support is the fastest (and best IMHO) way to engage Cakewalk support.

When you are cloning, are you cloning just a MIDI track or a Simple Instrument track? And are you leaving both tracks active so that all notes and controllers are are being doubled, or do you mute the original? If dupe events are being sent to the synth, I can imagine that would alter the rendering process just enough to fix an intermittent problem.
 
And are you still using TTS-1 for testing or is all of this with Ivory?
 
 
 
 

brundlefly
When you are cloning, are you cloning just a MIDI track or a Simple Instrument track? And are you leaving both tracks active so that all notes and controllers are are being doubled, or do you mute the original? If dupe events are being sent to the synth, I can imagine that would alter the rendering process just enough to fix an intermittent problem.
 
And are you still using TTS-1 for testing or is all of this with Ivory?
 
 
 
 

When cloning, I'm cloning just a MIDI track, never using a Simple Instrument track.  I mute the original and play back the clone and then mute the clone and play back the original and both are fixed, no dupe events. I'm using Ivory again. THis is very strange, I hope this workaround works everytime.
 
I'm beginning to wonder if you open my bun file and play it without altering anything or loading a synth if you would get the same problem? I think you now have TTS-1 installed don't you? If you still have to load the TTS-1 synth, could you not use the simple instrument? That may make a difference. Once you loaded the synth you could try it 2 different ways, one with copy and pasting my midi data into your midi track or you could change the input of my midi track to your synth that you had to load.
 
Also I can create a new bun in 64 bit X3 using True Piano. That way people may be able to open the bun and instantly play the file without loading anything.
 
Thanks for helping with this crazy problem.

I have to replace TTS-1 because I don't have the 32-bit DX installed. I seriously doubt if any of these machinations are going to reproduce the symptoms on my machine given that I've never seen it, but if you want to upload a project with 64-bit TruePianos (either the Cakewalk or Full version), I'll be happy to give it a go. To minimize the amount of fiddling needed to make it audible, remove all buses from the project, and set the output of the synth track directly to Main Outs 1/2.
 
 

Dupe Post
 
 

brundlefly
I have to replace TTS-1 because I don't have the 32-bit DX installed. I seriously doubt if any of these machinations are going to reproduce the symptoms on my machine given that I've never seen it, but if you want to upload a project with 64-bit TruePianos (either the Cakewalk or Full version), I'll be happy to give it a go. To minimize the amount of fiddling needed to make it audible, remove all buses from the project, and set the output of the synth track directly to Main Outs 1/2.
 
 

I reinstalled Win 7 from scratch. installed my Layla 24 audio, did all Win Updates+optional, motherboard updates, Nvidia updates, installed MOTU midi interface, installed X3 64 bit only. Opened the normal template played the piano and recorded it, had a few sus pedal problems.
 
Opened my bun file, loaded True Pianos, copied the midi data from TSS-1 midi track to True Pianos midi track. Played it and the sus problem was gone for that mdii track only. Then I went to the TSS-1 midi track and used Truepiano as the input and there was the sus problem.
 
I saved to a new cwp file, recorded the audio of the good Truepianos track and also the bad one, then saved it as a bun file. So you can try the CWP first if you like. I have a feeling it will show up this time. For some strange reason something gets reset when you copy midi data or clone the track like I did the other day. Cloning also gets rid of the problem.
 
I got rid of all the buses and pluggins to keep it simple. Hopefully Truepianos will load automatically. Here's where the CWP and BUN are
https://onedrive.live.com/?gologin=1#cid=C256E2DAE26B22A5&id=C256E2DAE26B22A5!105
I deleted the old files, so there's only those 2 files there.
 
Thanks for your help,

Interesting thread. I am not very versed in midi and thought that I was doing something wrong when recording. I get mixed sustain messages when recording in True Pianos, Dim Pro and Rapture. It seems like some times the sustain pedal works as intended, and some times it carries on for a lot longer than when I am telling it to stop. I also record the audio from my keyboard (Ensonique KT76) at the same time as the midi, and the sustain in the audio track works exactly as intended.
I can't remember having this issue before I updated to X3 and thought that maybe I'd changed setting. As I said, I'm not that savvy with midi and I hope that this is the problem being discussed and I haven't misread the entire thread. I'll keep an eye on this thread and hope I can pick up some pointers.

rebel007
Interesting thread. I am not very versed in midi and thought that I was doing something wrong when recording. I get mixed sustain messages when recording in True Pianos, Dim Pro and Rapture. It seems like some times the sustain pedal works as intended, and some times it carries on for a lot longer than when I am telling it to stop. I also record the audio from my keyboard (Ensonique KT76) at the same time as the midi, and the sustain in the audio track works exactly as intended.
I can't remember having this issue before I updated to X3 and thought that maybe I'd changed setting. As I said, I'm not that savvy with midi and I hope that this is the problem being discussed and I haven't misread the entire thread. I'll keep an eye on this thread and hope I can pick up some pointers.

You described the problem perfectly. You have it also. Your Ensonique KT76 is an external synth and it doesn't happen with any external synths like you reported, it only happens with the softsynths like Truepianos. It doesn't happen with X1, something changed with X3.
 
I recorded a punchy rhythmic piano the other day at a very brisk tempo - 237. I didn't even use the suspedal at all.  I had to stop several times and autopunch back in. Backed up about 4 bars. When I heard my recorded piano, I played along like I always do and every time I tried to autopunch I got all sorts of sustaining notes before the punch in point, until it punched in and then the notes died out. SO what this indicated is that X3 is not recording all of the note offs.
 
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.
 
I turned in a bug report on this and they said it's not a bug, but more of a unique problem with my computer. Since then I've found one other person in this thread that reported the problem, you make the 2nd. So I can get this back on the bug list and fixed, would you download my newer bun and cwp file and see if you notice the sustaining problem?
 
There are 2 Truepianos midi tracks. One is named "bad". All you need to do is play one midi track and then mute that track and unmute the other midi track and play it to see if you hear the sustaining problem. If you open the bun file instead of the cwp, you'll hear the audio versions - one bad Truepianos, one good.
 
 Hopefully Truepianos will load automatically. If it doesn't play, you may have to go to my midi track and click on "input" and make sure Truepianos is selected. IF Truepianos wasn't automatically loaded, you'll have to load it manually in the SynthRack, don't choose "simple instrument" instead choose a separate midi track and audio track and then go back to my midi track and changed the input to Truepianos.
 
Don't use copy and paste to paste the mdidi data into the Truepianos midi track, if you do somehow it resets the midi track and the problem goes away.
 
Here's where the CWP and BUN are
https://onedrive.live.com/?gologin=1#cid=C256E2DAE26B22A5&id=C256E2DAE26B22A5!105

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.

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.

Actually this is good news. I think i'll upload my new bun file to Cakewalk and let them know 4 people have now verified this bug. I renamed my download files. The CWP file was misnamed bun in the name, not the extension. I think you turning in a bug report will be good also, you may find more insight into this than I've found.


I'm looking into a related issue, but this one so far only applies to Ivory piano. I recorded a punchy rhythmic piano the other day at a very brisk tempo - 237. I didn't even use the sus pedal at all.  I had to stop several times and autopunch back in.
 
Backed up about 4 bars. When I heard my recorded piano, I played along like I always do and every time I tried autopunch I got all sorts of sustaining notes before the punchin point, until it punched in and then the notes died out. SO what this indicated is that X3 is not playing back all of the note offs.
 
After recording when I play back the track it sounds fine. All the note offs are correct. It just very annoying to have a rumble of sustained notes happening right before it autopunches in and then persists for a few more seconds until the hung notes die out. This happens with 64 bit and 32 bit X3. When I use Truepianos instead of Ivory, it works fine, so I hope this Ivory problem goes away after they fix this bug.