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

[moss]

Using the extension on XTouch One:
Is it possible to have zeros in the bars/beats segment display like there is when it is displaying time?

Currently the beats readout on the segment display doesn't seem to line up with the labels printed on the XTouch One (img attached).

It would also be useful if I could choose that the Tempo/Ticks button switches between beats and time. Currently it switches between ticks and tempo, but perhaps that's just a personal preference.

The formatting will be fixed in the next update!

[moss]

Hi Moss. Thanks for all your hard work on these controller scripts.

I've got a Push 2 and I'm trying to work out if there's a quicker way to switch between tracks when in the device view. When using Ableton Live, one row of the top buttons selects tracks and the other row of buttons selects devices in the track. With Bitwig (as far as I can tell) I have to navigate up the tree to the mix view, then select a new track, then hit device again.

In short, if I'm trying to jam/perform and switch between tracks quickly to control effects or mute/unmute them etc, it's a bit fiddly and slow.

I thought there might be a shortcut I'm missing to switch tracks but stay in the device view, or perhaps always display the track remotes but be able to switch tracks with one button press. Is there anything I might have missed? I also looked at the user view, but I still can't see how to switch tracks to show the track remotes without going back to mix view, then back to the user view again.

I am afraid not. For a live application I suggest to collect the parameters you need in the project remote controls.

[moss]

DrivenByMoss 26 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 5.3+
• New: Added 'stop is queued' state to the session grid clips. Signal is the same as queued playing.
• Faderfox EC4
  • Fixed: Updated template to make it work with current Faderfox web-interface.
• Generic Flexi
  • Fixed: Parameter #1 reset on 1st instrument did not work.
• MCU
  • Fixed: Improved formatting of bars to align with the text on the hardware.
• Native Instruments Kontrol Mk2
  • New: Loop+Encoder changes Loop start
  • New: The browser presets can be navigated by turning the encoder and confirmed by pressing the encoder.
• Native Instruments Kontrol Mk3
  • New: Added support for NHIA protocol v4:
    • Support for the Shift-Button
      • Slow change of values when using knobs in combination with Shift
      • Zoom in/out with Shift+Encoder
      • Shift+Quantize: switches the options for recording quantize
      • Shift+Auto: toggle clip automation recording
    • Support for native Plug-in mode
    • Support for changing tempo
    • Colored track VUs
    • Added detection of Maschine 3 plugin
    • Loop/Shift+Loop+Encoder changes Loop start/length
    • Mixer modes are now switched by pressing DAW multiple times
    • Added a new layer mode
    • The browser can be used (see the manual for details)
• Push 2/3
  • New: Improved state icons in clip mode.
  • New: Having pressed the Mute/Solo for a longer time does deactivate toggling Mute/Solo on button release.
  • New: Improved lookup on latest macOS.
• XJam
  • New: The knobs are now real relative knobs! Requires Firmware 1.55 and update the template incl. in DrivenByMoss.

Enjoy!

[pc999]

DrivenByMoss 26 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 5.3+
• New: Added 'stop is queued' state to the session grid clips. Signal is the same as queued playing.
• Faderfox EC4
  • Fixed: Updated template to make it work with current Faderfox web-interface.
• Generic Flexi
  • Fixed: Parameter #1 reset on 1st instrument did not work.
• MCU
  • Fixed: Improved formatting of bars to align with the text on the hardware.
• Native Instruments Kontrol Mk2
  • New: Loop+Encoder changes Loop start
  • New: The browser presets can be navigated by turning the encoder and confirmed by pressing the encoder.
• Native Instruments Kontrol Mk3
  • New: Added support for NHIA protocol v4:
    • Support for the Shift-Button
      • Slow change of values when using knobs in combination with Shift
      • Zoom in/out with Shift+Encoder
      • Shift+Quantize: switches the options for recording quantize
      • Shift+Auto: toggle clip automation recording
    • Support for native Plug-in mode
    • Support for changing tempo
    • Colored track VUs
    • Added detection of Maschine 3 plugin
    • Loop/Shift+Loop+Encoder changes Loop start/length
    • Mixer modes are now switched by pressing DAW multiple times
    • Added a new layer mode
    • The browser can be used (see the manual for details)
• Push 2/3
  • New: Improved state icons in clip mode.
  • New: Having pressed the Mute/Solo for a longer time does deactivate toggling Mute/Solo on button release.
  • New: Improved lookup on latest macOS.
• XJam
  • New: The knobs are now real relative knobs! Requires Firmware 1.55 and update the template incl. in DrivenByMoss.

Enjoy!

Cool.

Does the NI stuff works with Linux?

[moss]

DrivenByMoss 26 is online!

...

Enjoy!

Cool.

Does the NI stuff works with Linux?

Yes, since the Mk3 finally has all the logic in the device itself.

[User79]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

What do you mean by "Two variants even appear there"? Please post a screenshot of you settings.

