DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.1)

[Guanavia]

Hi Jurgen,

Absolutely love you Bitwig extension. SO useful, thank you for doing it.

I'm curious if you're considering adding support for the MPC Studio to the list of supported MPCs?

I got rid of my MPC One to focus more specifically on learning Bitwig more deeply, but REALLY miss the MPC pads. I've tried a bunch of other pad controllers, but for some reason the MPC pads just feel better to me (I like the added resistance over something like SL MkIII) and would love to get great integration with the MPC Studio.

Best.

[moss]

Hi Jurgen,

Absolutely love you Bitwig extension. SO useful, thank you for doing it.

I'm curious if you're considering adding support for the MPC Studio to the list of supported MPCs?

I got rid of my MPC One to focus more specifically on learning Bitwig more deeply, but REALLY miss the MPC pads. I've tried a bunch of other pad controllers, but for some reason the MPC pads just feel better to me (I like the added resistance over something like SL MkIII) and would love to get great integration with the MPC Studio.

Best.

No, I have no plans. It works completely different and I am not sure if it is even possible to support it.

[moss]

Quick question… do wireless game controllers work with DbM or USB?

If it is detected by the OS as a game controller it should work.

[moss]

Hi Jürgen,

thank you for your outstanding coding work! I recently moved from Ableton to Bitwig and managed to integrate my launchpad with the DAW flawlessly. I got the latest firmware, downloaded the latest version of drivenbymoss and it got also autodetected. Although my launchkey mini mk3 won't get detected at all. The same here, latest firmware and so on...
When I add it manually, I can get it work as a normal midi keyboard (with the help of your specific midi in/out configurations). But it shows me only the "drum" and "custom" settings for the pads. I cannot enter the session mode. The launchpad on the other hand jumped instantly to session mode per default...

Any ideas how to get it working?

Thanks a lot!
Children of our Stars

Not really. Firmware is the only real idea but you say you checked that already. Besides that,
- try to connect it without the other Launchpad
- try a different US cable / port

[moss]

