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.

Just curious...has anyone tried mixing down a section to see if the dropped notes actually render correctly in a mixed file?  I haven't tried this...actually just now thought of it.

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.

Teds_Studio
Just curious...has anyone tried mixing down a section to see if the dropped notes actually render correctly in a mixed file?  I haven't tried this...actually just now thought of it.

Hi Ted.
 
No, I haven't yet tried to bounce/freeze the project that's exhibiting this behaviour.
I'm currently engaged in mixing down vocals on my main DAW. I have to say that so far, this behaviour is only manifesting itself on my secondary machine, but i will, when I get a some "free" time (whatever the hell THAT is) I'll take a look.
Probably won't be until the weekend.

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.

I've posted in the Problem Reports forum because we don't seem to be getting any response or acknowledgement here.
http://forum.cakewalk.com...ing-used-m3192444.aspx

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.

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.

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.

I wasn't adding any new drum maps, and I only ever use them on one track. Sonar just did something strange. In fact, it's very common for me to open up the drum map manager and find that it has a 'spare' drum map that I didn't ask for, usually a duplicate of the one I am using. But all I ever do with drum maps is assign one, once, at the start of the project.