Page 1 of 1
Battery 3 mapping issue
Posted: Thu Jul 14, 2011 4:15 pm
by abl385
Does anyone know how I tell Battery 3 to start the key mapping from C2 instead of C1 (every time I load a new kit that is) AND again from C2 instead of C3 for the pads? I am using an AKAI MPK25. I tried modifying the options but I only make it worse.
Re: Battery 3 mapping issue
Posted: Fri Jul 15, 2011 2:06 am
by dentaku
Yeah, I see what you mean. My MPK49 pads start at C3 (when I'm using the Ableton Live MPK preset)and Battery kits usually start at C1.
You could use the Vyzex editor for your MPK and change Pad Bank B, C and/or D to start at C1 instead but that's a bit fiddly and unnecessary.
The easiest way is the simply turn the knob next to the LCD on your MPK to preset #2 "Reason" and this makes the pads start at C1 instead in Pad Bank A, C2 in Pad Bank B and C3 in pad Bank C.
Another way is to put a Pitch MIDI Effect plug-in before Battery and move it to -12, -24 etc.
Of course this only applies to kits that are laid out in a logical way. Some of them just seem to have the mapping in strange orders that I don't understand.
Re: Battery 3 mapping issue
Posted: Sat Jul 16, 2011 2:57 pm
by R7
Inside Battery click file, options... One of the options is keyrange offset which you could change to c2, then every time you load battery the first pad will be on c2 by default, however if you then load one of the battery kits they will load their default midi note possition, which start at c1 still. Another thing you can try if thats still a problem is in the same options menu there is a transpose midi in option, if you set it to -1 as it is in octaves it shud mean when you hit a c2 battery will pick up a c1, and this will still work for kit presets.
Hope that helps...
Re: Battery 3 mapping issue
Posted: Sun Jul 17, 2011 3:38 am
by abl385
Thank you for your replies.
dentaku wrote:Yeah, I see what you mean. My MPK49 pads start at C3 (when I'm using the Ableton Live MPK preset)and Battery kits usually start at C1.
You could use the Vyzex editor for your MPK and change Pad Bank B, C and/or D to start at C1 instead but that's a bit fiddly and unnecessary.
The easiest way is the simply turn the knob next to the LCD on your MPK to preset #2 "Reason" and this makes the pads start at C1 instead in Pad Bank A, C2 in Pad Bank B and C3 in pad Bank C.
Another way is to put a Pitch MIDI Effect plug-in before Battery and move it to -12, -24 etc.
Of course this only applies to kits that are laid out in a logical way. Some of them just seem to have the mapping in strange orders that I don't understand.
Great advice! When I changed to the second preset (Reason), the pads worked great.. they started from C1 indeed! And changing to pad bank B gave me C2 etc. Also the pitch MIDI effect was really clever and worked great as well. HOWEVER, I can't use both at the same time: if I insert the pitch MIDI effect (and change to -12) the pads won't work and we have a problem
One more thing I noticed was that in the second preset (Reason) like I said the pad banks work perfectly fine. On the first preset though (LiveLite) or to be specific on the one I'm using, the pad banks don't seem to work. B, C and D are dead. How can this be fixed?
All of the above really make me wanna try the Vyzex editor, since both of the tricks were possible but not at the same time. So there must be a way through Vyzex to solve these problems at once.. Can you please explain if you know?
R7 wrote:Inside Battery click file, options... One of the options is keyrange offset which you could change to c2, then every time you load battery the first pad will be on c2 by default, however if you then load one of the battery kits they will load their default midi note possition, which start at c1 still. Another thing you can try if thats still a problem is in the same options menu there is a transpose midi in option, if you set it to -1 as it is in octaves it shud mean when you hit a c2 battery will pick up a c1, and this will still work for kit presets.
Hope that helps...
I tried changing the keyrange offset but it does nothing really.. normally this should fix the problem, but sadly it doesn't. Also tried 'transpose MIDI in (octave)' and if I set this to -1 it could help, but then if I click on a cell it will trigger a different one and this totally messes things up
