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

[nowiamone]

5 When trying to build a properly functioning browser via the existing /osc adresses, some adresses don't work as expected, or are missing. When using /browser/filter/4/{+,-} to scroll through Tags, for example, those tags will immediately be committed and therefore not let the user scroll through the whole list of tags anymore. The user will be stuck, until resetting the filter, and in addition /browser/filter/x/reset doesn’t work, and there's no /focus filter xy column, and /clear focused filter, available. (Just like no /select quicksource xy).
And /browser/filter/{1-6}/item/{1-16}/isSelected, and /browser/result/{1-16}/isSelected seems unusable for actively selecting the result. Direct selection would be reaaally awesome though.
Thanks to your awesome /action list, i was able to build some workarounds - but now i reached the /action 20 (limit of the /actions) because of those workarounds, haha. But nevermind, those are "first world problems".
I think this whole browser topic is difficult due to Bitwigs browser-re-make, since version 5.0? I can guess the API might be a bit weird in the browser-realm, since then, haha

Browser is currently quite broken since the changes of Bitwig 5 are still not reflected in the API.

Hello Mr. Moßgraber,
I clearly remember you saying that the status of the Bitwig browser in the API has been “broken” since version 5.0 - but it seems to me that it actually works (again?) via the API, for example, to select search results individually. But not with your OSC script, unfortunately

Using /browser/result/{1-16}/isSelected to select browser results via remote control is “broken”/buggy in the OSC script (wrong results are selected, or none) - but it seems to me that it could be fixed! It would be great if you could take another look at that, specifically the correct wiring between the OSC script and the API for individually selecting and loading search results in the browser. It's about adding a logic to catch numerical indexes and the "item" subcommand so you can leverage the Bitwig API's ability to select items from a bank by index. Thank you so much!

[LuapSand]

Hi,

the Bitwig Connect 4/12 has a feature called "Bitwig Mode" where turning the jog dial controls whichever parameter the mouse is currently hovering over in the Bitwig GUI. I find this workflow extremely useful.

My question: is the underlying API that enables this "mouse-hover parameter control" publicly exposed in Bitwig's Controller Scripting API? Or is it an internal/privileged channel exclusive to the Connect 4/12's own script?

Background: I'd like to replicate this experience using a different controller (e.g. Electra One or similar) via a custom controller script. Before investing time in coding, I want to understand whether this is technically feasible for third-party scripts, or whether Bitwig has kept this API surface private for the Connect 4/12.

Has anyone looked into this, or has Moss already explored it?

Thanks!

[LuapSand]

Ok nevermind. Found it my self. It seems indeed possible. I think Moss used it already: "Last Parameter control & adaptive scrolling"

[moss]

In Bank/Device mode, pressing the lower page buttons can sometimes cause Device view to jump to Channel view. If you re-enter Bank mode and press the lower buttons again, it can happen repeatedly. On a fresh restart, using Hierarchical track view seems more reliable, but eventually the Device view still jumps up a layer.

The function to "go up" is executed when you long press one of the 8 buttons. I noticed that there is an issue if you quickly switch between 2 buttons. I changed some things to make it more solid and hope that this fixes it. Will be in the next update.

[moss]

Hey Jurgen

I have a polite feature request if possible to accommodate in some shape or form ?

Using a Kontrol mk3

I love using bitwigs groups and the enter group / exit group functionality. I have this set to two shortcuts on my typing keyboard and this works to dive into the group and the tracks are then reflected on the mixer on the Kontrol screen. (makes it easier to focus on a specific group).

Would there be any way to incorporate an Enter / Exit group functionality on the Kontrol keyboard itself?

Potentially:
SHIFT + RIGHT ENCODER to enter group
SHIFT + LEFT ENCODER to exit group

Many thanks

Sorry, no. We are sadly pretty fixed to what is possible on these devices. Send such requests to NI.

[moss]

Dear Mr. Moßgraber,
is sending /time/signature broken for Bitwig 6 with the OSC script?
i try (/time/signature) STRING(3 / 4)
and (/time/signature) STRING(3 / 4)
and nothing seems to work to set Bitwigs time signature.

Recieving it works though , via the same adress and same formatting...
RECEIVE | ENDPOINT([::ffff:127.0.0.1]:63226) ADDRESS(/time/signature) STRING(3 / 4)
works fine.

But sending to Bitwig doesn't? Any help/info is appreciated

This message is currently only sent but not received. Will add it to the wishlist.

[moss]

