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

[icaria36]

A bit more about the Oxi One MK2:

https://oxiinstruments.com/forum/d/3393 ... ntroller/2

Very nice. Let's see if they change their mind.

I asked again hoping to get a more technical answer, but their second reply, while leaving room for optimism, is still lacking technical details:

> Yeah, Moss would be able to do it

https://oxiinstruments.com/forum/d/3393 ... ntroller/3

I asked whether the MK2 has the enablers for third party developers already in place but the reply, as I read it, seems to say that a specific developer (Moss) "would" bee able after talking to them, meaning that the enablers are not in place or not documented in a way that a third party developer on their own can use them.

Dunno, maybe I'm reading too much in those few words. I don't want to be that obnoxious non-tech guy insisting on a point in a web forum, so I will leave it there with the hope that some day...

[aMUSEd]

Does Reaper have anything like Bitwig remote controls to configure plugins so they recall the same device mappings each time they are loaded?

[moss]

Does Reaper have anything like Bitwig remote controls to configure plugins so they recall the same device mappings each time they are loaded?

Sadly, not. But I added a configuration layer for parameters with pages that work like in Bitwig.

[aMUSEd]

Does Reaper have anything like Bitwig remote controls to configure plugins so they recall the same device mappings each time they are loaded?

Sadly, not. But I added a configuration layer for parameters with pages that work like in Bitwig.

Thanks I will try and work out how to use that, have you done a video on how it works?

[moss]

Does Reaper have anything like Bitwig remote controls to configure plugins so they recall the same device mappings each time they are loaded?

Sadly, not. But I added a configuration layer for parameters with pages that work like in Bitwig.

Thanks I will try and work out how to use that, have you done a video on how it works?

[thomba]

I've recently started using your updated Komplete Kontrol integration for the MK3 with Firmware 2.0 in Bitwig — great work overall! However, I’ve run into a few issues and questions I hope you can clarify or look into:

1. Inconsistent Knob Mapping with Some Plugins

In Bitwig, certain plugins (e.g., Arturia’s CS-80 V4) display parameter assignments automatically — even without a defined Control Editor template. However, when using your script, the same plugins show no knob allocations at all on the MK3. This seems like an inconsistency in how parameters are being mapped or exposed.

2. Unexpected Behaviour When Adding Instruments and FX

I followed the same steps shown in your demonstration video, starting a new instrument track from scratch. However, I encountered some odd behaviours. I've attached screenshots to help illustrate the issue (though please note, the images are in the wrong sequence — apologies for that).

Here’s what happened step-by-step:

Step 1: I created a new instrument track.

Step 2: I loaded the FM4 plugin. The parameter text was partially visible, but only two of the knobs responded to movement — the others appeared inactive or unmapped.

Step 3: I added an FX plugin — everything worked as expected.

Step 4: I switched back to the FM4 synth. Oddly, the title bar still displayed the name of the FX plugin (e.g., “Chorus”), yet the FM4’s parameter knobs were now visible and responsive — which they weren't in Step 2.

So it seems the controller’s UI and parameter mapping doesn’t always refresh or update correctly when switching between devices.

Maybe this is something specific to my setup, but I thought it was worth sharing in case others are seeing similar results.

Thanks again for the continued improvements — looking forward to seeing how this develops further!

Best regards,

[aMUSEd]

I've recently started using your updated Komplete Kontrol integration for the MK3 with Firmware 2.0 in Bitwig — great work overall! However, I’ve run into a few issues and questions I hope you can clarify or look into:

1. Inconsistent Knob Mapping with Some Plugins

In Bitwig, certain plugins (e.g., Arturia’s CS-80 V4) display parameter assignments automatically — even without a defined Control Editor template. However, when using your script, the same plugins show no knob allocations at all on the MK3. This seems like an inconsistency in how parameters are being mapped or exposed.

I'm guessing you mean this?

Screenshot 2025-09-09 at 14.40.18.png

This is normal for Bitwig - on the right are the default mappings organised how they were setup by the developer. On the left where it currently says 'No Pages' is the Remote Controls editor (which you can open in its own page) - here you can add params and rearrange them to suit your own needs - you can add as many pages of params as you like and you can choose to add them on a per preset or per device level (per preset would be if you wanted different setups for different purposes, per device means every time that device is loaded you get the same setup). Like this

Screenshot 2025-09-09 at 14.46.57.png

Once params are added to that they will show up in the keyboard

Where you are finding plugins that have it already setup it's usually because the developer has already created remote controls for it (or you have installed some of the ones we have shared in the thread below). Bitwig have done it for all their own devices and some companies (e.g u-he) have too (for some) but the gaps are the reason for the thread here:

viewtopic.php?t=480998&hilit=device

[thomba]

Hi and Hello - thanks for your response

No, what I am referring to is the different behaviour between both scripts in regard to the above subject matter.
Using the bespoke Bitwig Script knob assignments in this particular case appear. Although very random of nature, but nevertheless they appear. Using the DrivenbyMoss Script the knob assigment fields remain completely empty in this particular case.

I was just wondering if the above could be described as a bug or an inherent - not really important - difference in the approach of both scripts.

The latter issue only appears in my particular case when using the DrivenbyMoss script.

[aMUSEd]

By 'bespoke Bitwig Script' do you mean the one NI recently created for firmware 2?

[aMUSEd]

Just checked and I see what is happening - the NI one auto populates the keyboard display with the param mapping setup by the dev whereas the Moss one doesn't. That's interesting - although making your own is still the best option (or using NKS for instruments like the CS as the NKS2 mapping is superior)

[thomba]

We probably mean the same

But from what I understand it is NI providing the groundwork for any changes with the help of the firmware. It is then up to the DAW developers to provide the script to make the best out of the new opportunities for their individual DAW.

So for Bitwig one can choose between the Bitwig own script, which works fine and the DrivenbyMoss script (way superior in its approach) with which I experience the above issues.

[thomba]

I am actually using Komplete Kontrol a lot. It is just a very clunky software

[aMUSEd]

We probably mean the same

Yes we do

[aMUSEd]

I don't see this much because as a rule I either create remote controls for any device I am using when I first get it or for more complex synths I make a NKS mapping

Except for very basic plugins with just a handful of knobs I find the default mappings are rarely optimal for me

[thomba]

I don't see this much because as a rule I either create remote controls for any device I am using when I first get it or for more complex synths I make a NKS mapping

Except for very basic plugins with just a handful of knobs I find the default mappings are rarely optimal for me

Dito. I just wanted to raise this "issue".
But the actual problem is the handling issue laid out in my post as well