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

[moss]

I got another idea/question:
Would it be possible for you to create /OSC commands for us to directly control the creation of notes? Like /clip/create/[length in beats], but /note/create/60/[length in beats], for instance, to create a Middle-C , with a certain length into the currently selected clip (beginning at the beginning of the clip)?

This would be awesome for direct chord-creation-tools, i'd like to build. Currently i'm building a visual Circle of Fifths / Quintenzirkel inside Touch OSC, which, thanks to your OSC Script, is able to send the chord notes via /vkb_midi/. But obviously the chords then have to be recorded manually into Bitwig, which could get much more convenient/automated, if there was an option to create notes directly.

Noted. But not sure if this will ever happen.

[moss]

Hey,

Bitwig 5.3.9 Mac M1 Moss 25.1.1 When simuating a push 2 and clicking on show GUI Bitwig completely crashes

Kr,

Wim

Hi Wim,
yes, known bug on Bitwigs side. Please complain as well, so far, they see it as not that important to fix it.

[torstenanders]

This is my first post here: thanks a lot for all the substantial developing efforts that went into DrivenByMoss!

I likely miss something obvious, but it appears I cannot install DrivenByMoss for Bitwig. I want to use DrivenByMoss with Faderfox EC4.

I copied DrivenByMoss.bwextension into ~/Documents/Bitwig Studio/Extension and started Bitwig (after various unsuccessful attempts I also tried restarting the OS, just in case). After doing so, I would expect that the controllers provided by DrivenByMoss would be listed when I try Add Controller, but seemingly this is not the case (see screenshot 2 -- apologies for the wrong order). Is this expected?

Beyond this, I also tried the seemingly preconfigured Faderfox EC4 controller, but that only resulting in a Generic controller (see screenshot 1). Again, is this expected? It clearly looks different than the interface shared in the relevant YouTube video. For example, the I/O is not bidirectional.

For completeness: I had the Faderfox controller updated to version 2.0 earlier, but I tried to also add the special DrivenByMoss customisation to it. Within the EC4, I entered Setup 15 (Setup 1 is already used for something else) + Group 1, then pressed [Func] and Setup to instruct the controller to receive. I then sent EC4_DrivenByMoss_Setup.syx to it (using SysEx Librarian), which seemingly worked, because afterwards under the EC4 Setup 15, the Group 1 was now called DBM.

Again, I assume I am missing something obvious here. Any help?

System: DrivenByMoss 25.1.1, Bitwig 5.2.7, MacOS 14.7 (M1 MBP)

[torstenanders]

Update: Just realised that the required version for DrivenByMoss 25.1.1 is Bitwig 5.3+. So, I downgraded to DrivenByMoss-25.0.1, and now Bitwig can seemingly load DrivenByMoss.

Thanks again for your work!

[thomba]

Arturia Launckeys MK3 are now offering the opportunity to control the Komplete Kontrol mappings with a new custom mode for download. This function is not available in your DrivenByMoss solution? Right?

By the way: Many thanks for your fantastic solution you are providing to the community.

[moss]

Arturia Launckeys MK3 are now offering the opportunity to control the Komplete Kontrol mappings with a new custom mode for download. This function is not available in your DrivenByMoss solution? Right?

Correct.

[thomba]

Thanks

[Sekops]

Hi Moss,

Im seeing something unexpected regarding recording automation and wanted to ask. Perhaps I'm not understanding how Bitwig or the script should be working...

From the Bitwig 5.3 manual:

› Latch mode begins recording automation values as soon as you begin changing parameters. Recording then continues until the transport is stopped.

› Touch mode also waits until you have begun changing parameters to begin recording automation values, but once you stop interacting with a parameter, recording is halted and any preexisting values are preserved.

When Arranger Write Automation is Enabled, with DrivenByMoss-25.1.1-Bitwig on Mac OS 15.5 and a Push 2.

When "Stop automation recording on knob release" is "On" in settings:

Latch Mode: Records automation fine when moving the pot on the Push 2, however as soon as I release the pot, Write Automation is disabled. Shouldn't it remain on? Otherwise it behaves the same as Touch mode? Recording does not continue until the transport is stopped.

Touch Mode: Records automation fine when moving the pot on the Push 2, when I release the pot, Write Automation is disabled as expected from what the Bitwig manual describes.

When "Stop automation recording on knob release" is "Off" in settings:

Latch Mode: Records automation fine when moving the pot on the Push 2, when I release the pot, Write Automation remains enabled as expected from what the Bitwig manual describes.

Touch Mode: Records automation fine when moving the pot on the Push 2, when I release the pot, Write Automation remains enabled. Shouldn't it get turned off? Otherwise it behaves the same as Latch mode? Recording is not halted and any preexisting values are overwritten.

From what I'm seeing Latch mode and Touch mode behave the same for any given state of "Stop automation recording on knob release".

