All Midi channels responding to midi keyboard

[Billy86]

I have multiple virtual instruments, each on their own track.  They are all responding to midi input from my Nektar keyboard. when I select ‘None’ on these tracks for Input, they remain on Omni, so obviously they can still ‘hear’ the midi input. Can’t figure out why None for input doesn’t mean none, it stays on Omni (ie. All).  In preferences, I also have the setting that means listen to the track that’s in focus. 
 

How do I break the signal flow of Midi to tracks I don’t want responding? The track I want to respond is in focus, and the monitor button is active, and the track is responding as expected. But so are all the other tracks. Thanks. 

[user 905133]

1 hour ago, Billy86 said:

I have multiple virtual instruments, each on their own track.  They are all responding to midi input from my Nektar keyboard. when I select ‘None’ on these tracks for Input, they remain on Omni, so obviously they can still ‘hear’ the midi input. Can’t figure out why None for input doesn’t mean none, it stays on Omni (ie. All).  In preferences, I also have the setting that means listen to the track that’s in focus. 
 

How do I break the signal flow of Midi to tracks I don’t want responding? The track I want to respond is in focus, and the monitor button is active, and the track is responding as expected. But so are all the other tracks. Thanks. 

Assign the output track widgets to single channels if you want a track to go to a single midi channel or monotimbral instrument (assuming the instrument itself is not set to omni mode). If you don't want a track to play you can mute it or set volume (CC7) or sometimes expression (CC11) to 0 if the instrument respects those CCs.

 

 

 

[Max Arwood]

Change the midi channels. That might help. 
Solo and mute buttons might help?

Be sure midi send is not on for the soft synths. 

Edited Sunday at 02:40 AM by Max Arwood

[Billy86]

Thanks for the replies. I’ll look at this when I’m back at my computer. Still, would be nice if you set a virtual instrument track’s input to None, it would be none and we could move on. 

[David Baay]

2 hours ago, Billy86 said:

Still, would be nice if you set a virtual instrument track’s input to None, it would be none and we could move on. 

You need to disable Always Echo Current MIDI Track iin preferences. It doesn't make sense to Echo 'nothing' so the input is automatically changed to Omni whe 'Always Echo' is enabled so that you'll get a response to whatever controller you're playing.

But you'll still want to set a forced MIDI Output channel on each track to ensure that each instrument in a multitimbral synth responds only to its respective track. If you create the tracks initially as Instument Track Per Output, that will happen automatically.

 

Edited Sunday at 06:14 PM by David Baay

[pwal lɒwq]

4 hours ago, Billy86 said:

Thanks for the replies. I’ll look at this when I’m back at my computer. Still, would be nice if you set a virtual instrument track’s input to None, it would be none and we could move on. 

This is an ancient issue, I guess there'd be a lot of old code needed changing to fix this because it's still a thing

None means none, except when it means all

[msmcleod]

"None" becomes "Omni" when "Always Echo Current MIDI Track" is checked.   It's effectively a workflow short-cut to mean ignore all MIDI input on all tracks except this one I'm working on.

The MIDI input filter on each MIDI / Instrument track allows you to select specific channels on each device listed.  You can even save that choice as a preset if it contains only hardware MIDI inputs.

If you change None to something else, then this "None" to "Omni" behaviour goes away and it'll only receive MIDI input from the devices/channels you've chosen.

Just change the MIDI input to your MIDI keyboard device and it'll work.

It's up to you whether you want "Always Echo Current MIDI Track" on or not.  Personally, I find it useful as it saves me having to manually enable/disable input echo.

Also consider disabling MIDI output on VSTi synths.  Unless they're actually generating MIDI themselves, there's normally no need for it to be enabled as their input can be picked up by other synths when switched on.

[David Baay]

I agree it's generally best to set Inputs to your primary controller port. If you don't want anything echoed on the track even when 'Always Echo' is enabled, you can either set an Input channel that deosn't match your controller's transmit channel or set the port to the Cakewalk's Virtual Controller.

[Billy86]

Thanks everyone! Lots of options.