Hi,
i use one Arturia Keylab and one Arturia Keylab Essential.
I use Ableton Live with many scenes. Every Scene is one Song. I use it for live performance on stage.
In a scene i use instrument rack with several different software sounds, synthesizers, strings, piano etc.
All works fine - only one question.
In the instrument rack i enable and disable a sound for example piano with the pad on my arturia - that works fine.
But i want to enable and disable it with the KEylab and with the key lab essential. If i use the Midi Learn funcition i overwrite it with the key lab or i overwrite it again with the key lab essential. I think, i cannot make two controller keyboards on one step in Ableton. I need to Midi command on one thing in Ableton. You know what i mean?
Any idea?
Midi Learn function / Midi control
-
ellicottvilleny
- Posts: 22
- Joined: Sat Jan 16, 2021 5:23 am
Re: Midi Learn function / Midi control
This isn't exactly what you asked, but here's my thoughts:
* It sounds to me like you wish midi learn functions could let you set up your controller to do more than one mode or function and overwrite a midi mapping with another one. This is not something you will be able to do seamlessly during a live performance.
* Instead, you should probably look for a more sensible workflow. Let me explain how I have live keys set up, both in Ableton Live, and in other environments, such as Mainstage.
* Ableton LIve is the centerpiece of MANY live keys rigs, and they all may be different.
* I use the clip launcher and the scenes, and the channels (tracks) to launch clips, and to change which instrument patch I am playing. I find a Novation Launchpad MK1 that I bought used for $50, to be 100x more useful for this than any ad-hoc use of a midi controller mapped via midi learn functionality.
*I would think that the correct thing to do for you is to (a) determine what you want to do, (b) determine what combination of devices and SCRIPTS would do that, rather than trying to build a whole workable set of rig controls from a single midi-mapped controller.
* Sure, midi map gets used here and there, for example, I might map my organ's leslie rotary on/off to a pad on one of my little Korg or Arturia controller's drum pads, or a vibrato knob to one knob on a controller, but I set it and forget it. Remember to TEST that every little midi map you made works, or you won't have access to it when you're live.
* The basic useful lives key rig with ableton that I would set up first, is one pad to go to next channel, one pad to go to previous so you can page through your entire session's channels (what other DAWs call tracks, each one having an instrument loaded, with a patch selected) one by one. Channel 1 might be my piano, Channel 2, a clav, Channel 3, a rhodes, Channel 4, Hammond B3, Channel 5, Big Stringy Pad. Etc. If that's ALL you wanted to do with a live keys rig, frankly, Mainstage is your boi, not Ableton, but Ableton provides SO MUCH that Mainstage can't do, that I suggest you use the channels to be your sounds. You might even want to map buttons to let you have a single midi signal (a note or CC) switch to each of your 16 most commonly used sounds. But you WILL EXHAUST what a midi learn based workflow can do, quickly.
* A level up from the basic rig (one sound per channel) is to go with an Instrument Rack based approach like this worship keys guy:
https://www.youtube.com/watch?v=q1jaMfsEpaw
* It sounds to me like you wish midi learn functions could let you set up your controller to do more than one mode or function and overwrite a midi mapping with another one. This is not something you will be able to do seamlessly during a live performance.
* Instead, you should probably look for a more sensible workflow. Let me explain how I have live keys set up, both in Ableton Live, and in other environments, such as Mainstage.
* Ableton LIve is the centerpiece of MANY live keys rigs, and they all may be different.
* I use the clip launcher and the scenes, and the channels (tracks) to launch clips, and to change which instrument patch I am playing. I find a Novation Launchpad MK1 that I bought used for $50, to be 100x more useful for this than any ad-hoc use of a midi controller mapped via midi learn functionality.
*I would think that the correct thing to do for you is to (a) determine what you want to do, (b) determine what combination of devices and SCRIPTS would do that, rather than trying to build a whole workable set of rig controls from a single midi-mapped controller.
* Sure, midi map gets used here and there, for example, I might map my organ's leslie rotary on/off to a pad on one of my little Korg or Arturia controller's drum pads, or a vibrato knob to one knob on a controller, but I set it and forget it. Remember to TEST that every little midi map you made works, or you won't have access to it when you're live.
* The basic useful lives key rig with ableton that I would set up first, is one pad to go to next channel, one pad to go to previous so you can page through your entire session's channels (what other DAWs call tracks, each one having an instrument loaded, with a patch selected) one by one. Channel 1 might be my piano, Channel 2, a clav, Channel 3, a rhodes, Channel 4, Hammond B3, Channel 5, Big Stringy Pad. Etc. If that's ALL you wanted to do with a live keys rig, frankly, Mainstage is your boi, not Ableton, but Ableton provides SO MUCH that Mainstage can't do, that I suggest you use the channels to be your sounds. You might even want to map buttons to let you have a single midi signal (a note or CC) switch to each of your 16 most commonly used sounds. But you WILL EXHAUST what a midi learn based workflow can do, quickly.
* A level up from the basic rig (one sound per channel) is to go with an Instrument Rack based approach like this worship keys guy:
https://www.youtube.com/watch?v=q1jaMfsEpaw