I've mapped the y-axis of my padKontrol to the pitch value of the grain delay effect in Ableton Live. Right now it increments the pitch value in whole numbers (1, 2, 3, etc.). Is there a way to make it more granular, such that it could increment the value half a point at a time (.5, 1, 1.5, etc.)?
I tried mapping the y-axis to other values in grain delay (e.g. delay time); still whole numbers only. I tried using the x-axis instead; same problem. I also tried making the Min and Max values of the mapping in Live 0 and 1, respectively. That just made it so that the touching anywhere on the top half of the x-y pad incremented the value by 1; still no decimal values.
For what it's worth, I have used other devices to control this value to a decimal degree of precision with no trouble, and it's also worth noting that the PK's x-y pad is quite sensitive enough to register the input. It's like this is a preset somewhere that someone thought would be very convenient, and I just have to figure out how to turn it off. As usual, eh?
I'm working on a MacBook Pro with Live 8.1 and I've got the latest PK firmware. Any and all sage wisdom will be appreciated.
Can the padKontrol x-y pad send decimal values to Live?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
This is definitely a Live thing. You need to set the parameter range properly.
The PK's controllers will transmit normal full range MIDI messages (bottom of the pad is 0, top of the pad is 127, on the X axis), and this is the way most if not all MIDI controllers work. MIDI only sends whole numbers between 0 and 127.
It is up to the receiving software (Live in this case) to translate that 0-127 range into something else which is useful or relevant to the parameter it is mapped to.
The PK's controllers will transmit normal full range MIDI messages (bottom of the pad is 0, top of the pad is 127, on the X axis), and this is the way most if not all MIDI controllers work. MIDI only sends whole numbers between 0 and 127.
It is up to the receiving software (Live in this case) to translate that 0-127 range into something else which is useful or relevant to the parameter it is mapped to.
Current Gear: Kronos 61, RADIAS-R, Volca Bass, ESX-1, microKorg, MS2000B, R3, Kaossilator Pro +, MiniKP, AX3000B, nanoKontrol, nanoPad MK II,
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
Other Mfgrs: Moog Sub37, Roland Boutique JX03, Novation MiniNova, Akai APC40, MOTU MIDI TimePiece 2, ART Pro VLA, Focusrite Saffire Pro 40.
Past Gear: Korg Karma, TR61, Poly800, EA-1, ER-1, ES-1, Kawai K1, Novation ReMote37SL, Boss GT-6B
Software: NI Komplete 10 Ultimate, Arturia V Collection, Ableton Live 9. Apple OSX El Capitan on 15" MacBook Pro
I would normally agree with you, but I've used a Wii remote through OSCulator to send CCs and not gotten anything like this behavior. Also, if by parameter range you mean the min and max of the MIDI mapping in Live, no amount of tinkering helps. I'll post the problem to a Live forum, but I'll still be checking back here. Anybody who's got an answer feel free to shout out.
Edit: I also tried changing the mapping mode through all the various options (absolute, absolute (14-bit), various flavors of relative), and all of them continued to provide only whole values.
Edit: I also tried changing the mapping mode through all the various options (absolute, absolute (14-bit), various flavors of relative), and all of them continued to provide only whole values.