Hello there!
anyone can help me figure out how to go around the elektron auto channel to get these mutes working?
I have a Digitone2 which has 16 tracks and Im mapping for example its mutes to a midi controller.
I use a midi filter pipe to filter all but a group midi channel say 4. then I have a CC Range filter and set it to 1-16, then a transform pipe that essentially remaps the mute cc94 to one of those 1-16 ccs and maps that to midi ch 1-16 which works with midi 4 - essentially grouping the mute 94 to cc 1-16 which is shared by one midi channel in this case 4. this is brilliant because I have other devices say a digitakt and octatrack etc… so that is how I get around all these midi channels when Im trying to map them to midi controllers…
my issue here is that everything works great except for the track that shares the auto channel in my DIgitone’s case its track 15. now what ever track is selected in my digitine will get the command sent by the controller. say I have track 10 selected, when I press pad 15 it will mute track 10 - because my auto channel is hijacking the responsibility…
can any of you advanced midihub users give me any tips or ideas how to bypass the auto channel?
If you set the auto channel on the Digitakt to X, then any data coming in via MIDI channel X will play on the currently selected Digitakt track. Auto channel doesn’t affect MIDI output from the Digitakt itself.
Hopefully an Elektron user with an understanding of the subtleties of Auto Channel can chime in.
In the meantime, it sounds like you might need some parallel pipelines going on.
Please upload the relevant parts of the .mhp so others can see.
does MH need to know the “currently selected Digitakt track”?
btw, it seems many users avoid having the Auto Channel the same as a set device channel. Is that unavoidable in your case?
that sounds right, in regards to elektron auto channel. you mainly use it to play what ever track you have selected on your device in a midi controller. set the controller to that auto channel and you play what ever track you have on your elektron device. its great.
In my case Im trying to map all its 16 tracks to my launchpad pro (I do for all my elektron devices).
Besides the fact it can be overkill to have 16 tracks per device I wanted to have the flexibility if I wanted to.
the easy fix is to sacrifice the one auto channel track for that device, only use 15 tracks per device. but I have a midi hub, and I thought I can somehow get around this issue. I dont know what you mean about parallel pipes. Id like to understand more… but the main concept of what I do with these elektron boxes is that I group each device to one midi channel. in my example the Digitone is Midi ch 4. and the mute CC94 is remapped to 1-16 to work with midi 4. in my launchpad I just set each pad to cc1-16 and its midi ch 4. tehy all work as expected except the one for track 15 because that is what my auto ch is set to on my digitone.
so that one as expected will mute what ever track is selected… I tried several things like make a new midi group for that one track 15 say midi group 5 with CC94 remapped to its isolated CC, and then the launch pad for that track set to that cc and ch 5… I though that would work but its still doing the same thing because in my device, track 15 is set to midi ch 15 and the auto is as well… maybe what I want to do is just not possible?
By the way this is just the mute example but was planning to sort this and apply the fix to other parameters if I find a fix. If there isnt a fix I may just have to use 15 tracks instead of 16… lol!
Im adding a thin version of my patch. thanks so much for the help! MIDIHUB_DIGITONE PIPES.mhp (668 Bytes)
If you want to be able to control all 16 tracks’ mute via MIDI - then there is no getting around it: You have to disable the auto channel mapping on the Elektron box. This is just how Elektron boxes work, and no amount of MidiHub magic can get around it.