abacab
I have noticed this "None" feature too ... I wonder if anybody has submitted an official bug report to Cakewalk? 
 
IMHO, discussing bugs on the forum may sometimes bring attention of Cake staff.  But it appears that it must be a very major bug that affects many users to get attention here.  Venting here will not fix anything.
 
For a relatively minor bug, even if it's a major annoyance to a few, the problem report system is still probably the most effective way to improve Sonar for us all.
 
http://www.cakewalk.com/S...Contact/Problem-Report

 
i have, and it most certainly is not minor, as it leads to data loss.

If you enable in the preferences the automated echo for the selected track, then "none" becomes "omni" for the selected track. This is useful, because you can switch your keyboard to a track simply by selecting it.
 
If you disable automated echo, "none" is none and stays none. Then, you can echo single tracks and select whatever input you like, be it an explicit midi channel of a particular midi input, be it midi omni for all inputs, or be it none to silent it.
 
I think this a completely consistent logic. But it depends on the automated echo in the preferences. Turn it off, if you don't want Sonar to have "none" behave like "all" for the selected track.

ralf
If you enable in the preferences the automated echo for the selected track, then "none" becomes "omni" for the selected track. This is useful, because you can switch your keyboard to a track simply by selecting it.
 
If you disable automated echo, "none" is none and stays none. Then, you can echo single tracks and select whatever input you like, be it an explicit midi channel of a particular midi input, be it midi omni for all inputs, or be it none to silent it.
 
I think this a completely consistent logic. But it depends on the automated echo in the preferences. Turn it off, if you don't want Sonar to have "none" behave like "all" for the selected track.

OK, but still, shouldn't only the track selected have the "None" set to "Omni" then?  And even then, it should only listen from the keyboard.  

Every project I work on has synth MIDI out making its way to tracks that shouldn't be getting it.

I'm not using my keyboard often, so I can't say if there may be problems for larger projects, but I never noticed any misrouting for midi input.

When you activate a track for echo or recording, it switches from "none" to "all/omni" (not "omni"), and it won't switch back to "none" if you turn echo or recording off. (But it will not echo without echo on.) In the screenshot in your first post, one track is set to automatic echo (with the A on the echo icon) and three tracks have echo on directly. The track with automatic echo will interpret and show "none" as "omni", the other three tracks will follow whatever is set for midi input.

The screenshot doesn't show the midi input selection for each track, so I can't say which tracks should echo the midi input, but most likely all four tracks will echo and this is correct from the logic as I described it.

ralf
If you enable in the preferences the automated echo for the selected track, then "none" becomes "omni" for the selected track. This is useful, because you can switch your keyboard to a track simply by selecting it.
 
If you disable automated echo, "none" is none and stays none. Then, you can echo single tracks and select whatever input you like, be it an explicit midi channel of a particular midi input, be it midi omni for all inputs, or be it none to silent it.
 
I think this a completely consistent logic. But it depends on the automated echo in the preferences. Turn it off, if you don't want Sonar to have "none" behave like "all" for the selected track.

If I disable echo and not recording... then ANY input settings becomes "none" and stay none. "None" (as none) make any sense if (and only if) whatever you do there will be no input.
 
Sorry to say, but current "completely consistent logic" remind me about very old joke: "To prevent infections, use condom... but more important, avoid sex" 
 

azslow3

ralf
If you enable in the preferences the automated echo for the selected track, then "none" becomes "omni" for the selected track. This is useful, because you can switch your keyboard to a track simply by selecting it.
 
If you disable automated echo, "none" is none and stays none. Then, you can echo single tracks and select whatever input you like, be it an explicit midi channel of a particular midi input, be it midi omni for all inputs, or be it none to silent it.
 
I think this a completely consistent logic. But it depends on the automated echo in the preferences. Turn it off, if you don't want Sonar to have "none" behave like "all" for the selected track.

If I disable echo and not recording... then ANY input settings becomes "none" and stay none. "None" (as none) make any sense if (and only if) whatever you do there will be no input.
 
Sorry to say, but current "completely consistent logic" remind me about very old joke: "To prevent infections, use condom... but more important, avoid sex" 
 

That's not what I said. All I said is that you have two options. Turn automated echo on, then "none" will become "omni" for the selected track, which is pretty useful to quickly change the input for your keyboard by selecting a track. Turn automated echo off, then you have to manually enable and disable echo for each track, which gives you direct control without any surprises. Pretty simple, and it's your choice. But enabling automated echo and then complaining that it doesn't know if you want it to be active or not at the very moment ...

ralf

azslow3

ralf
If you enable in the preferences the automated echo for the selected track, then "none" becomes "omni" for the selected track. This is useful, because you can switch your keyboard to a track simply by selecting it.
 
If you disable automated echo, "none" is none and stays none. Then, you can echo single tracks and select whatever input you like, be it an explicit midi channel of a particular midi input, be it midi omni for all inputs, or be it none to silent it.
 
I think this a completely consistent logic. But it depends on the automated echo in the preferences. Turn it off, if you don't want Sonar to have "none" behave like "all" for the selected track.

If I disable echo and not recording... then ANY input settings becomes "none" and stay none. "None" (as none) make any sense if (and only if) whatever you do there will be no input.
 
Sorry to say, but current "completely consistent logic" remind me about very old joke: "To prevent infections, use condom... but more important, avoid sex" 

That's not what I said. All I said is that you have two options. Turn automated echo on, then "none" will become "omni" for the selected track, which is pretty useful to quickly change the input for your keyboard by selecting a track. Turn automated echo off, then you have to manually enable and disable echo for each track, which gives you direct control without any surprises. Pretty simple, and it's your choice. But enabling automated echo and then complaining that it doesn't know if you want it to be active or not at the very moment ...

As clearly stated in the OP, this thread is not about workarounds we all know. Yes, there is an option to turn Echo off. And when it is off, the input is irrelevant.
But the thread about the meaning of the word "None" which is always "Omni". If the Echo is off, it is still Omni, but since the input is irrelevant it works as "None", the same way as let say "Kawai DP / MIDI Ch 1" is also works as "None".
 
As you have written, automatic Echo (lets not call it "automated", since this word is normally used for Track Automations) is pretty useful. If you have several tracks and you change the focus to play different synth by changing the track in focus (Sonar does have easy mappable to keyboard/MIDI functions for that, but not for switching directly to specific track), at some moment you can temporarily switch to track you do not want to play. Fancy things can happened then, especially when some of Synth has MIDI output enabled. Not only some notes can be audible, arbitrary (!) parameters inside this synth can be invisibly (!) changed in case some other synth sends CC and this synth react on them. Unlike notes, changes in parameters are permanent (!). You can not "undo" them, they are not reverted on transport stop, they can be invisible. You save your project and it is "corrupted", without any way to find why.
 
I repeat, we know workarounds. Adding external "MIDI Loop" which is never used and setting track input to it is the (only?) way to truly set track input to "None". But "completely consistent logic" should respect the meaning of the word "None". I do not think there can be any second opinion on that... 
 
 

Maybe discussion would be less heated, if you would name your problem simply the way it is: There is no option to turn off automatic echo for particular tracks, because "none" as input is interpreted as "omni" in that case.

MarioD

Sanderxpander
That one has been a PITA for ages to me too.

You are not alone!

++++++1

And often when people offer solutions or workarounds, you dismiss them as not being what you want, thus causing those people to feel they've wasted their time - which they have.

 
No matter how the OP responds to any help given, it is never wasted. This is a public forum. Threads are read by tens or hundreds of users. Someone out there is being helped by those comments even if the OP rejects them.