Try increasing your MIDI buffer setting in Preferences.

Just a thought - all MIDI data is recorded at the START of the MIDI note. If you play a fraction too early (a few milliseconds before actual recording starts) all MIDI data is not recorded and the note is lost. If you are too early only the note length would remain without any pitch etc. information and this is clearly not enough to effectively create a note. Your reaction time varies over the day, from day to day and when you are agitated or not. Maybe quantize at recording will help? As I said - just some toughs, no idea if I am sprouting nonsense or something ;-).

yeah, that is nonsense. you play a note at anytime during the count-in and it will be placed right on 0 and play back fine and on time.

We've had this come up on the forum many, many times in the past.

The recommendation - as always - is NOT to start your Midi data at 01:01:000

Start at measure 2, even 3 or 4.

This way everything (Sonar/Interface/Midi/Tempo etc) is able to get in sync and do it's stuff before you hit any Midi notes

Bristol_Jonesey


We've had this come up on the forum many, many times in the past.

The recommendation - as always - is NOT to start your Midi data at 01:01:000

Start at measure 2, even 3 or 4.

This way everything (Sonar/Interface/Midi/Tempo etc) is able to get in sync and do it's stuff before you hit any Midi notes

+1
 
starting a midi song at 02:01:000 has been accepted practice essentially forever... no matter what sequencer you have..
 
 

JClosed


Just a thought - all MIDI data is recorded at the START of the MIDI note. If you play a fraction too early (a few milliseconds before actual recording starts) all MIDI data is not recorded and the note is lost. If you are too early only the note length would remain without any pitch etc. information and this is clearly not enough to effectively create a note. Your reaction time varies over the day, from day to day and when you are agitated or not. Maybe quantize at recording will help? As I said - just some toughs, no idea if I am sprouting nonsense or something ;-).

Understand your point, but in my case it was a MIDI note that I'd entered manually via step record. 

Increase value of Prepare Using <value> Milliseconds to 500 in MIDI preferences if it's less than that. SONAR X* defaults to 250 which is too low for some systems, and is the most common cause of dropped MIDI notes.

Yeah I already had increased it to 500 because of problems using R-Mix, so it wasn't that unfortunately. 

sharke


Yeah I already had increased it to 500 because of problems using R-Mix, so it wasn't that unfortunately. 

fwiw, imo the correct answer here is in Jonesey's post above... it is simply good practice to start any midi based song at measure 2.. there is simply no way you can ever guarantee correct operation of a midi song by doing otherwise... regards.

fwiw, imo the correct answer here is in Jonesey's post above... it is simply good practice to start any midi based song at measure 2.. there is simply no way you can ever guarantee correct operation of a midi song by doing otherwise... regards.

I have to disagree with that. The vast majority of projects on the vast majority of systems should play back correctly from time zero.  In my experience, specific problems with this can (and should) be resolved with system or project tweaks, rather than making it SOP to start all projects later in the timeline. If there is a widespread issue with this, sample projects should be sent to Cakewalk for them to troubleshoot and resolve with code changes if necessary.