oh just another one for ya:



you would expect this "None" pictured here to mean that this MIDI track will accept NO input right?  

WRONG.

it actually accepts ALL input.  It right currently playing the MIDI-out data from my bass track into my Drums!!!!   
 
In order for me to get it to NOT hear MIDI notes from other tracks, I need to manually select my MIDI controller every time.   This is just totally ridiculous.

I will be recommended to install LoopBe which makes it so that my MIDI controller will always be selected.
 

oh and the best part of this, is that I put some MIDI volume automation on one of my tracks, and it is effecting the volume (CC 7 data) on my other tracks, because of this bug!!!

Its seriously time to leave Cakewalk.  They have had these issues for years and refuse to fix.

Disable 'Always Echo Current MIDI Track' in preferences. SONAR cant 'always echo' nothing so it enables all inputs, not knowing which one you intend. This is working as intended, just not the way you would prefer.
 
Good luck finding another DAW that doesn't just have a different set of 'unpreferred' behaviors and limitations.

brundlefly
 
Good luck finding another DAW that doesn't just have a different set of 'unpreferred' behaviors and limitations.

Amen to this.

brundlefly
Disable 'Always Echo Current MIDI Track' in preferences. SONAR cant 'always echo' nothing so it enables all inputs, not knowing which one you intend. This is working as intended, just not the way you would prefer.

If you think that was an intentions... What is the difference between "None (Omni)" and "All inputs/All channels"?
 
While I also think that Silver is quite offensive in his recent posts, but I must admit that I would also like 15+ years old Sonar MIDI engine is replaced with something more up to date or at least 15+ years old bugs are fixed (or at least those 'features' which no-one can refuse to call bugs)

brundlefly
Disable 'Always Echo Current MIDI Track' in preferences. SONAR cant 'always echo' nothing so it enables all inputs, not knowing which one you intend. This is working as intended, just not the way you would prefer.
 
Good luck finding another DAW that doesn't just have a different set of 'unpreferred' behaviors and limitations.

this is not the problem.  its not even the "current" midi track.  its all over the place.

I wouldn't say I am offensive.   I am simply stating how I feel.  Offensive would mean I personally offended someone.  I am simply being harsh on a product.  Is the software feeling hurt?
 

In addition to a real 'None' for input, I have been wanting a real 'None' for output for years.  It would be great to be able to 'park' clips in a track with its output set to 'None'
 
But ... it is what it is

BobF
In addition to a real 'None' for input, I have been wanting a real 'None' for output for years.  It would be great to be able to 'park' clips in a track with its output set to 'None'
 
But ... it is what it is

they don't care about fixing MIDI issues.  It is obvious.