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

[lorenlepton]

Sure, you can do this. But I have no time to give guidance for such things.

Hahaha. That’s fair regarding having no time. Though I am glad that something can be done.
My coding fingers have been itching so I might just have a try & learn a few things that isn’t game dev

Thank again

[bombasstard]

And then something like "set current scene cursor to scene number XYZ"?

But you can monitor the state of the scenes.

Thank you - I see, if I can solve my problem in another way - otherwise I will dive into your development tutorials on YT to see how that works

[guppi]

Hello Jürgen,

I'm using 4 Akai Midimix with Generic Flexi side by side to have 32 channels of direct volume control. This works but I have to pin each controller also side by side when opening a new or another project. As this is done with 4 mouseclicks it is doable. It is not the main problem.

My problem is, that I couldn't find a way to fix the volume fader in Bitwig at 0db with Generic Flexi. This leads to the problem that I have to setup the mapping panel in Bitwig for each Project new every time and this is obviosly very counterproductive to the idea of having an already mapped 32 channel mixer with all projects with an upper limit at 0 dB. Could you give a parameter limitation within Generic Flexi to solve this problem or do you have an idea to circumvent this problem? Thank you very much!

Sorry, no idea.

General Flexi allows to switch mixertracks in their sequence or delete or add some of them without having to remap things everytime to the hardwarecontroller because of it's relative nature. This is great. When I limit the controller ranges in Bitwigs mapping panel, this realtive nature is gone and all of the mappings become absolute even the controller script is prioritized. I have no oversight or the skills to program stuff like a range limitation in general flexi so my 3 questions are this: is this theoretically possible? is there a script that does this so I could try to copy the codeparts and go crazy about it? Could you implement it?

I am not aware of a script that does this (but there could be).
Yes, it is possible but you would need to do this for each and every parameter. Therefore, this should better implemented in Bitwig itself.
And no, I have no plans to implement something like this.

OK, thank you very much for your answer. I could try to make a most rudimentary volume script with the help of your videos ..and chat gpt? let's see ..

[nowiamone]

Tiny bugreport for the SL MK3
Seems like the "jumping across pages" issue wasn't only part of the /OSC Script (thanks again for fixing this!), but it appears in the SL MK3, too.

When reaching the Track FX Page via holding the UP Button of the SLMK3, and selecting Track FX,
then, when trying to select Page2, 3, 4, 5, etc. it jumps across those and instead selects the Modulator Page. (Same behavior for Project FX)
This is my page-setup example, and below is how the SL Mk3 handles it:

page setup.jpg

2.jpg

Another minor issue: When the project remotes were selected inside of Bitwig, before trying to reach the Track Remotes (= Track FX) via the SL MK3s up-arrow+TrackFX button, the Track FX button no longer leads to the Track FX, but actually the Project FX! Even when the Project Remotes are not currently selected, but when i switched from selecting the Project remotes to the main device, within Bitwig, for instance. Not very important to me, but just letting you know

[moss]

Tiny bugreport for the SL MK3
Seems like the "jumping across pages" issue wasn't only part of the /OSC Script (thanks again for fixing this!), but it appears in the SL MK3, too.

When reaching the Track FX Page via holding the UP Button of the SLMK3, and selecting Track FX,
then, when trying to select Page2, 3, 4, 5, etc. it jumps across those and instead selects the Modulator Page. (Same behavior for Project FX)
This is my page-setup example, and below is how the SL Mk3 handles it:
page setup.jpg
2.jpg



Another minor issue: When the project remotes were selected inside of Bitwig, before trying to reach the Track Remotes (= Track FX) via the SL MK3s up-arrow+TrackFX button, the Track FX button no longer leads to the Track FX, but actually the Project FX! Even when the Project Remotes are not currently selected, but when i switched from selecting the Project remotes to the main device, within Bitwig, for instance. Not very important to me, but just letting you know

Thanks. Will check.

[mable76]

Hi there,
I am new to Bitwig and just trying to setup my Komplete Kontrol MK2 with DrivenByMoss. As soon as I select it, there is no soft-controller functionality anymore; the coloured indicators are gone. Switching to Bitwig's controller support, they are back and work, but now I cannot use the keyboard anymore, no matter how I change the settings. Even with the DrivenByMoss extension deleted, I cannot use the keyboard anymore which worked fine before. What do I miss? I am on MacOS 12.7.3 and Bitwig 5.1.2

[moss]

Hi there,
I am new to Bitwig and just trying to setup my Komplete Kontrol MK2 with DrivenByMoss. As soon as I select it, there is no soft-controller functionality anymore; the coloured indicators are gone. Switching to Bitwig's controller support, they are back and work, but now I cannot use the keyboard anymore, no matter how I change the settings. Even with the DrivenByMoss extension deleted, I cannot use the keyboard anymore which worked fine before. What do I miss? I am on MacOS 12.7.3 and Bitwig 5.1.2

