MIDI latency

There is a default setting in Sonar that handles turning the Midi Input Echo on/off, as you move from one midi track being in focus to a different midi track.
 
So, if I have the midi track for my piano in focus (selected), Sonar will automatically turn that track's Midi Input Echo to 'on'.  This makes it so I can hear the piano notes when I play notes on my midi controller.
 
If I then click on the midi drums track, Sonar will turn Midi Input Echo for the piano track to 'off'', and will turn it 'on' for the drums midi track.  This makes it easy to move back and forth to different midi tracks, and be able to hear only the sounds you want to hear, the ones for the midi track that is in focus.
 
You can also manually turn Midi Input Echo on/off, and I use this approach when I want to hear a layered sound, such as piano with strings, or violins with cellos or that sort of thing.
 
I would imagine you have Midi Input Echo set to 'on' for more than one midi track, and have it this way from either manually setting it, or the setting in Sonar that controls it happening automatically has been turned off.
 
To fix the problem, click Midi Input Echo to 'off' for all the midi tracks you DON'T want to hear the sounds from while playing, and make sure the Sonar setting that automatically handles it for you is set the way you really want it.
 
The setting in Sonar that controls it being handled for you is in:
 
Edit>Preferences>MIDI>Playback and Recording, and the setting is called 'Always Echo Current MIDI Track'.  Make sure this is checked if you want Sonar to handle it for you.
 
Bob Bone
 

Nomenclature.
 
I keep calling songs projects. When you press the monitor button it will send the input through the channel, whether midi or audio.
 
Then like Robert was saying there's a setting for automatically monitoring when you click on a track.
 
You can monitor many tracks and hear them all as you play to layer sounds.
 
 
 
Midi latency is a misnomer, used for audio latency. That doesn't sound like what you have if you have two of them.
 
There is midi latency but it's very minor but can cause real problems with intricate timing situations.
 
Like Robert was saying local off should fix the problem.
 
You want local off then have a midi track sent back to your keyboard so it doesn't sound until the midi messages make the round trip through the software and back to the keyboard.
 
If you're using an external keyboard, you don't say.
 
 

ok, got it fixed.  Uninstalled the Edirol UM2 drivers, rebooted, reinstalled, rebooted, now it works. 

Have you tried shifting the driver mode (Preferences->Audio->Playback and Recording)? I have noticed latency from my MIDI controller based on the driver mode used.

tindog13
Thanks for the info... I was only using one midi track, so it wasn't that... I did find the Local control on the keyboard and turned it off (don't remember turning it on and I've recorded midi before, oh well)... and that fixed the echo, but the note I hear now is the latent note, there is a delay when I play. Clicking stuff all over the place, haven't found a solution.

So, what are your buffers set to now, or the ASIO panel latency? You haven't written a word about it. Is it simply set to the (once default) 50 ms?

Running in ASIO mode is preferred with drivers specific to your audio interface. An ASIO buffer of 128 samples is a good starting point to test latency within a project. Lower values will give you less latency, but add to CPU loading, so as projects get bigger it may need to be revisited. When you are mixing (post production), latency is no longer an issue, so adjusting these a step or two higher will allow the engine to run smoothly during that phase.
 
Just FYI, the ASIO buffer is not a "fire and forget" setting, but one you will need to revisit and be comfortable knowing how to adjust depending on what you are trying to achieve.

Shifting the drivers seemed to fix it after a computer restart. Thanks so much for the all the responses.