Did that of course. Did not find any explanation on this topic.
Yes, still diggin. Could be the Ableton script of how they address the macros. The knobs just work fine.
Hi Klaus_Uebergang
I use Ableton live, I’m trying to understand more about your problem.
You want to map a fader of the Minilab as a Macro for a lot of synths but without using the Macro mapping on Ableton?
1 Like
hey @VFertorandez , I would like to map the macros to the faders of the minilab3 without using the global midi mapping function of Ableton as if you are using the “blue” global midi mapping it is hard-wired again to this specific synth you were midi mapping it to. I can address the knobs in macro mode but not the faders. I hope it s well explained…
Ok I Understand, this week I will have a Minilab 3 ,then I think I can try to see if there’s a problem or if the Minilab can’t do it and send a Request.
But now I understand more clearly what you want 
2 Likes
Would be great to have a solution for that as I would love to use the faders on the fly. As otherwise you basically only have 8 knobs to macro design. I could also be an Ableton script problem. But it should be solvable hopefully
…
1 Like
Hi
have you tried using a midi monitor to check and remap the controls ?
on some occasions I had to manually configure the fades and knobs and save a preset with that to reload them so that ableton would not overwrite them.
and finally what I can think of is to create a custom midi mapping script to see if it might work well for you.
2 Likes
Sounds interesting. I have to dig closer into this. Thanks for the idea.
2 Likes
I don’t understand; what script are you using; ableton; analog or user?
-in ableton the script uses the 8 pots to control vsts/effects; the faders are for volume and pan; you can’t change it
-in custom you can map any way you like (see below)
-in analog lab mode you can use separate instruments and map them as you want, including macro; for each specific synth. create a midi mapping for each instruments including the macros (little gear in the right; midi); save your mapping and your set. you can also do the same in custom mode; so each instrument will have the mapping of your choosing (you need then to turn on/off monitor if you have several). Note that it doesn’t work with the analog lab plugin (which is a bit stupid imo) but only independant arturia plugins.
Lastly; if you want to have a remote ableton script but are note happy with the one provided you can create a custom one editing a text file (it’s explained in the link; create a folder with the name of your script; put the modified text file in it, it’s quite easy).
https://help.ableton.com/hc/en-us/articles/206240184-Creating-your-own-Control-Surface-script
This way you could map the 12 pots and faders to device mode; maybe 4 pads even. You could also add a function to flip through pages of your macros.
you won’t have the advanced function of the ableton script (name displayed on the screen; main encoder function; launching clips) though (or if there’s a way I don’t know it)
hope it helps
edit: I understand know that you’re talking about ableton devices macros and not arturia plugins. so yeah see about the custom script option if you’re not using arturia plugins.
edit again: if by any chance you know python you can try modifying the original script (inside the ableton application on a mac). but that’s probably quite the task.
Thanks for your thoughts on this. I thought it would be much easier just to address all the controls of the minilab on the fly with the macros. did not come to my mind this obstacle. In the end, it’s a controller a lot of people are using with Ableton and it should be easy to customise your workflow. Maybe with an Update of firmware, this problem will be solved… But I will also dig into the control surface topic.
The knobs on Keylab mk2 I have never been able to map them to the macros in Ableton Live 11. Even if I use the Midi Control Center or use Ableton mapping program it doesn’t work. The Mk2 hasn’t had an update in a long time. I had to purchase a Novation Launch Control XL it seems more reliable than the knob mapping on KeyLab mk2.
I have the minilab but I guess it’s the same problem. As I just wanted a nifty simple mini controller for working on the road with a relatively nice keyboard and build quality, I have decided for the minilab but seems like akai would have been the better solution… let’s keep on diggin.
1 Like
It’s basically a design choice from arturia; you can’t have a full ableton control in a format like this. The bigger essential mk3 allows you to have 16 macros but still no way to flip through banks.
there’s never a perfect solution for all of this. I really doubt they will change the way it works but maybe someone could come with a custom template that helps.
Alternatively if the plugin allows it’s less trouble to just midi learn directly into the vst.
1 Like
you can do that pretty easily with a custom remote script; see my link above. I have a generic 24 pots controller here and was able to make it a remote in about ten minutes, it works with anything.
you just edit the txt file with the midi CC of your controller (device control 1-16); create a folder with the name of your choosing; put the txt file inside; then launch live; select your script in the list with your keyboard as in and out and you’re done. You’ll also have to deactivate the default script. you could also assigns buttons to switch through banks.
1 Like
That sounds complicated haha. 
Thanks for the idea though. I would love if even it did just 1st 16 macros like on the new keylab mk3. At least the knobs are useful for quick parameters in live gigs…instead of having another seperate controller to hook up.
@grrrzzzt I will give it a try… Let’s see. I know it s a design choice but would have been more useful to just have a user preset where you can easily address all the control knobs and faders like with the push or the Akai products…
How does it work with the minilab 2 as it has all knobs? Are they easy to address? Thanks for your tips and explanation! best!
follow the instructions here:
https://help.ableton.com/hc/en-us/articles/206240184-Creating-your-own-Control-Surface-script
find where you have:
Encoder1: -1
Encoder2: -1
Encoder3: -1
Encoder4: -1
…(up until encoder16)
and replace the -1 with the CC number of the corresponding encoder (I suggest a custom mapping for example using CC 12 to 27. anything but 1 would be alright since 1 is modwheel). assign some buttons to “nextbank…” “previousbank…” so you can scroll through them if you want. then you follow the instructions and you should be up and running. I don’t know how familiar you are with midi but it looks complicated but I was surprised how straightforward this is. Only thing is you can’t access more advanced features like clip launching / parameter name feedback with this but for what you want to do that’s enough.
some services like remotify.io gives you an interface to do all that included the advanced features but that’s a paying service; not super useful in my opinion in this case.
1 Like
I had the same issue with my Keylab MKii in Ableton - seems like mapping is always global and not specific to the channel you’ve selected/record enabled. It’s simple enough to map to macros but as you’ve mentioned it’s always hardwired to be global. I got around it with a simple max4live device that enables you to control 8 macros. If you have M4L and Ableton 11 let me know if you want the link and I’ll have a look for the download. Works a treat for me and completely stable.
2 Likes
Hi @Danturia yes, I would love to check this as I haven’t found a workaround, yet. By any chance can I extend it to the faders as well? So I would have the full amount of controllers of the Minilab 3 assignable? Best and thanks !