Here is a screenshot of my settings.

[moss]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

What do you mean by "Two variants even appear there"? Please post a screenshot of you settings.

Here is a screenshot of my settings.

That's just the generic driver of Bitwig but not DrivenByMoss. Remove that.
Click on "Add Controller" and select "Ableton" -> "Push 2", which should be actually auto-detected. Since this is not the case I suggest that you put the DrivenByMoss.extension file in the wrong location.

[User79]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

What do you mean by "Two variants even appear there"? Please post a screenshot of you settings.

Here is a screenshot of my settings.

That's just the generic driver of Bitwig but not DrivenByMoss. Remove that.
Click on "Add Controller" and select "Ableton" -> "Push 2", which should be actually auto-detected. Since this is not the case I suggest that you put the DrivenByMoss.extension file in the wrong location.

No ableton in the drop down menu.
It seems that i have put it in the wrong location. i´m on mac. In Bitwig under pref. i can see the location. When i click on it i can open the location in the finder. There i put the drivenbymoss file in.

[User79]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

What do you mean by "Two variants even appear there"? Please post a screenshot of you settings.

Here is a screenshot of my settings.

That's just the generic driver of Bitwig but not DrivenByMoss. Remove that.
Click on "Add Controller" and select "Ableton" -> "Push 2", which should be actually auto-detected. Since this is not the case I suggest that you put the DrivenByMoss.extension file in the wrong location.

No ableton in the drop down menu.
It seems that i have put it in the wrong location. i´m on mac. In Bitwig under pref. i can see the location. When i click on it i can open the location in the finder. There i put the drivenbymoss file in.

Here is a screenshot of my location:

[moss]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

What do you mean by "Two variants even appear there"? Please post a screenshot of you settings.

Here is a screenshot of my settings.

That's just the generic driver of Bitwig but not DrivenByMoss. Remove that.
Click on "Add Controller" and select "Ableton" -> "Push 2", which should be actually auto-detected. Since this is not the case I suggest that you put the DrivenByMoss.extension file in the wrong location.

No ableton in the drop down menu.
It seems that i have put it in the wrong location. i´m on mac. In Bitwig under pref. i can see the location. When i click on it i can open the location in the finder. There i put the drivenbymoss file in.

It needs to be in:
Mac: ~/Documents/Bitwig Studio/Extensions/

[moss]

I obviously did something wrong. I downloaded the latest version for Bitwig DrivenByMoss 25.5.0. Then I copied the corresponding file into the Extension folder. I'm using Mac OSX 15.6. I've now started Bitwig and can find the Push 2 controller in Bitwig under Preferences. Two variants even appear there. I'm opening a new project. Unfortunately, nothing is displayed on the Push display. The display remains dark, as do the buttons. The controller works without any problems in Ableton Live. However, I would like to connect it to Bitwig because I heard about the script. Does anyone know this behavior? Am I doing something wrong?

What do you mean by "Two variants even appear there"? Please post a screenshot of you settings.

Here is a screenshot of my settings.

That's just the generic driver of Bitwig but not DrivenByMoss. Remove that.
Click on "Add Controller" and select "Ableton" -> "Push 2", which should be actually auto-detected. Since this is not the case I suggest that you put the DrivenByMoss.extension file in the wrong location.

No ableton in the drop down menu.
It seems that i have put it in the wrong location. i´m on mac. In Bitwig under pref. i can see the location. When i click on it i can open the location in the finder. There i put the drivenbymoss file in.

Here is a screenshot of my location:

That looks correct. Are you running the latest Bitwig version?

[User79]

I found the error! As Jürgen mentioned, I had selected the wrong save location. On Mac, I had to go to the Bitwig app, click on Show Contents, and was able to find the relevant folder there. Now the extension works, too. Thanks for the help!

[Red_Hector]

I have a strange problem that the DBM Electra One Bitwig preset is causing my ESQ-1 to have sustained notes.
When I adjust certain aux send 6 amounts on the E1 Bitwig Preset, and the ESQ-1 track is selected in Bitwig, sustained notes occur. The ESQ-1 has to be power-cycled to stop the issue.
Only Aux Send 6, on particular audio input channels do this.
When turned, it sends the following type of messages:
BF 40 02
BA 40 02
BF 40 7F
BA 40 7F
BF 40 7E
BA 40 7E

The ESQ-1, which is set to channel 11, is somehow interpreting them as sustain on messages. At least, this is what an AI search has come up with as the possible issue.

I could change the ESQ-1 channel, but would it then start to react to other E1 Bitwig preset controls being turned?

Is there a way to stop Bitwig forwarding the messages from the E1 DBM Bitwig preset to instrument tracks, without disabling the E1 preset?

[pc999]

Yes, since the Mk3 finally has all the logic in the device itself.

Very nice

[Mantras]

This question can be deleted as I read the manual... Thanks for this script Moss!