Let’s see. It’s been awhile since the last Month in Music Tech update. I’ve been heads down learning C++ and the JUCE library over the last month or so. Hopefully in a few more months I’ll have a new app to unleash on the world thanks to JUCE’s new licensing model, which makes it more accessible

I just released an updated version of my BeatStep Pro controller script for Bitwig Studio 2.0. The release is available at https://github.com/benschmaus/bitwig-beatsteppro/releases, and it has the same functionality as described at https://factotumo.com/2017/01/bitwig-bsp-script-update-enhanced-cursor-device-control/. In a nutshell you can use each of the BSP’s sequencers independently as MIDI inputs for tracks, control cursor device params/macros, and navigate tracks, devices, and

I made a few small tweaks to the Bitwig Beatstep Pro script I released a few weeks ago. The encoders now control parameters and macros for the cursor device of the selected track instead of the primary device. Since you can navigate the selected track’s device chain using steps #3 and #4 in control mode

I’ve written about Bitwig controller scripts for Arturia’s Beatstep Pro step sequencer before. After getting some good mileage out of justlep’s Bitwig scripts, I found myself wanting a little more. In particular, I wanted support for controlling a track’s primary device parameters and macros without having to manually assign the encoders. So I decided to write a

[Update, 12/12/2016]: I put together a new Bitwig script for Beatstep Pro to address some of the shortcomings I discovered with the scripts discussed in this post. Notably, the new script supports controlling device params and macros without having to manually map the BSP encoders, navigating tracks, browsing/selecting presets and a few other things. Arturia’s Beatstep Pro,