Hello!
I know there are endless posts on the subjects, but I haven’t found a solution yet…
I’ll try and be as clear as possible.
My setup is: Ableton + APC40mkII + APCmini
CASE 1 : Everything’s fine!
- The first 8 tracks with 8 clips each form a 64-clips grid, covered by the APC mini’s green rectangle
- The following 8 tracks with 5 clips each form a 40-clips grid, covered by the APC 40’s red rectangle
- Result: All is well, no conflict, each button properly triggers the appropriate clip
CASE 2 : What the…?
- Same setup as above…
- …BUT, on some clip slots, I manually assign a button on either controller (because I need to launch a dummy clip, an effect, etc.).
- Result : the assigned buttons will trigger a clip slot on the OTHER CONTROLLER AS WELL!
I’ve had so many midi conflicts with other controllers and the APC40mk2… but with the APC mini, also from Akai, I thought at least they would have thought of that…
Any suggestion? I’ve tried fooling around with MidiPipe, to no avail.
Am getting kind of desperate here…
AKAI APC40+Mini MIDI Conflicts
Re: AKAI APC40+Mini MIDI Conflicts
My advice is to only do mapping on one controller or the other. If you do this, you can make the other controller not mappable by turning it OFF for midi in/out on the lower section of MIDI Preferences (specifically ‘Remote’. But still leave it set up as a Control Surface).
The result will be that one controller is midi mappable and the other is not midi mappable. Since the other is no longer midi mappable, there can’t be conflicts.
The result will be that one controller is midi mappable and the other is not midi mappable. Since the other is no longer midi mappable, there can’t be conflicts.
-
djSquirrelFR
- Posts: 2
- Joined: Wed Oct 10, 2018 1:25 pm
Re: AKAI APC40+Mini MIDI Conflicts
Oooh thanks that sounds interesting...! Not very practical as I'm so used to manual mapping, especially for dummy clips! But I'll see if I can make it work.
Re: AKAI APC40+Mini MIDI Conflicts
Well, you would just have to limit mapping to a single controller instead of doing mapping on both.
Remote basically turns midi mapping on and off for a device. This is handy if a different controller has the same notes/ccs/channels and you don’t want them interfering. It’s also handy if you know a keyboard will always only play music, you can still have a different keyboard or pad controller be mappable while the music keyboard has Remote turned off. You’ll have mapped keys but that keyboard itself will be immune to the mapping and playable.
Remote basically turns midi mapping on and off for a device. This is handy if a different controller has the same notes/ccs/channels and you don’t want them interfering. It’s also handy if you know a keyboard will always only play music, you can still have a different keyboard or pad controller be mappable while the music keyboard has Remote turned off. You’ll have mapped keys but that keyboard itself will be immune to the mapping and playable.