MIDI Issue - Input Selection Being Ignored

Hello Everyone,

This has been happening for as long as I can remember.  Here is the situation:
 
MIDI track with input set to "USB Oxygen 25 - Omni".   I am assuming this means pick up ONLY notes from my Oxygen USB controller I physically press.  

However, I am getting MIDI notes from other tracks that have MIDI notes!  Most likely via MIDI-Out, but still... my input on this particular track is my USB controller!  How are any notes from other tracks coming through?

Thank You,
Adam
 

czyky
Are you talking about during playback and more events are sounding than are in the track? Or do you mean during recording and more note events are getting recorded that you physically press on your controller?

During recording - more notes are coming into my armed track than what I am physically entering into my USB MIDI controller.  It is MIDI notes I have in other tracks (they do have MIDI out enabled, and I need them to be, but I just need this track to ignore all that... but how?)
 
Thank you!

actually when its on MIDI OMNI, it is during playback and recording, but when I choose the MIDI USB Input Controller, then its only during recording, but thats still no good
 

Is it happening on all VSTi's or just one?
 
Also if you strat a new track with just one instrument track, does it still happening?

If you record the erroneous data by choosing Omni out, what does it look like on the event filter?

it looks like it was recorded by Channel 1.  Basically the problem here is even though I have my MIDI Controller set as the input - the track still accepts input from other MIDI out tracks!   Funny thing is, if I switch it to MIDI OMNI (all devices) and then back - it works again...

Seems like this is going on a while...

http://forum.cakewalk.com...622.aspx?high=midi+out

its all right here.... http://forum.cakewalk.com...818.aspx?high=midi+out

yup... kinda disgraceful actually...it's 100% pure Cakewalk issue.

haha!

Hold on guys; that thread is long and covers a lot of ground. The primary issue and several related issues were fixed in X3. There remains one issue that I know of that a MIDI track that has focus while another track is armed to record will show a false "confidence recording" indication as described above, and if looping is enabled, can actually cause playback on the wrong instrument on the second and subsequent iterations of the loop.
 
That may be part of the problem being described here, but some of the other symptoms don't align with that.
 
In any case, in order to troubleshoot something like this and have a chance of other users replicating it, you need to boil the project down to the minimal configuration that demonstrates the issue, and very thoroughly describe all of the routing, port and channel assignments, input echo status, etc. of all MIDI tracks and MIDI Out enabled synths in the project, and the MIDI configuration of the controllers (e.g. does it have a MIDI In, and does its MIDI Out act as a Thru?) and MIDI interfaces.
 
At this point, the description of the problem is way too sketchy to make sense of.
 
 

This only happens if you have "Aways Echo Current MIDI Track" enabled in preferences. This causes the input of new MIDI tracks to default to "Omni" which is the same as AllInputsOmni. If you don't have Always Echo enabled, new track inputs will default to None so you'll be starting from the correct state in the first place.
 
 
 
 

So did Silktone's Toggle-Input-to-None-and-Back workaround solve your problem?
 
I'm finding that even with Always Echo enabled (i.e. starting with Input = Omni on a new track) and then setting the input to <Controller> - Omni or <Controller> - <MatchingChannel>, I only get the false confidence recording clip outline; no notes show in the clip while recording, and nothing is actually recorded or echoed to the synth. I don't have to toggle the Input to prevent actual recording.
 
I don't have multiple MIDI interfaces connected to my DAW at the moment, but I have in the past so there are entries for them in TTSSEQ.INI. Maybe that's all it takes to make the problem go away...?
 
I'll try to look into this more later.