A bit more info would be helpful. What do you mean by "soft-controller functionality"? What does "I cannot use the keyboard anymore" mean?

[mable76]

From the Bitwig manual (sorry, I just have the German one here), page 359:
"Falls Sie einen unterstützten MIDI-Controller angeschlossen und eingerichtet haben, sehen Sie zusätzliche Farben auf der Device-Oberfläche. Diese farbigen Elemente zeigen uns die aktuellen Soft-Controller- Zuweisungen an. Alle Details dieser Zuweisungen finden Sie im Bereich Device-Zuweisungen, die angezeigt werden, wenn der Remote-Control- Schalter aktiviert ist."
It is about the automatic mapping of the NI Knobs to the remote controls of the selected device. Those are marked in colors then. This automatic mapping is gone with DrivenByMoss used.

If I switch to the native controller support of Bitwig for my keyboard, it still works, but strange enough I cannot send any notes with the keyboard anymore then.

[moss]

From the Bitwig manual (sorry, I just have the German one here), page 359:
"Falls Sie einen unterstützten MIDI-Controller angeschlossen und eingerichtet haben, sehen Sie zusätzliche Farben auf der Device-Oberfläche. Diese farbigen Elemente zeigen uns die aktuellen Soft-Controller- Zuweisungen an. Alle Details dieser Zuweisungen finden Sie im Bereich Device-Zuweisungen, die angezeigt werden, wenn der Remote-Control- Schalter aktiviert ist."
It is about the automatic mapping of the NI Knobs to the remote controls of the selected device. Those are marked in colors then. This automatic mapping is gone with DrivenByMoss used.

If I switch to the native controller support of Bitwig for my keyboard, it still works, but strange enough I cannot send any notes with the keyboard anymore then.

I am not familiar with Bitwig's implementation but check if you have the correct MIDI in-/output ports selected.

[mable76]

I did, but I can't figure it out. Thanks for the speedy replies by the way! Much appreciated.

EDIT: I have just found out that I had accidentally used the (Bitwig) setting for the MK1 before when the keyboard worked. With the MK2 selected (which I have) I cannot get it to function at all. Transport and Soft-Controls work fine here though. Now I use the DrivenByMoss setting for the MK2 and everything works as it should. I only miss the Soft-Controller functionality which is really handy. It would be fantastic to see that in DrivenByMoss, too.

[moss]

I did, but I can't figure it out. Thanks for the speedy replies by the way! Much appreciated.

EDIT: I have just found out that I had accidentally used the (Bitwig) setting for the MK1 before when the keyboard worked. With the MK2 selected (which I have) I cannot get it to function at all. Transport and Soft-Controls work fine here though. Now I use the DrivenByMoss setting for the MK2 and everything works as it should. I only miss the Soft-Controller functionality which is really handy. It would be fantastic to see that in DrivenByMoss, too.

Actually, NI never intended that you can control device parameters with the DAW mode
However, I squeezed them in anyway. Press the CLEAR button to access the device/parameters mode. There is also a Send mode if you press it again. See the DrivenByMoss manual for details.

[mable76]

Actually, NI never intended that you can control device parameters with the DAW mode
However, I squeezed them in anyway. Press the CLEAR button to access the device/parameters mode. There is also a Send mode if you press it again. See the DrivenByMoss manual for details.

Oh... this is exactly what I was looking for! Thank you so much!

[emeelio]

Dear Jürgen,

I am experiencing a bug on Bitwig, launchkey mini MK3. When I set the knobs to either "device" or "custom", the knobs stop working and I cannot switch to a different track by using 'shift'+'arp'/'fixed chord'. Everything should be up-to-date:

Bitwig version: 5.1.2
OS: Windows 10
Firmware LK: 1.1.2, build 425
DBM: 22.2.1

Thanks for any help!

[el davo]

This is primarily to say Thank You! Your Novation LauchControl XL Bitwig script is ace! I was especially thrilled to find working step sequencers.

I only had a quick peek at the code base so far. Would it be possible to create a trigger sequencer mode with *mappable* parameter destinations in Bitwig (rather than "hardcoded" pan etc)? E.g. by sequencing the 8 grid performance dials or similar?

[osaga]

Hi Moss!

Thanks for all the hard work.

Push 2
Mapping device parameters
... is it possible to map the parameter to the button below the dial? And if so, can I choose between
1) Toggle state (on while pushed, off when released)
...or
2) On/Off State - On when pushed and released. Off when pushed and released again.

Thanks!