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

[dmirate]

Hi!

I’ve been lurking around looking for info on MIDI Fighter Twister and using Driven by Moss script. I feel some of the info I’ve found (here or on other forums/Reddit) is conflicting (or I’m just not understanding it).

I’m trying to set up my fighter with basic functions. Eight encoders on one page to be the Bigwig remote controls, and the other 56 are reserved for direct cc mapping.

My question - understanding the Bitwig remote control knob’s will have bidirectional feedback - will the other 56 encoders also have that?

I tried this already, and I could only get the eight remotes to be bidirectional. I did toggle the option on the mapping screen to send feedback on the others (as well as the remotes). Did I do something wrong, or is this a limitation? Thanks in advance!

EDIT - I went a different route, and used 1st Instrument, Device, Track, and Project Remotes. I think that is probably more than enough for me (plus the pages for each). But I am still interested in knowing if there is a way to do this. I did find what might be a bug - I'll post that next.

2nd EDIT - Moss, this is a fantastic script. Once I got into it, I really discovered how deep you can go, even with the generic settings. Thanks so much for making this available. Do you have a patreon, or some sort of way I can donate to your cause? Or shirts or mugs that I can buy? Anything?

[dmirate]

Hi Moss,

I think I may have found a bug. I have one mappable parameter that does not work as expected. This is 1st instrument, parameter #1 reset. I have mapped MIDI CC 8 on channel 2 to this parameter. This is currently Slot 208 in my program.

It does not do anything.

I did a couple of tests to rule out a few things:
1. I changed that same MIDI CC 8 / Channel 2 to reset 1st Instrument, Parameter 2 - it resets as expected.
2. I mapped a different MIDI CC, which was CC 9, also channel 2 to reset 1st Instrument. It does not work.
3. I tried using another slot (just in case, #300), MIDI CC 8 / Channel 2 - It does not work.
4. I tried different knob modes (on both slot 300 and 208).
5. I tried changing the resolution to 14-bit (although I am not sure what that does).
6. I did not do anything with the "Functions Layer" or "Type" drop-downs

So I think it has something to do with 1st Instrument, Reset Parameter 1 - unless it has to do with #6 above, but the other 31 controllers I mapped the same way work without extra required settings.

In case it matters, here are the reset of my settings for this slot:

2025-06-15_12-40-57.png

[moss]

Hi!

I’ve been lurking around looking for info on MIDI Fighter Twister and using Driven by Moss script. I feel some of the info I’ve found (here or on other forums/Reddit) is conflicting (or I’m just not understanding it).

I’m trying to set up my fighter with basic functions. Eight encoders on one page to be the Bigwig remote controls, and the other 56 are reserved for direct cc mapping.

My question - understanding the Bitwig remote control knob’s will have bidirectional feedback - will the other 56 encoders also have that?

I tried this already, and I could only get the eight remotes to be bidirectional. I did toggle the option on the mapping screen to send feedback on the others (as well as the remotes). Did I do something wrong, or is this a limitation? Thanks in advance!

EDIT - I went a different route, and used 1st Instrument, Device, Track, and Project Remotes. I think that is probably more than enough for me (plus the pages for each). But I am still interested in knowing if there is a way to do this. I did find what might be a bug - I'll post that next.

2nd EDIT - Moss, this is a fantastic script. Once I got into it, I really discovered how deep you can go, even with the generic settings. Thanks so much for making this available. Do you have a patreon, or some sort of way I can donate to your cause? Or shirts or mugs that I can buy? Anything?

If you only send MIDI CC to Bitwig, it is one way. Your solution is the one I would have suggested as well.
You can donate below each video on Youtube (The THANKS button is hidden behind the "...").

[moss]

DrivenByMoss 25.5 is online!

Get it from https://mossgrabers.de

• New: Added support for Intuitive Instruments Exquis

Enjoy!

[moss]

Hi Moss,

I think I may have found a bug. I have one mappable parameter that does not work as expected. This is 1st instrument, parameter #1 reset. I have mapped MIDI CC 8 on channel 2 to this parameter. This is currently Slot 208 in my program.

It does not do anything.

Good catch! Will be fixed in the next update (not the one I just released).

[itisjanuary]

Moss, I was curious as to whether you have used the Novation Zero SL MK2?
It is very similar to the SL mk2, sans keybed and features additional faders/controls.
I am hoping to get to use it with your software, and if it is not directly compatible, I would like to humbly request its addition in the future.

[itisjanuary]

I just heard you say in an old video that the zero is fully functional. I'll give it a go!

Thank you for your amazing work.

[McSpekkie]

Hi Moss!

I’ve created my own Bitwig color palette that displays perfectly and one-to-one on the Launchpad Pro MK3 when using Bitwig’s native support. However, when I switch to DrivenByMoss—which I much prefer to use—the colors no longer match.

I would really like to have a palette that works one-to-one with the Launchpad Pro MK3 via DrivenByMoss.

Could you please explain how DrivenByMoss translates Bitwig colors to Launchpad colors? Or, if you prefer, could you create such a palette yourself?

Thanks in advance!

[isosis]

Hey Moss!

I can't get the script to wortk with the Exquis - it *looks* like it works, finds it, notifiation says its working etc, but it receives nothing - when i set it up to use the bitwig and very limited Exquis script that works, so it is sending midi , juts not working via the Moss script

[moss]

Hi Moss!

I’ve created my own Bitwig color palette that displays perfectly and one-to-one on the Launchpad Pro MK3 when using Bitwig’s native support. However, when I switch to DrivenByMoss—which I much prefer to use—the colors no longer match.

I would really like to have a palette that works one-to-one with the Launchpad Pro MK3 via DrivenByMoss.

Could you please explain how DrivenByMoss translates Bitwig colors to Launchpad colors? Or, if you prefer, could you create such a palette yourself?

Thanks in advance!

There is no API support in Bitwig to get the current palette. Furthermore, the color palette on the Launchpad has 127 fixed of which many colors look quite identical. Therefore, it would be helpful anyway.

[moss]

Hey Moss!

I can't get the script to wortk with the Exquis - it *looks* like it works, finds it, notifiation says its working etc, but it receives nothing - when i set it up to use the bitwig and very limited Exquis script that works, so it is sending midi , juts not working via the Moss script

Could it be that both extensions are active?

[isosis]

I don't believe so, i removed the old one from the config - when I do that Bitwig gives me options of the mappings to add and has both options but i just pick the Driven one, and the other is not setup in the config anywhere

[moss]

I don't believe so, i removed the old one from the config - when I do that Bitwig gives me options of the mappings to add and has both options but i just pick the Driven one, and the other is not setup in the config anywhere

I have a slightly newer firmware (which is not released). Could be that there is an incompatibility. Will check back.

[nowiamone]

EDIT: i thought /vkb_midi/channelselection was broken, but it actually was a mistake on my side

[Bruno-IntuitiveInstru]

I don't believe so, i removed the old one from the config - when I do that Bitwig gives me options of the mappings to add and has both options but i just pick the Driven one, and the other is not setup in the config anywhere

I have a slightly newer firmware (which is not released). Could be that there is an incompatibility. Will check back.

Hello there, Bruno from Intuitive Instruments writing.
I have double checked with the current official firmware (2.1.1), the one you can download form our website, and everything works fine in Bitwig with DrivenByMoss version 25.5.0. and Bitwig 5.3.8.