I was hoping to get a little bit more info as to how this mapping is done, I notice you have a mode where different scales can be selected, I assume to be played on the pads?
The mapping was done by assigning clyphx x-controls (in a UserSettings script) to the midi notes I had setup on the Quneo.
Clyphx x-controls access Live's API as a midi remote script, and you can choose what parts of Live you want to control, so you can assign those instructions to your midi controllers. It simply uses midi notes and control changes. So, I had different quneo presets so I could use different midi notes and channels for more x-control functions.
However, since I got M4L with the 9 update I've been porting over my Clyphx functionality so most of the clyphx controls are getting phased out.
There are a lot of advantages to using an M4L patch instead of Clyphx x-controls.
A big one is that I don't really like having to switch quneo presets all the time to switch to different "pages" of functionality (like nativeKontrol modes for the APC or LPC series). Even though I can get the presets to change automatically, I'm picky about the amount of time the quneo takes to switch to another preset (around 1.5 seconds). So with the M4L patch I can just have any midi numbers set on the quneo (I just do 0-63 on the pads, like monome) and then for every different "page" or "mode" I just use a gate and change the instructions. I *was* converting the midi notes to access the Clyphx X-controls but had to set up midi tracks for each separate channel I needed to access in the script (because Live's MIDI spec sucks) but since I've gotten the hang of controlling Live's API I really don't need those X-Controls anymore, so in short it's more of a closed system, not having to go outside of live, rely in midiyokeas much, etc. And the only time I need to change a Quneo preset is when I need to access X/Y pads, so really I only need to have 2 presets for the different pages I have set up (so far)
Alright well, that's probably above your head but it might be good info for others, anyway, I do have a page where I'm accessing CHORDS, not scales, personally I don't like using scales; I need my accidentals:) but they're alright sometimes. I do have a rack of the 8 traditional modal scales, but that's more of a filter; I have midi tracks with the signal path of custom racks going as: CHORDS -> ARP -> MODES, so with Modes last in the chain you can get nice little modal/key change variations. I will share the racks soon, relatively soon. Sooner than Bitwig soon
Now you mentioned Bank Switching process, but in what way, bank switching with user remote script (blue hand)? Or Quneo bank switching where the preset can transpose the midi notes? I haven't had a use for that, and since I have M4L I can do whatever mapping settings I need in there, which is great, because is goes back to not having to rely on using or setting up multiple quneo presets.
That being said, to keep it simple and direct to your question, if you want to customize and not rely on the scripts that are currently availble for quneo, you can go the Clyphx X-control route, or the M4L route. Excuse the redundancy.
The advantages to the Clyphx route is: less cpu/ram, because you don't need M4L. The cons are, you'll need to use midiyoke and maybe midi-ox (I've been using midi-ox, it's great, but again, since using M4L, it's becoming obsolete. The scripting is easy; though if you want more advanced functionality (like having multiple simultaneous actions happening in a sequence) you may have to learn some python (not hard) to create custom user actions. Also, it's free. Another con is, you'll need to set up a number of quneo presets for pretty much every page or mode, or set up different mappings in midi-ox and have those change, which is easy but tedious.
M4L advantages: In the box functionality, No relying on midi-yoke, or midi-ox (as much or at all). Instead of having to set up different quneo presets to have different functional pages you can just switch gates in max and change the instructions to fit the midi notes, instead of needing to dedicate a particultar midi note to a particular instruction (though changing midi notes is easy). Learning curve is alot higher for Max than Python but that's maybe like comparing 4D to 2D.
Other than that, nativeKontrol is said to be having a Quneo script similar to the LPC series, but he's bogged down with Push stuff so that might be awhile.
There's also a Launchpad port without the user modes. I *was* using another script called QuneoLive and modified a few things and used that with my X-Controls, but I don't need Quneo scripts anymore, and things are more streamlined and consolidated.
OH, not to forget a huge thing: PROGRAMMING LEDS. That was the most time consuming process of the programming, and I went a few different routes, some straight up complicated convoluted shit that fortunately I don't need to use anymore. Without Max it's a pain in the ass, because you'll have to do some kind of programming to get LED behavior, and that's just not as optimal in many compared to programming it in Max.
So if you really want to get the most out of quneo, I'd say get M4L.
It's a lot more fun than learning to program in Python anyway.
That being said, I'm a newb with Max but I've gotten far since I got it, so I've pretty much got up to Push functionality just on my own from scratch, and should be past it by next month. It's also getting more advanced and twice as functional compared to an LPC or APC script, but being a newb I know that the coding isn't as optimal as it can be, so I don't want to release anything at least until I get get CPU cut in half. Right now it takes about 8% on a dual-core.
For you, if you really want custom control, you'll have to learn programming on some level, whether it's Python or M4L, and at least know what MIDI is and does.
Otherwise you can wait for others to put out some stuff.
Can't say when I'll be putting something out; maybe instead of one huge patch I'll release them in parts, I dunno, and I take forever just to get out of bed so I wouldn't hold your breath waiting for me. The other things is is half of my controls are specifically tailored to some racks and tracks so the patch wouldn't work out of the box for everyone unless they used the same template as I do (which I wouldn't mind sharing, sans the samples and vsts)
I will put out those Chord and Arp racks, though, they are immensely useful.
I do tend to work faster when I have money in front of my face, though.
I really should get some video up though, just to flex.
For now I think you're stuck with hard-mapping Quneo controls to whatever in Live. Are you familiar with User Remotes scripts so you can use the faders to acess the blue-hand automapping?