I'm not understanding what the purpose of the "Stop automation recording on knob release" setting is for. Isn't that defined by Latch & Touch modes instead?

[moss]

Hi Moss,

Im seeing something unexpected regarding recording automation and wanted to ask. Perhaps I'm not understanding how Bitwig or the script should be working...

From the Bitwig 5.3 manual:

› Latch mode begins recording automation values as soon as you begin changing parameters. Recording then continues until the transport is stopped.

› Touch mode also waits until you have begun changing parameters to begin recording automation values, but once you stop interacting with a parameter, recording is halted and any preexisting values are preserved.

When Arranger Write Automation is Enabled, with DrivenByMoss-25.1.1-Bitwig on Mac OS 15.5 and a Push 2.

When "Stop automation recording on knob release" is "On" in settings:

Latch Mode: Records automation fine when moving the pot on the Push 2, however as soon as I release the pot, Write Automation is disabled. Shouldn't it remain on? Otherwise it behaves the same as Touch mode? Recording does not continue until the transport is stopped.

Touch Mode: Records automation fine when moving the pot on the Push 2, when I release the pot, Write Automation is disabled as expected from what the Bitwig manual describes.

When "Stop automation recording on knob release" is "Off" in settings:

Latch Mode: Records automation fine when moving the pot on the Push 2, when I release the pot, Write Automation remains enabled as expected from what the Bitwig manual describes.

Touch Mode: Records automation fine when moving the pot on the Push 2, when I release the pot, Write Automation remains enabled. Shouldn't it get turned off? Otherwise it behaves the same as Latch mode? Recording is not halted and any preexisting values are overwritten.

From what I'm seeing Latch mode and Touch mode behave the same for any given state of "Stop automation recording on knob release".

I'm not understanding what the purpose of the "Stop automation recording on knob release" setting is for. Isn't that defined by Latch & Touch modes instead?

Sounds correct to me. The meaning of the option is when it is enabled: when you release the knob (= it is no longer touched) automation is turned off automatically. It makes mainly sense for WRITE automation, so you do not need to stop playback. It is pointless for TOUCH mode since this behaves already similar.

[Sekops]

Great, thanks for the clarity, you're right it makes sense for Write and not so much for Touch. Cheers

[flavor8]

>> Question: how do I avoid the record button turning being activated on the tracks when I adjust the faders on the XTouch? I think that's causing some automation to be recorded, which is then in turn causing my loop to incorporate volume changes (although, I don't see any in the automation lanes).

> Please explain in more detail what you are doing.

I am running loops in Bitwig while adjusting the volume of each track using the faders. Whenever I adjust a fader, it turns "rec" on for that track, and seemingly it captures volume adjustment automations, because I start to encounter resistance / fader movements the longer that the loops continue to play. Like I say, I don't see these automations in the Bitwig UI, but something seems to be recorded somewhere.

[moss]

>> Question: how do I avoid the record button turning being activated on the tracks when I adjust the faders on the XTouch? I think that's causing some automation to be recorded, which is then in turn causing my loop to incorporate volume changes (although, I don't see any in the automation lanes).

> Please explain in more detail what you are doing.

I am running loops in Bitwig while adjusting the volume of each track using the faders. Whenever I adjust a fader, it turns "rec" on for that track, and seemingly it captures volume adjustment automations, because I start to encounter resistance / fader movements the longer that the loops continue to play. Like I say, I don't see these automations in the Bitwig UI, but something seems to be recorded somewhere.

In the Bitwig settings you can deactivate: Settings -> Recording -> Auto-arm
In the DrivenByMoss settings you can deactivate: "Workflow: Select channel on fader touch".

[Techlo]

Hi, since updating to the latest controller script and Bitwig 5.38, my S61 mk2 randomly fires the Stop button, usually within the first couple of bars. It doesn't matter what device/keyboard/mouse starts the playback, the S61 mk2 fires off a Stop almost right away. Turning off the controller stops this stopping behavior, so it's definitely originating there. When using the standard "Controllers" script instead the issue goes away. I also use a Maschine Jam and Push 2 and they function properly with the script. This doesn't happen in Reaper or Maschine 2.

Sorry, haven't heard of such an issue so far and I cannot reproduce it.

j

Thank you, turns out it wasn't a script problem, it's entirely a Bitwig problem I'm having as it occurs with no controllers or Qwerty keyboard connected.

[teknoman]

Hi,

Has there been any consideration for adding the Ableton Move to the list of supported controllers? I haven't seen much discussion about it here, but it is an excellent piece of hardware that should fit nicely into the BW workflow. I have a unit to loan if needed. Thanks!

[moss]

Hi,

Has there been any consideration for adding the Ableton Move to the list of supported controllers? I haven't seen much discussion about it here, but it is an excellent piece of hardware that should fit nicely into the BW workflow. I have a unit to loan if needed. Thanks!

I have no plans for this.