Hello, I’ve been trying to use Global MIDI to map one of the pads on my midi keyboard to the tap tempo button but it simply won’t work and I can’t figure out why.
I changed the setting of the respective pad to a midi CC (channel 1, CC 20). Then I made sure this works by using the global midi monitor of GP.
Then I went to the Global MIDI window, chose the correct line in the menu and selected the correct midi signal by MIDI learn.
Then I closed all the options windows and repeatedly pressed the pad on the controller. The MIDI indicator in the GP window will indicate incomind MIDI data but the BPM value will stay the same and there’s no indication that the MIDI signals do anything at all.
However I just noticed that it does seem to work when I use notes instead of CCs. This is a bit inconvenient though since it will likely produce interference with actual midi notes sent to my virtual instruments at some point. As I understand midi my interpretation does correspond to the orginal specifications (midi notes for musical information, CCs for controlling other attributes). Is this a bug in GP or is there any meaning to this?
Since your screenshot shows falling values for CC#20, it looks somehow like it’d be a configuration error…
Make sure you configure your pad according to the manual:
You never told us which keyboard you exactly use… so i just guessed it was the mk2 - maybe it’s the mk1 and this model behaves diffrent… i don’t know.
Make sure, the pad is set as “Gate” and the “ON” value is fixed as 127 while the “OFF” value is 0.
It’s the Keylab 49 Mk1 actually. Yes, it’s configured as sending continuous values. Maybe that’s the problem. However my expectation was that every value over 127/2 would register as “active”.
@schamass Not a strictly GP-related question but how do I choose the correct setting for the pad? In the MIDI control center I can choose the type of midi signal, the channel and the min and max value.
(By the way the result is the same when I try to use a button on the global rackspace panel that’s mapped to the same function in the system actions plugin. The button itself works fine but mapping a pad on my midi keyboard doesn’t work.)
Coud it be that this results from a single push on the midi pad? It woud meen that you have something like a “falling roll” activated. The good momentary configuration would be:
press your pad : a CC20 with value higher than 0 is produced
release your pad : a CC20 with value 0 is produced
Absolutely. I just need to figure out how to do that on my controller, seems to be a bit tricky at least. According to the MIDI monitor the Keylab doesn’t even send specific aftertouch signals but just a bunch of control signals with different velocities.
It’s the Keylab 49 Mark 1 and I got it connected via USB with no additional MIDI appliances. My GP rig is clean, no additional midi plugins. I do have another midi keyboard attached. And yes, the Keylab always behaves the same, no matter which GP rig I use.
