asked Dec 23 '17 at 13:56 by maranite (11)

In Bitwig v2.2, the controller script for Arturia Keylab doesn't work correctly, specifically: * Absolutely fuck-all works (except the keys)

Track selection, device selection, macros, envelopes, you name it, it's busted. All worked fine on v1.3 [Keylab 88 firmware is v 1.2.6 latest)]

After several frustrating hours of trying to debug the controller javascript files, I finally figured out that Bitwig no longer uses the javascipt controller files... removing every last controller script on my system wouldn't get rid of the "(by Bitwig)" drivers (for Arturia KeyLab & Akai), suggesting that these have been baked into the app, and designed to override/bypass ay existing scripts. What a horrible design choice!

Moreover, frustrated efforts to get my personal Keylab script working have revealed what appears to be a bug/regression in Bitiwg... The controller Javascript engine doesn't handle tuple deconstruction any more. In v1.3, Thomas Helzle's script made extensive use of this common javascript feature... you can test the bug with the code below (paste it into a controller.js file, and fire up Bitwig studio):

host.defineController("Tuple", "Test", "1.0", "afff5ae0-bbbb-11e4-ab27-080020000066");
host.defineMidiPorts(1, 1);

function ReturnsAnArray() {
    return ["Tuple", "Test"];

function UsesJavaScriptDeconstruction() {
    var qq;
    var ww;
    //[qq,ww] = Y();  // uncomment this line and Bitwig rejects/hides the controller!!!

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Dec 23 '17 at 13:56

Seen: 259 times

Last updated: Dec 23 '17 at 13:56