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

[ruralaudio]

Hi! I was testing out the DrivenByMoss extension in Bitwig 6 on Linux (CachyOS) for my Akai Force.

I found something about the script working on Linux, but following the manuals and video guide, I only see examples using the Network Midi Driver and not the USB connection.

I can easily find three midi inputs using the USB and Computer Mode on the Force, but can't seem to make it work with the script. The controls are off and I get a MIDI Output error after a little while. I only get this MIDI Output error when using the DrivenByMoss script and not the build in Bitwig scripts (which doesn't seem to send any information).

Any forum post or resources I can look at to see if I can make this work?

[moss]

Hi! I was testing out the DrivenByMoss extension in Bitwig 6 on Linux (CachyOS) for my Akai Force.

I found something about the script working on Linux, but following the manuals and video guide, I only see examples using the Network Midi Driver and not the USB connection.

I can easily find three midi inputs using the USB and Computer Mode on the Force, but can't seem to make it work with the script. The controls are off and I get a MIDI Output error after a little while. I only get this MIDI Output error when using the DrivenByMoss script and not the build in Bitwig scripts (which doesn't seem to send any information).

Any forum post or resources I can look at to see if I can make this work?

Sadly, it does not work without the Akai network driver.

[maxravedj]

How does Flexi's "Browser: Scroll presets" slot function work? What midi events it expect? Note, CC events do nothing. Also "Browser: select the next tab" does nothing at all.

[ruralaudio]

Sadly, it does not work without the Akai network driver.

Thanks for clarifying, it's all good and thanks for all your hard work!

Let me know if there is anything I can do, to see if it could be relevant to work on later.

[kaveer]

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.

Your solution solved this issue completely, which I've had for years. I tried to make it hiccup, but couldn't.
Thank you for that. This is a great deal for many who use Push2 in Bitwig with your script.
Amazing work!

Just 2 small ideas, if you don't mind.
The currently selected Device Page's name could have a darker background with the already white font — it would help avoid searching for what's selected.

Also On the Device Page, maybe the font of each Control's title could be a little smaller and/or display across 2 lines, to accommodate more characters — which in my experience often seems necessary. I know Bitwig won't show all characters, but perhaps the Push 2 has enough screen space for that?

Many thanks!

[moss]

How does Flexi's "Browser: Scroll presets" slot function work? What midi events it expect? Note, CC events do nothing. Also "Browser: select the next tab" does nothing at all.

It is not intended for buttons. Use a knob to scroll with this function.

[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.

Your solution solved this issue completely, which I've had for years. I tried to make it hiccup, but couldn't.
Thank you for that. This is a great deal for many who use Push2 in Bitwig with your script.
Amazing work!

Just 2 small ideas, if you don't mind.
The currently selected Device Page's name could have a darker background with the already white font — it would help avoid searching for what's selected.

Also On the Device Page, maybe the font of each Control's title could be a little smaller and/or display across 2 lines, to accommodate more characters — which in my experience often seems necessary. I know Bitwig won't show all characters, but perhaps the Push 2 has enough screen space for that?

Many thanks!

Great to hear. Ideas are noted.

[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!!

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

Hello Jurgen thanks as alwyas for your reply!!
Yes there is a clip selected.
What happens is that is not possible to make the Sequencer play as a STANDALONE, it just doesn't make any sound.
If I program a sequence it happens that the sequence is DIRECTLY written in the clip WITHOUT using the "Print to clip" option. When I play the clip in Bitwig I toggle between all of the sequencer modes and they just "mirror" the clip notes, showing what's inside the clip.
But the sequencer itself as a Standalone doens't play. In resume the sequencer is not able to play its own sequences. Through the sequencer pads I just can write notes in a clip.

[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?

Hello Jurgen thanks as alwyas for your reply!!
Yes there is a clip selected.
What happens is that is not possible to make the Sequencer play as a STANDALONE, it just doesn't make any sound.
If I program a sequence it happens that the sequence is DIRECTLY written in the clip WITHOUT using the "Print to clip" option. When I play the clip in Bitwig I toggle between all of the sequencer modes and they just "mirror" the clip notes, showing what's inside the clip.
But the sequencer itself as a Standalone doens't play. In resume the sequencer is not able to play its own sequences. Through the sequencer pads I just can write notes in a clip.

Ah, I see. You cannot use the on-board hardware sequencer with DrivenByMoss (since I use the developer mode of the Launchpad). If you want to use the Launchpads sequencer instead connect it as a plain MIDI device.

[olimpo]

Hello, no no forget about "standalone" it is not what I meant it is bad writing. What I mean is that the PLAY button does not reproduce the sequence that is programmed in the launchpad itself.

[ffx]

New NI Kontrol MK3 beta firmware supports 16/32 bit resolution for velocity/parameters... Will this work with this extension OOTB?

[banermattou]

Hi Moss,
I am trying Bitwig 6 (I am currently in 4) to see if I should upgrade. I am using my push1 with your script and it is a delight to use.
However, I’ve run into an issue with the new Bitwig 6 browser. I rely heavily on Collections to stay organized, but with the new version of your script, I can’t seem to navigate them, they appear permanently collapsed.
Is there a specific way to expand these via the controller now, or is this a limitation introduced by the new API changes? Thanks for all your hard work!

[moss]

Hello, no no forget about "standalone" it is not what I meant it is bad writing. What I mean is that the PLAY button does not reproduce the sequence that is programmed in the launchpad itself.

You cannot use the Hardware sequencer of the Launchpad in combination with DrivenByMoss.

[moss]

Hi Moss,
I am trying Bitwig 6 (I am currently in 4) to see if I should upgrade. I am using my push1 with your script and it is a delight to use.
However, I’ve run into an issue with the new Bitwig 6 browser. I rely heavily on Collections to stay organized, but with the new version of your script, I can’t seem to navigate them, they appear permanently collapsed.
Is there a specific way to expand these via the controller now, or is this a limitation introduced by the new API changes? Thanks for all your hard work!

Sadly, the API is still not adapted to the new browser and the old API is only a bit "reconnected" to make it work. Write to Bitwig, the more the better, ...

[banermattou]

All right, thank you for the answer. That is sad indeed, as they have made a lot of great additions since I last upgraded. However, this is the second time I've tried a newer version, and browsing Collections on the Push is such a basic part of my workflow that upgrading just isn't worth it for me. I’ll write to them, hopefully, it will help bring this matter to their attention.