Hi Drumbox,
You triggered my curiosity and as I'm preparing next beta as we speak, I figured I could drag this in as last minute enhancement.
..which last minute change seemed weird to me as:
All adaptable variables can potentially be set by the webgui and buttons (though buttons can't support mapping obviously).
And indeed, both button menu and webgui have this option. In the webgui you'll find it in the LCDmenu as mimicked button function and readme screen as a normal dropdown.
It's hard to find as I figured it to be a seldom used function.
Which appears it's true, as it doesn't work anymore
and nobody seems to have noticed 
No matter, it was a silly typo and now fixed. Now the options for you:
You triggered my curiosity and as I'm preparing next beta as we speak, I figured I could drag this in as last minute enhancement.
..which last minute change seemed weird to me as:
All adaptable variables can potentially be set by the webgui and buttons (though buttons can't support mapping obviously).
And indeed, both button menu and webgui have this option. In the webgui you'll find it in the LCDmenu as mimicked button function and readme screen as a normal dropdown.
It's hard to find as I figured it to be a seldom used function.
Which appears it's true, as it doesn't work anymore
and nobody seems to have noticed No matter, it was a silly typo and now fixed. Now the options for you:
- In modules/UI.pi, on lines 465,466 change gv.MIDICHANNEL into gv.MIDI_CHANNEL.
For getting the dropdown on a better place in the GUI, please refer to "more info->tweaking the webgui" in the docs and the examples on the readme screen of the webgui.
- Wait 4-8 weeks for next release. Bug fixed and dropdown on a less obscure place in the webGUI.
- Try the drumchannel option
- Investigate why the multitimbral option doesn't always work.
Next release will show the connected devices in the webgui, which may be a help.
I might be of help investigating, but for that please register and use private messages - see rules...