You are right, ‘map input’ makes little sense.
I was thinking of ‘map input’ as a special input where only already mapped triggers where present, but in hindsight that would defeat most purpose of map pipelines, because you could only change the values of the messages (eg change a CC value or ‘note on’ velocity) but not the message type itself (eg remap a cc, a note message, channel, etc)
What’s really needed is just map output. It’s more straightforward and more effective.
Btw that would be awesome! Two use cases:
- Currently, I am using a controller which I find excellent (Studiologic Mixface, no involvement with them) but it’s a little too dumb in some areas: it can’t do inverted switches like Beatstep (whch as a controller is inferior in any other area). So I am adding a filter pipe with mapped bypass to each pipeline, which works as a NOT operator. Being able to do the NOT operation just once in a map pipeline would be great.
- I am using a fader for remapping channels (so that I can use my Blofeld keyboard as a master - changing channels on that is cumbersome). Since Mixface has an LCD which shows the transmitted value, at first I configured the fader to only send 1 to 16 (so that I could read the channel on its screen). But mapping a channel on midihub expects 0-127 and divides that by 8; I then had to revert back the fader to 0-127, but now I have lost the ability to read the correct channel on its screen. A map pipeline would let me send 1-16 values (and read those on the screen) and translate that into 0-127 for midihub channel mapping. Hope the way I explained it makes sense.
If this is going to happen I’m going to buy a second midihub just for the fun of programming it