Very frustrated. The knobs/sliders work fine (mapped through MIDI MAP), but not the pads. Have tried all config options I can think of (notes, control change, program change). Nothing works.
Has anyone got this to work? Otherwise, it’s going back. My little Alesis kbd works just fine.
You can try Stoermelder MIDI-CAT instead. (It can map MIDI Note and MIDI CC)
Or keep using VCV MIDI-MAP after you change the Minilab in Arturia Midi Control Center to send CC’s for the pads - here’s a picture from the user manual
I always use this tool to view exactly what MIDI messages, (notes, CC, channels, etc…), is sent from an external MIDI device. Then if I need to make change I know what I need to do (either in the MIDI controller or in VCV). Great tool.
Swapping in the Stoermelder module fixed it. For some reason the base VCV mapper doesn’t respond to the CC messages from this kbd (the SM module works perfectly).
OK I took Jay’s suggestion and put the SM Monitor on it.
Seems the problem is the KBD. Whatever settings I burn into its ROM, it only ever sends note messages. These can be interpreted by the SM but not the VCV. Problem solved. I’ll look to see if there’s a known bug with the firmware.
My MIDI keyb is a Oxygen61 from M-AUDIO. The pads only send note messages on MIDI channel 10 . So I have to use one seperate MIDI-CAT to received them on channel 10, and then I transform them into triggers or other things. Much more complicated than just changing at the source (e.g.: Arturia MIDI control center), but that’s my work around.
That is why, for my setup, I needed the MIDI monitor. I could clearly see that the keyboard notes were sent using ch. 1, the faders and knobs on ch. 16 and the pads on ch. 10.