Hello Jürgen,
i m testing your incredibly awesome OSC script, which works really fine (i will ask bitwig support soon about the "clip playback progress" function, which will be awesome I put some "dummy" midi input there, so i can activate the OSC controller. But although i can use Touch OSC smoothly with OSC adresses, as soon as i try to also use Midi CC, i got a problem, because Bitwig does not seem to send back Midi info!? I can assign my touch OSC controllers via Midi CC to Bitwig controllers like Volume without any problem. BUT, when i move those controllers in Bitwig, they don't send their new position towards Touch OSC.
I m using your "generic - flexi" script, with Loop Midi going in, and another Loop Midi Port going out. Those Loop Midi ports are properly connected to Touch OSC, i know this, since i tested it in Ableton and everything works smoothly there - bidirectional.
Now i realized: this also counts for my Komplete Kontrol S49mk2 Keyboard-Encoders! I can assign and use them via the Keyboard - but when i fiddle around within Bitwigs interface , i dont see any value-change in my KK Display! So this seems like a topic also affecting other midi controllers (i m also using your NI KK S-series script for the Keyboard).
This "no-midi-out-problem" persists, even when i deactivate the OSC script, or use the Touch OSC bridge instead of Loopmidi.
Bitwig 5, Beta v5, 20.1 drivenbymoss script.
Maybe you know what the problem could be? Thank you!

Not sure if I fully understand what you are doing but if you map a MIDI CC in Bitwig it will "overwrite" the buttons function and you will also get no feedback. To get bi-directional mapping either use the different modes (and remote control parameters) or only use the MIDI mapping with USER parameters. They will also give you feedback.

[moss]

Guten tag Jürgen,

First of all great work on your script, my Launchpad X works perfect with Bitwig,
really impressive what a functionally you put in there!

But one little question
Is there a way to switch pages instantly, from track 1-8 to 9-16 and back, which just one button press?
Now I have to scroll thru several tracks or use bird eye view.
Ideally is would like to use the left and right arrow in session view to go to next/previous page.
Or is there way I can map this myself?

thanks and keep up the great work!

Currently not. But I think it might make more sense to flip the cursor key behaviour.

[stuzog]

Is it possible to use DBM 20.1.0 with Bitwig Studio 5betas and DBM 19.2.2 with Bitwig 4.4.10 during BW5 testing?

[moss]

Is it possible to use DBM 20.1.0 with Bitwig Studio 5betas and DBM 19.2.2 with Bitwig 4.4.10 during BW5 testing?

No. Only if you switch the bwextension file as well.

[zemoonie]

Hey Moss!

First, thank you for your incredible effort for maintaining this whole ecosystem of scripts, I've been using them for years

I recently purchased a LaunchPad Mini and a MidiFighter. I know that there are dedicated script controllers for those, but as I need some flexibility with my setup I thought to manually set everything with Flexi instead, so that I can map the CC to various elements across tracks.

For my setup to work, it's very important that the controller gets feedback when the mapped parameter is changed. The only way that I could make it work is to use the "User" functions in Flexi, but that's limited to only 8 parameters + 8 toggles, while for instance the MidiFighter has 16 knobs and 16 buttons and I'd like to avoid using pages.

Is there another way that I might be completely missing? I originally tried with simple MIDI CC instead but I don't receive any feedback on the controller if the mapped parameter is changed.

I also noticed something that appears to be a bug in the Flexi script:

1. Map a CC through Flexi to User parameter
2. Map the parameter to a track volume fader
3. Also map a momentary button to the track volume fader, change the action to Set Value To and the target value to -Inf
4. Move the controller CC to set the value of the volume fader to anything but -Inf. Also move the track fader and verify that the controller receives the feedback (tried with both the launchpad in custom user mode with a fader and with a MidiFighter knob)
5. Press the momentary button to set the volume of the track to -Inf

Expected:

The controller receives the new value of -Inf and resets its LEDs accordingly

Actual:

Occasionally, the controller doesn't receive the update and the LEDs value, as well as the controller value (so in order to regain control of the parameter, I have to move the hardware controller to zero to pickup)

I also tried the same with using a Track function (Set Volume) and could reproduce exactly. It doesn't always occur so you might have to try a few times, but at least in my experience, on an empty project, 4-5 times are enough.

Thanks and let me know if I can help you further with more details.

[Guanavia]

[/quote]

No, I have no plans. It works completely different and I am not sure if it is even possible to support it.
[/quote]

Ahh, understood. Thanks for the reply! If you ever do randomly decide to test it I'd definitely use it.

Best

[moss]

Expected:

The controller receives the new value of -Inf and resets its LEDs accordingly

Actual:

Occasionally, the controller doesn't receive the update and the LEDs value, as well as the controller value (so in order to regain control of the parameter, I have to move the hardware controller to zero to pickup)

Check what you have set as the "Takeover mode". This normally happens when you have set it to "Catch". Change to immediately.

[quincy]

Hi Moss. I've just picked up an Ableton Push MK 1 and I'm having trouble working out if I can focus the track or project level remote controls from the Push. If I focus the project/track remotes with the mouse then the controller shows them (the 8 knobs correspond) but I can't work out how to focus the track or project remotes from the controller.

I'm using Bitwig 5 beta 6. Thanks for all the help.

[moss]

Hi Moss. I've just picked up an Ableton Push MK 1 and I'm having trouble working out if I can focus the track or project level remote controls from the Push. If I focus the project/track remotes with the mouse then the controller shows them (the 8 knobs correspond) but I can't work out how to focus the track or project remotes from the controller.

I'm using Bitwig 5 beta 6. Thanks for all the help.

This is not implemented yet. Just learned today how it might get implemented.

[quincy]

Great, thanks for getting back to me. I haven't tried your older script for 4.4 yet so I'm curious to try that as well.

[nowiamone]

Hi,

Concerning my "bidirectional" Midi-Problem: Sorry for describing my problem not precisely.
Coming from Ableton i would expect the following way of midi-mapping to work bi-directionally:
- Strg+M = Midi Map mode active.
- Pressing "midi" on the NI KK S49mk2 Keyboard to have some custom-assignable encoders
- assigning the first encoder(cc14) to a Volume Fader in Ableton
-> Result: The Fader is controlled by the encoder. And moving the Fader in Ableton changes the value shown in the KK Keyboard Display.

Now, trying to do the same in Bitwig:
- pressing on the 'Hand' symbol in the bottom right, to open up the mappings panel, then clicking on a Volume Fader in a Bitwig Track (alternatively: rightclick on the fader, clicking on assign midi)
- Pressing "midi" on the Keyboard
- assigning the first encoder (cc14) to the Fader
- closing the mapping mode
-> Result: The Fader is controlled by the encoder. But moving the Fader in Bitwig does not change the value shown in the KK Keyboard Display. [same thing for all take-over-modes]
To troubleshoot this behavior in Ableton, i would check, if the "Remote" row of the KK keyboard is deactivated in the midi-preferences. But i don't know how to do that in bitwig.

Bitwig Beta 5 v6 here, using Komplete Kontrol S49mk2 with your 20.1 drivenbymoss script

Sorry for yet another question, about the Keyboard script:
How to adjust the KK controller settings to do the following within the Clip-View with vertical Scenes:
1) Lets assume our current clip-selection-focus lies on Track 2, Clip 5 (so within Scene 5). Moving the navigation-knob upwards should not switch focus to the track above, but rather the clip above, in exactly the same Scene! So: no horizontal change of selection-focus, when moving "up". "Up" should mean up, and not also moving to the total left, then forcing the user to press right however times necessary to get back to the Scene where the "up" was intitially pressed. Same for down-movement.
I would suggest an assignable toggle button for fast track- and scene-selection. When this toggle button is held down, it will switch the navigation-knob to the "meta-ebene" , which means tracks (up/down) and scenes (left/right). When this magical meta-ebene toggle-button would not be pressed down/or toggled, the navigation-knob would again function as described above, navigating the clip-grid.
This would combine the best of both worlds: a) clip-grid and b) track/scene navigation, in an extremely fast way, because the focus-switch is midi-assignable (which is far superior to any non-midi-assignable implementation of this switch in the controller-script-preferences for example).

To not anger people who like things as they are, this "up means up, down means down" style of navigation could be switched on/off in the preferences. Also for the preferences i would suggest an additional "stay within clip-grid (exclude tracks/scenes)" on/off so the user can choose if moving to the far left selects the track, moving to the top selects the scene - or not.


2) not so important, but would be nice: "CLEAR" button on KKS49 should clear (delete) the selected clip. "Mode select" could then be on some other button, like the usually un-used first button above the display. I tried to assign one of the top-row buttons to Bitwigs "delete" function, but no luck - this is no good workflow compared to a scripted Button like Clear, since, one has to change the keyboards mode to Midi, each and everytime one wants to delete a clip with a custom button.

Thank you alot!