Hi, I'm new to the this website and I couldn't find a search button on this thread so I wanted to ask about my touchosc problem myself. So I have touchosc app installed on my tablet. On protokol, i can see both midi and osc connections are working. In bitwig however, only midi connection works. I came to that conclusion because i can't control my DAW from my tablet if i disable midi connection type; disabling or enabling osc however, does nothing. So I set up drivenbymoss extension for bitwig, but still does not work (only thing i did was copy paste a file into "Program Files\Bitwig Studio\resources\Extensions", so idk if it was actually enough but i see the "by drivenbymossgraber" text down below after selecting osc product in bitwig dashboard). I should also note, I use my tablets ip on "host to send to" on bitwig, and also the touchosc app can see my pc as a host. Send and receive ports are also compatible. The reason i need osc connection type to work is because i made a custom template on touchosc and i couldn't make it work since midi control numbers are more than 128, changing channels after 128 didnt work for some reason so i guess i need the osc connection type.

For reaper, someone on reddit told me to do this on touchosc "Scroll down in the button settings, remove MIDI message, In the OSC message remove preexisting address entries, Click + in the osc address and add a constant, In the constant write "/action/1007" (this starts playback)" and it really worked, i didnt even need to map it in bitwig afterwards. But i guess there are no command IDs in bitwig unlike reaper. So i feel totally lost. Is there something i should be writing in the address section, if so, what?

Here is a playlist of all of my OSC tutorials:

Also the DrivenByMoss manual explains in detail all available OSC commands.

[moss]

UPDATE 7/04/26 - solved questions 1 and 3 today by examining more carefully the options offered in the setup screen. What a great piece of software you have built.

2) Is there a new drivenbymoss extension version for Bitwig 6.0/6.3 in the pipeline?

There are no changes in the API for Bitwig 6. So, no need to change anything but will test more in-depth in the next days.

[moss]

Hello Mr. Moßgraber,
I clearly remember you saying that the status of the Bitwig browser in the API has been “broken” since version 5.0 - but it seems to me that it actually works (again?) via the API, for example, to select search results individually. But not with your OSC script, unfortunately

Using /browser/result/{1-16}/isSelected to select browser results via remote control is “broken”/buggy in the OSC script (wrong results are selected, or none) - but it seems to me that it could be fixed! It would be great if you could take another look at that, specifically the correct wiring between the OSC script and the API for individually selecting and loading search results in the browser. It's about adding a logic to catch numerical indexes and the "item" subcommand so you can leverage the Bitwig API's ability to select items from a bank by index. Thank you so much!

I just did some tests with 6.0.3 and could not spot a problem. Yes, it kind of works but the API still does not support the features of the new browser. If you still have issues please explain in more detail how to reproduce them (e.g. with which devices on the track).

[moss]

Ok nevermind. Found it my self. It seems indeed possible. I think Moss used it already: "Last Parameter control & adaptive scrolling"

See here:

[LuapSand]

Ok nevermind. Found it my self. It seems indeed possible. I think Moss used it already: "Last Parameter control & adaptive scrolling"

See here:

Danke!!

[moss]

DrivenByMoss 26.6.1 is online!

Get it from https://mossgrabers.de

• New: Prevent accidently firing of long button press event when quickly changing between two buttons.
• Fixed: Electra One
  • Fixed: Update of transport positions was only slowed down in mixer mode.
  • Fixed: Values might not have been updated when switching modes.
• OXI One Mk1/Mk2
  • New: Made Note Edit and Automation mode temporary so it can be closed with the BACK button as well.
• OXI One Mk2
  • New: Made Generator and Groove mode temporary so it can be closed with the BACK button as well.
  • Fixed: BACK button was not working.

Enjoy!

[olimpo]

Many many thanks Jurgen !!!

[olimpo]

Sequencer: I have Bitwig 5.0.11 and Launchpad Pro Mk3, I can't make the sequencer work with your scripts, DrivenByMoss 24.3.0 and DrivenByMoss 19.2.2. Sounds are not triggered, sequence is not recorded. The rest works alright.
The sequencer works just fine when used with Bitwig's own native script.
What can it be? Maybe I Should try with still older versions? Thanks!!

[moss]

Sequencer: I have Bitwig 5.0.11 and Launchpad Pro Mk3, I can't make the sequencer work with your scripts, DrivenByMoss 24.3.0 and DrivenByMoss 19.2.2. Sounds are not triggered, sequence is not recorded. The rest works alright.
The sequencer works just fine when used with Bitwig's own native script.
What can it be? Maybe I Should try with still older versions? Thanks!!

It helps a lot if you describe what you are doing to use the sequencer. Is a MIDI clip selected?