I bought the Keylab as part of the Producer Pack bundle which is how I ended up with Bitwig.
The mappings on the sliders and knobs don't match up with the numbers on the display panel of the keyboard. The display panel works fine in Reaper.
When I plug in the MIDI monitor in "Arturia Mode" (bank 2) the data I get is completely different than the keyboard display.
http://cescato.altervista.org/VST-MIDI%20Monitor.htm
For instance, the first knob's data stream is CC#74 0-127, but the display reads CC#35 61-67.
Similarly, the first slider's data stream is CC#73, but the display reads CC#67.
None of the knobs or sliders have the correct CC#'s.
This wouldn't normally be a big deal, but some VSTs use CC#'s instead of MIDI Learn to map to the controller. So it is very confusing to have the wrong information.
MIDI CC mapping incorrect for Arturia Keylab 49...
-
- KVRian
- 532 posts since 18 Sep, 2013 from Mesa, AZ
~ good luck ~
~ re~member to do good in a spirit of love, unity, compassion, and kindness ~
~ re~member to do good in a spirit of love, unity, compassion, and kindness ~
-
- KVRist
- 392 posts since 20 Nov, 2014
I have a 61 key and the mappings were wrong on the default factory firmware. Once I updated to the latest firmware on The arturia site all was fine.
Formally known as CnuTram.
-
- KVRian
- Topic Starter
- 532 posts since 18 Sep, 2013 from Mesa, AZ
I'm running the latest firmware though, 1.33. Perhaps the display is showing data from bank1 instead of bank2, because Bitwig is re-mapping the CC's.
In the KeyLab.js controller script there is a function called sendTextToKeylab()...if that was updated to return the correct CC data to the display that ought to fix the issue I think. I'll see if I can figure out how to debug it, but I don't know Bitwig's controller API so it would be a bit of a shot in the dark.
In the KeyLab.js controller script there is a function called sendTextToKeylab()...if that was updated to return the correct CC data to the display that ought to fix the issue I think. I'll see if I can figure out how to debug it, but I don't know Bitwig's controller API so it would be a bit of a shot in the dark.
~ good luck ~
~ re~member to do good in a spirit of love, unity, compassion, and kindness ~
~ re~member to do good in a spirit of love, unity, compassion, and kindness ~
-
- KVRian
- Topic Starter
- 532 posts since 18 Sep, 2013 from Mesa, AZ
Basically Bitwig is remapping Bank2 with Bank1's CC data, and completely overriding Bank1...so when you're in Bank1 it's Bitwig mode and the knobs and sliders control Bitwig stuff. In Bank2 it's Arturia mode and it's sending Bank1 CC data so that the Arturia plugins don't get confused since they're expecting data from Bank1 instead of Bank2. Unfortunately the firmware still thinks it's on Bank2 and sends the display that information, but Bitwig is actually sending Bank1 data to all the VSTs.
It took me a couple hours since I didn't know what I was doing, but I was able to go into the controller script and send a display update with the correct information, overriding what the firmware was reporting.
Simply place the attached file into the "resources/controllers/arturia" folder in your Bitwig directory.
I guess now that I fixed it I'll post it to the controllers subforum and submit a support ticket to Bitwig with the update.
It took me a couple hours since I didn't know what I was doing, but I was able to go into the controller script and send a display update with the correct information, overriding what the firmware was reporting.
Simply place the attached file into the "resources/controllers/arturia" folder in your Bitwig directory.
I guess now that I fixed it I'll post it to the controllers subforum and submit a support ticket to Bitwig with the update.
You do not have the required permissions to view the files attached to this post.
~ good luck ~
~ re~member to do good in a spirit of love, unity, compassion, and kindness ~
~ re~member to do good in a spirit of love, unity, compassion, and kindness ~