Can MIDI mapping differentiate between controllers?

[Muzik 4 Machines]

so it seems another undocumented "feature" (like limiting people to 1000 scenes) again messed my live act

i have 1 midi in on my soundcard i use for track input AND remote
i also use my apc in remote to manually map sme useless buttons to usefull parameters(namely clip stop buttons to drum rack mutes)
they send notes (E2 IIRC on channel 1 to 9)
everything is fine
then i play my keyboard on channel 2 (to talk to my synth on midi channel 2) and eveytime i hit e2, it mutes/unmutes the track

i thought the MIDI ports were independant and some control on port 1 channel 1 would NOT interfere with channel 1 on port 2, but it seems it does, that greatly limits the remote assignement you can make as there is only 16 midi channels for ALL the interfaces (i actually use the bcf, kp3, apc, my traveler as independant midi ports but it all screws up that channel 1 of the bcf will be the same as channel 1 on the apc or midi input and i already use 12 mdi channels just to send notes to my synths, so im left with only 4 channels to remote control (and the APC is hardwired to 1-9)

[Forge.]

you can assign track input to only receive from the device you choose and MIDI channel you want in the i/o settings for each track - change it from "all ins" to the keyboard name if it is USB and disable remote for it, otherwise just make sure none of the remote mappings use channel 2 - if the Keyboard has channel 2 all to itself then you still have 1920 notes to choose from (15 x 128)

if the controller has it's own way of changing the outputted notes/ccs then you could just choose notes that don't conflict on the device, otherwise I think you could do that in the user remote scripting (haven't tried that kind of thing in a long time) - otherwise m4L or there are 3rd party ways of changing the notes like control aid/MIDI Ox etc...

things like the APC/launchpad/VCM600 etc will be independent when working with the default settings (i.e. just "control surface") but not 'remote', but as soon as you override them then yes you are limited to note/channel or CC/channel - but that is actually a hell of a lot of controls still - 16 x 128 notes and 16 x 128 CC numbers

[Muzik 4 Machines]

its a lot of notes, but notes are not cc, so say the APC eats 9 channels, there is only 7 remaining for every other controlers, and with remote on, it can interfere with playback on external instrument
(i discovered this "bug" cause my tribe was triggering scenes, mutes, solo and record from a bassline on channel 3)

anyway i think the software should differentiate input+channel on midi remote mappings so some non configurable controllers like the APC's wont try to overrun each other

anyway another problem i found a workaround but i think is honnestly very limiting

[Forge.]

its a lot of notes, but notes are not cc, so say the APC eats 9 channels, there is only 7 remaining for every other controlers, and with remote on, it can interfere with playback on external instrument
(i discovered this "bug" cause my tribe was triggering scenes, mutes, solo and record from a bassline on channel 3)

anyway i think the software should differentiate input+channel on midi remote mappings so some non configurable controllers like the APC's wont try to overrun each other

anyway another problem i found a workaround but i think is honnestly very limiting

I guess the point I was making was more to find a way of using different notes instead of channels.

Although in this case I think it might be easier to just leave the APC be and change the other controllers so they don't send the same notes on those channels, as they are probably more configurable as they weren't designed specifically for Ableton

[Muzik 4 Machines]

but IMOHO, CC are more important than notes, notes are ok to trigger clips, but to adjust delay, not so good lol

but again, i know i can't change it, so i found a way to alter the MIDI routing with the midi timepiece so i can still use my ribbon controller on the tribe without muting the track

[Warrior Bob]

Live combines the input of all "Remote"-enabled MIDI controllers for the purposes of MIDI mapping. If you map E2 on channel 4 to something on one controller, then channel 4 / E2 from all controllers will trigger the mapped object, so long as Remote is enabled for those controllers.

I can't speak for Ableton as to why it was designed this way. Personally, I think it would have been better if MIDI mapping made a distinction between controllers. I use several controllers and run into this problem frequently.