GuruBlog

In bitwig-studio you controller mappings can be scripted using a javascript api. Fortunately most of the midi controllers I own (Launchpad, nanoKontrol, nanoPad, ...) are already mapped and all I had to do was to connect them. This weekend I found my very first hardware usb controller I bought back in the days when iMacs looked like candy and macos X was released. The M-Audio iControl for GarageBand. As the name suggests it was designed to work with GarageBand a very striped down version of Logic that came for free with MacOS X.

Since I wanted to play with the bitwig controler api for some time now I took the challange and wrote a midi mapping for the controller.

I mapped the mute, record arm and solo buttons to the according functions for the first 8 tracks.

The master volume slider controls the master volume

The transport control buttons are mapped to the corresponding functions int the bitwig transport sections. I also made the leds of the controler light up if someone clicks play, record or loop with the mouse by using Observer functions.

The 8 endless rotary encoders are mapped to volume, pan, send1, send2 or the first 3 macros of the first device of a track, depending on which button on the left of the controller is selected. This resembles the midi mapping that was implemented in GarageBand back in the days

I'm not sure if anyone else still has this board lying around, but if you do give my script a try and tell me in the comments section below

you can download the script for my github repository

to install it simply copy it to your "~/Bitwig/Controller Scripts" directory