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

[dankinzelman]

Is it possible to remove certain functions from the controller configuration easily? I am using a Novation 25sl mk II for live performance, and occasionally accidentally delete a track or a device, which is of course not ideal. Unfortunately, the delete button is easy to accidentally activate in the heat of the moment, and if I don't notice right away, the undo function can't be accessed. Actually, I wouldn't mind disabling the entire row of buttons for live performance.

[moss]

Is it possible to remove certain functions from the controller configuration easily? I am using a Novation 25sl mk II for live performance, and occasionally accidentally delete a track or a device, which is of course not ideal. Unfortunately, the delete button is easy to accidentally activate in the heat of the moment, and if I don't notice right away, the undo function can't be accessed. Actually, I wouldn't mind disabling the entire row of buttons for live performance.

Sorry, no.

[dankinzelman]

Ok, thank you in any case, your scripts are amazing!

[thomba]

SOLVED - I could not use the newest version, My mistake


Hey everyone,

I've just had to do a full reinstall of my system and am now in the process of properly setting up Bitwig again—currently running version 5.2.

In the past, I used the DrivenByMoss extension successfully with both my Launchpad Pro and the Native Instruments Komplete Kontrol MK3 keyboard. However, this time around, I'm running into issues.

The extension file is correctly placed in Bitwig’s extension folder, but when I launch the software, the Moss scripts aren't showing up. I have a vague memory that there was a specific setting or tweak needed within Bitwig to get it working, but I can't recall the details.

If anyone has tips or remembers the workaround, I'd really appreciate the help.
Thanks!
Thom

[xtreme sounds]

HI for the Akai force script, can we use switch back and forth to controlling Bitwig versus playing sounds locally on the force? Are they seamlessly integrated to play./control Bitwig and play/control the Force together?

[moss]

HI for the Akai force script, can we use switch back and forth to controlling Bitwig versus playing sounds locally on the force? Are they seamlessly integrated to play./control Bitwig and play/control the Force together?

Yes, you can do this. Here is a video about how to integrate it into Bitwig:

[djfoxtrot]

Hey! Love your scripts, use them all the time.
I'm currently running into an issue with my X-TOUCH - I'm in Hierarchical navigation mode, and have set F1 and F2 to "Enter Group" and "Exit Group" respectively. However, when I actually use those keys, nothing seems to happen. I can't actually seem to enter into the group in any easy way directly from the x-touch. Any help would be much appreciated, thank you!

My specs:
Windows 10, AMD CPU
Behringer X-Touch, Push 2 (both using drivenbymoss scripts)
I've also included a screenshot of the settings I am using.

xtouch error.png

[Hikita3000]

EDIT: PROBABLY SOLVED
---
Solution: The takeover mode was catch, that caused problems.
Now, with Immediate mode OSC works flawlessly.

Hi moss,
Thank you so much for your work. The community of Bitwig users is taking a great profit from your work.

I have a bug-report / question.
I am trying to control device parameters by OSC.
Sometimes the values are accepted, sometimes not. In the console there are no errors occurring. Here in this video you can see what is happening:


At first I try to control parameter 1, this does do nothing. After resetting it, controlling it works.
Although this method is not working for parameters 4, 5 or 7...
Any idea what could be going wrong?
Thank you already for your help!
Hendrik

[moss]

Hey! Love your scripts, use them all the time.
I'm currently running into an issue with my X-TOUCH - I'm in Hierarchical navigation mode, and have set F1 and F2 to "Enter Group" and "Exit Group" respectively. However, when I actually use those keys, nothing seems to happen. I can't actually seem to enter into the group in any easy way directly from the x-touch. Any help would be much appreciated, thank you!

These actions are Bitwig actions which are executed inside of the DAW and often depending on the window focus.
Instead, to enter a group:
1. Select the group with the select button
2. Press the Select button again to enter it
To leave a group:
Long press any of the Select buttons.

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

[nowiamone]

Hello, first of all I would like to congratulate you and thank you for this driver, which allows me to use OSC and Bitwig with my 24 inch touch screen.
I have a question. I want to use the fx selector plug-in.
Is there a way to change the active layer set with an OSC command?, like a programchange under OSC? Thank you.
(I use Bitwig 5.2 and OSC 1.29)

Being able to choose layers via OSC commands rather than programchange would be really nice
I'd need this to simplify and refine my Instrument Selector built in Touch OSC,
Dear Jürgen, please consider integrating this

What's working right now is:
/device/layer/{1-8}/activated
-setting the "activated" status of instruments in the selector [which is the on/off switch for device activation, unloading the instrument out of the RAM]
/device/layer/{1-8}/selected
- setting the "selected" status of instruments in the selector [which represents the current cursor position within the instrument selector, not particularily useful for live-jamming]

what's missing is
/device/layer/{1-8}/active
- setting the "active" status of instruments in the selector [which represents the currently loaded/playable instrument of the selector = the actual choice of the instrument]

Another thing which i want to ask you: Is there any chance to change the "Looping on/off" state of clips via the OSC Script? Would be really really awesome. Because sadly, Bitwig doesn't even offer a shortcut for this important function. So a OSC command would be really handy to enable/disable one-shot mode for specific clips when doing recordings/playbacks in the Launcher.

looping.jpg

Likewise interesting would be, whether OSC commands to control the on/off state of the next actions of Clips would be possible

next actions.jpg

[dankinzelman]

I have a Launchpad X and I'm trying to use Drum64 to play my drum machine. I can play OK, but the pad lighting is not aligned with where I've loaded the samples. The pads with loaded samples are illuminating yellow (although they light green and work fine to play the loaded samples). The white-illuminated pads have no samples and don't play anything. Any suggestions of how I can refresh the display of the active pads?

[flavor8]

Hello, thank you for the work on this!

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

[Bobby L'Avenir]

Hi Moss, is it possible to lock the shift button to do fine control on the 8 rotary knobs without two hands being needed to hold the shift button down? Many thanks

[WILLPOWER]

Hi, so I successfully installed it for BITWIG STUDIO 5.3.8 on Ubuntu 22.04 but once I selected open source control in Controllers, I do not have the option for: input - internal midi. it just says none. how can I have the option to add the port number ? I see that you use LoopBe1. Is there one you recommend for linux ? Thank you !