I haven't updated the Kontakt to the latest 5.6 since people have been complaining about many things. I've been having this odd problem lately (after Sonar 09 I think) that the input echo just stops working. Resetting instruments in Kontakt solves this but I cant be doing that all the time. So to be more precise this is the situation:
 
1) Started a new project
2) Made some music with a bunch of Kontakt libraries in one instance
3) Tried to continue my work and I can't get any sound by playing MIDI devices
4) The playback works just fine
5) Kontakt interface MIDI input is blinking so it's receiving the played MIDI
 
This is very odd and I can't continue my work at the moment. Any help would be appreciated. I might try the latest version of Kontakt if it solves the bug but a lot of people seem to have problems with it.

The latest version of Kontakt won't make any difference. What you are seeing is that there are some libraries that receive volume messages as midi continuous controller messages (CC). If you are not aware of this, and are not setting the required CC values in your midi tracks, Sonar can reset the CC values by default and thus turn the volume to zero. If you don't want to be bothered to properly set CC values in your tracks, you can disable this reset action in Preferences: Zero Controllers When Play Stops.
 
Regards,
Dan

Thanks Dan. I already reloaded kontakt and can't reproduce this but I will try that if this happens again. I've used Kontakt for some time and this has happened only recently. Where can you configure these CCs? I can't find any CC events on my tracks.

JoeHans
Thanks Dan. I already reloaded kontakt and can't reproduce this but I will try that if this happens again. I've used Kontakt for some time and this has happened only recently. Where can you configure these CCs? I can't find any CC events on my tracks.

When you record your midi, you can also record your midi cc data. Try the MOD WHEEL first, since it is the most commonly tied to volume. If the MOD wheel is actually used to modulate the sample, then you'll need to find which controller adjusts volume and record that by using midi learn. You can also, like I mentioned previously, just tell Sonar not to reset any controllers to zero.
 
Regards,
Dan

Sonar will secretly send controller messages even if the midi shows no events.
If you are so careless as to touch any knob or slider for the track, even if you put it back to the default: you've triggered one of Sonar's many monster functions.  Now there will be several midi messages sent. 
 
To see them, go into Kontakt, assign an instrument, edit with the Wrench (but don't save later ...).   Open Script editor.  Add a preset:  "Factory: Utitlities:  Midi Monitor".    Check "Verbose".   Check  All the options on the right side (Controller, Channel Pressure, Note Off, RPN/NRPN, etc).    If you can find a midi track where nothing was ever touched -- no data except All Notes Off (CC 123).   If you've touched volume, suddenly you'll be getting CC1, CC7, and CC11 too.   If you've touched pan, even if reset, then you'll always get CC10 messages.  
 
Press play.    You'll see the damn program has sent messages:   CC1, CC7, CC11, CC123 (this may be project dependent).     NOW if your preferences still have "Reset to Zero", as Dan said, those controllers that Sonar volunteered for you are going to be put at zero when you press Stop.   
 
So:  go to preferences and uncheck that option.   You'll have to do it over and over, for some reason Sonar resets it pretty often whether you like it or not (perhaps from opening a new project?)      Unless you use the Volume, Pan etc on the track: don't dare touch the sliders/knobs. 

Thanks guys. I will uncheck that. It seems to me this functionality would definitely need some rethinking from Cakewalk.
 
I had a similar problem few years ago when I started to learn the synth stuff in the first place. At that time I was advised not to touch the MIDI track sliders and I think I haven't in this case. But I can't say that for sure since I might have moved something with the mouse wheel by accident or some other unintentional actions.
 
By the way, shouldn't the sliders from Kontakt or MIDI tracks move to zero if there is a "hidden" CC doing it's thing? I checked many times and couldn't find any visible indication for no volume.

JoeHans
By the way, shouldn't the sliders from Kontakt or MIDI tracks move to zero if there is a "hidden" CC doing it's thing? I checked many times and couldn't find any visible indication for no volume.

Many of these are not always visible in Kontakt. They won't be visible in Sonar at all, except for the automation envelope/automation lane data.
 
Regards,
Dan

williamcopper
Sonar will secretly send controller messages even if the midi shows no events.
If you are so careless as to touch any knob or slider for the track, even if you put it back to the default: you've triggered one of Sonar's many monster functions.  Now there will be several midi messages sent. 
 
To see them, go into Kontakt, assign an instrument, edit with the Wrench (but don't save later ...).   Open Script editor.  Add a preset:  "Factory: Utitlities:  Midi Monitor".    Check "Verbose".   Check  All the options on the right side (Controller, Channel Pressure, Note Off, RPN/NRPN, etc).    If you can find a midi track where nothing was ever touched -- no data except All Notes Off (CC 123).   If you've touched volume, suddenly you'll be getting CC1, CC7, and CC11 too.   If you've touched pan, even if reset, then you'll always get CC10 messages.  
 
Press play.    You'll see the damn program has sent messages:   CC1, CC7, CC11, CC123 (this may be project dependent).     NOW if your preferences still have "Reset to Zero", as Dan said, those controllers that Sonar volunteered for you are going to be put at zero when you press Stop.   
 
So:  go to preferences and uncheck that option.   You'll have to do it over and over, for some reason Sonar resets it pretty often whether you like it or not (perhaps from opening a new project?)      Unless you use the Volume, Pan etc on the track: don't dare touch the sliders/knobs. 

Before trying to "explain" some of SONAR's "monster functions", you should first try to understand them.
 
SONAR and any other DAW which uses MIDI to communicate i.e. with a Control Surface will of course send MIDI messages to the controller when i.e. Volume sliders or Pan knobs get moved.
 
That's not a monster function, that's how it should be.