Random missing MIDI notes

I've recently been experiencing a phenomenon where certain, seemingly random MIDI notes are not being played back by BFD 3 & BFD Eco, which I use for full studio productions and demo/sketch pad purposes respectively. I believe it began happening around the time I upgraded to Platinum, although this was around the same time I added BFD Eco to my repertoire, so I couldn't say for sure what change started the problem. I don't think this is happening with any other instruments, though drums are the easiest to detect with this sort of thing.
 
While the missing notes appear to me to be random, each time playback is started from a certain point, it seems to be the SAME notes that are dropped on each playback. I would estimate that 1 of every 10 to 20 notes gets missed, but in some occasions I've heard significantly more of them lost. I usually have a few MIDI instruments going in a project, but this happens even when there is only a sparse drum track and 3-4 audio tracks playing back.
 
Yes, this had happened since the Platinum update a few days ago. Has anyone else encountered this behavior? What did you do?

I've had to jack my buffers right up to 2000!
 
If this doesn't work, make sure your Midi notes are short and all of the same length.
I find a length of 60 ticks works perfectly.

Go into the prv. Sweep with your mouse on the keyboard to the left so that all notes are selected.
 
Type '60' in the Event Inspector's duration field

This happens to me when using drum maps no matter what. I'm using Superior Drummer, SSD4, Drumforge (in kontakt) and other K5 libraries and even a project with Addictive Drums. Raising the buffer did some good, but the problem never went away completely...until I disabled the drum map.
 
I also noticed that it seems to happen after a certain amount of playback. I'm about to finish my project Sonar Platinum project pretty soon and I see I'm going to have to disable the drum map when rendering.

Once you're happy with the drums bounce them down to audio tracks. Then you can delete the MIDI tracks and any MIDI-related issue should disappear.

My approach to mixing is, other than rough mixes as I go along, once everything's tracked I get rid of all the MIDI tracks and just work with audio. Less system load if I decide to add in more effects and fewer console channels to be dealing with.

I must admit I've been seeing this too, with Superior Drummer 2 routed through a drum map in Sonar Platinum. I thought that maybe the VSTi just hadn't loaded the samples yet, but I have it set to load them all at startup so that shouldn't happen. So, chalk this up as a potential "me too".

Jim Polishski - That seems to have done the trick! I only tested it on one project so far, but that was the song with the most problems, so I'm highly optimistic. For the rest of you ...
 
"C:\Users\(your user name)\AppData\Roaming\Cakewalk\SONAR Platinum" is the default location.
"TTSSEQ.ini" is the file name.
 
Just move/delete it and viola, drums! Thanks again for all the input.

Are Cakewalk aware of this issue? Do we need a thread in the Problem Reports section?

Interestingly enough, for me it's also the snare sound that seems to drop out. I don't know if the problem is intrinsic to that MIDI event, or whether the other drum kit pieces are just played quietly enough and less frequently enough for me to not notice when they are absent.

Ok, I have a project where I can reliably reproduce this now.

1. It persists across restarts of Platinum
2. It persists even though I renamed ttsseq.ini
3. Whether the hit in question fires or not depends on where I start playback. I have a drum clip stretching from bar 203 to 211. If I start playback at 202:01:000 exactly, the hit at 205:01:479 does not trigger. If I start playback from anywhere else, including 202:02:000, or 201:04:000, or anywhere close to 202:01:000 but not exactly on it, it works.
4. It seems unrelated to the quantity of hits, because I am finding that a snare drops out when a kick does not, despite there being the same number of each in the clip and them being at roughly the same times each occurrence (it's a fast metal beat)
5. The 'where I start playback' issue is relative, not absolute: if I move the clips somewhere else in the song and still start playback exactly 1 measure before the clip begins, the problem persists.

There is only one VSTi playing (Superior Drummer 2), and it is going through a drum map where all the notes in are the same as the notes out. (It's just used to show note names in the Piano Roll.)
 

Bristol_Jonesey
It's not just snares, I'm getting dropped notes on Kick Drum events.

Yeah...I've experienced it with snares, kicks, HH...etc.  But once a note is dropped, it will stay dropped until I move it a tick or two.

Add me to the chorus of dropped notes while using midi triggered drums. I've tried every combination for the last two hours of upping and lowering my midi buffers and audio buffers. Things were fine until I looped a small section, and immediately the notes dropped. After looping, I couldn't get the notes to trigger. I even shut down the project, reopened it, and the notes were still dropping.
 
I had posted in another thread about how it was weird for the keyboard to not trigger AD2 when I was using a drum map. Don't know if this is related or not.

Kylotan
Ok, I have a project where I can reliably reproduce this now.

1. It persists across restarts of Platinum
2. It persists even though I renamed ttsseq.ini
3. Whether the hit in question fires or not depends on where I start playback. I have a drum clip stretching from bar 203 to 211. If I start playback at 202:01:000 exactly, the hit at 205:01:479 does not trigger. If I start playback from anywhere else, including 202:02:000, or 201:04:000, or anywhere close to 202:01:000 but not exactly on it, it works.
4. It seems unrelated to the quantity of hits, because I am finding that a snare drops out when a kick does not, despite there being the same number of each in the clip and them being at roughly the same times each occurrence (it's a fast metal beat)
5. The 'where I start playback' issue is relative, not absolute: if I move the clips somewhere else in the song and still start playback exactly 1 measure before the clip begins, the problem persists.

There is only one VSTi playing (Superior Drummer 2), and it is going through a drum map where all the notes in are the same as the notes out. (It's just used to show note names in the Piano Roll.)
 

Like I said earlier, whenever I experienced that exact same issue, I removed the drum map and the dropped notes stopped occurring. Everything played back fine. It appears to be an issue stemming from drum maps.

Vern C is correct. I went back in this morning and disabled the drum map in my project. The weird thing is, I had two drum maps for AD2, and both of them said that they had been changed. I only loaded one, and didn't change anything. I can now play back my drum tracks without drop outs, and the piano roll works like it always did. Going to sit down and make a laminated copy of the drum map. Going to keep things as simple as possible from here on out.

Kylotan
Yesterday I saw a weird bug where Platinum had created 5 or 6 extra drum maps for my project, besides the one I actually use. I wonder if some half-finished work on the drum maps accidentally slipped into the last release.

I've had that happen when I tried to insert a new drum map in a project and assign the outputs of multiple MIDI tracks to it at the same time by quick grouping. SONAR interprets that as "create a new drum map for each of these tracks and assign the output to it". You need to add the drum map first, and then quick-group the MIDI track output assignments to it. I don't think this behavior is new to Platinum.