microapp - I changed my settings from 250 ms to 999 and it works perfectly.
Thanks for the tip! I'd never really seen this problem before. Something must be a little different in Platinum because I've always gotten by with the default 250ms setting.
 
I'm using Superior Drummer BTW - so it's not just a AD issue.

John,
I just got Platinum running last night so this is preliminary but I think it is using more CPU than X3.
My current PC ( been waiting for next Sonar to upgrade) is a Core 2 Duo so it makes it easier to notice compared to I5 or I7. Never seen an issue after setting to 999 though.

Mines a i7-3770K, but I haven't paid attention to see if it's any worse  on the CPU. I don't find the CPU meters that accurate anyway.
 
Something is different though. Anyway - setting to 999 did the trick. Going up to 500 (from 250) didn't cure the problem - but 999 did. There must be some downside to this - but we'll see... ;-)

jbraner
 
 
Something is different though. Anyway - setting to 999 did the trick. Going up to 500 (from 250) didn't cure the problem - but 999 did. There must be some downside to this - but we'll see... ;-)

Im sure there must be a down side to .. something to do with timing I suppose ..

Just another "Thank you".  I too had to move up from 250ms in order to get a beat right using AD2;  I went straight to 999 but may play with settings if I can find any details on possible problems.
 
Here was the odd part for me that had me pulling my hair out for the last two days.  Using AD2, if I did a Sync play/stop with the groove selected, everything was fine.  Once I dragged the beat into a MIDI track I started having problems.  
 
Anyway, back to mixing.
 
Matt

The only downside to increasing the MIDI buffer I'm aware of is you have to wait for the length of the buffer for the transport to roll on playback/record.

Why the default is 250 I have no idea, it turns up as a problem all the time. Many versions ago it used to default to 500 if my memory isn't playing tricks.