MIDI Tracks: Cannot set Input:NONE, Echo:OFF --- WHY?

(was Errant MIDI Msgs With Korg NanoKontrol and S8.5P)

I picked up a Korg NanoKontrol control surface from an MF "stupid deal of the day".  Using some good info I found here, I started configuring it, the strip cotrollers as a Generic Control Surface and the transport controls as ACT. That part went smoothly but for some reason, the pan control on track 1 (the only strip I configured last night) triggers a drum in my EZdrummer instance and stops playback when it hits the extreme on either side (in addition to working the trk1 pan control properly). The one MIDI track doesn't have Omni or the NanoKontrol as input so what else could it be? I took a look at what it generates with MIDIOx and the extremes don't send anything unusual. 

I suppose I could delete my generic and ACT control surface configs for it (maybe they're jacked?) and start again. Any other things I should look for?

you can't.  that's the way it works.  I don't like it, but there it is.

I really do not know what they were thinking.

the only way to really set it to NONE is to disable your MIDI DEVICES INPUTS completely.

brundlefly


Two things:

1. SONAR will only let you set a MIDI track's input to None if you disable Always Echo Current MIDI Track in Global Options.

2. All recent versions of SONAR before X1b (going back at least to S7) had a bug whereby they do not properly distinguish events arriving on the same channel of different ports. This is usually only an issue when recording, and only with overlapping Note events, but you might conceivably be seeing some side-effect of this bug.

Disabling Always Echo Current MIDI Track in Global Options solved the problem. Thanks!

I guess it helps to ask the right question...




I've had just about every version of Cakewalk since Cake for DOS 4 to S8.5P but wasn't aware of these MIDI issues. Guess it was never a problem before I tried to use a control surface.