I know this has been commented on before.

Midi Track: none should mean none, not any/all inputs.

There is a selection on the menu for omni.

For an audio track none does not mean all audio inputs.

This is inconsistant.

None should be none, or remove the option.

J

Turn off this option:

Options > Global > General tab > Always Echo Current MIDI Track


...then you'll have what you want.

Thank you for your response. I did want to change this setting.

However, this does not address the NONE equals ALL annoyance.

There is already an OMNI choice. Must we have two? And the second selction is really the opposite of what the word means.

This has bugged me and others for years.

This makes little sense. Whatever the rational.

I could understand it if it is connected to the "Allow midi recording without an armed track." But, alas, it is not.

Never in my education or experience has NONE meant ALL. (Except, sorta, when my grandkids say, "Yes means no,...")

J

None = OMNI for the active MIDI track when that setting is on. When it's OFF then None = None

That's how the echo setting is implemented. Personally, I LIKE the visual indication that the current track is receiving input from ALL MIDI sources. And on the flip-side: if you have trouble figuring out which MIDI track is active [which is NOT necessarily the same as the currently SELECTED (highlighted) track(s)], then the OMNI indicator is a quick way to figure it out.

Thank you for the info.

I had changed the setting and tested. But it did not change. And thus I replyed with continued ignorance.

I opened a new project and all was as you indicated.

This is good.

Still seems a bit convoluted to be connected to alway echoi the current track.

In this project I need to know these tracks have NO input, since I am using some local midi pipes to send data from these tracks to record automation on other tracks and buses.

Thank you again for your wise and clear understanding.

J

This topic is a bit confusing. From time to time the visual cues don't exactly match up with the current settings or input states. I've not yet found a pattern. But a restart of SONAR normally clears things up.

Also, be aware that strange things can happen if you assign a hardware input to a track....then re-open the project on a system where that hardware input is not available. This happened to me on my DAW a while back when I was using a USB MIDI interface & external MIDI sound module. I created some projects, then upgraded my equipment and got rid of the MIDI interface & hardware. When I re-opened the projects later to work on them (replace the hardware patches with soft-synths, etc.), the inputs were all haywire; and the tracks didn't seem to retain any changes to the inputs. I figured out a way to fix it.....got it documented somewhere. But it was quite confusing.

That is the only downside to SONAR's incredible routing power. It takes time to understand it -- and even when you do it might throw you a curveball every once in a while.

"the inputs were all haywire"

Haywire is something most of us do not use everyday. So when it heads its ugly rear it sure does require too much time to do something with it.

J

deja vu: why doesn't 'none' equal 'zero'?

while we're at it, let's get a midi out setting of none as well.

Maybe you guys should know that this anomaly is not experienced universally.

With midi input set to none on any MIDI track, that track does not play, does not echo, and will not record any events if the track is armed for record.

I've not seen this behavior in Sonar 6 or Sonar 7.

Cakewalk needs to work on simplifying their software. It's unnecessarily complicating and confusing.
I can only imagine how many new users and beginners lost interest in SONAR because of all the confusing and annoying things like... None = Omni
Too much of the weirdness and 'dead weight' stuck on through the software's history.