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

[moss]

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.

[moss]

Being ab le 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]

It is not an option of the layer but a parameter of the instrument selector device. What you can do is to map it to the e.g. 1st parameter of a remote control page and then use the set parameter value command to change it.

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

Sadly, both currently not available via the API.

[moss]

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?

I could not reproduce the issue but I had sometime issues when loading samples from the browser. You can try to switch between tracks or turn the drum device off and on again.

[moss]

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

Please explain in more detail what you are doing.

[moss]

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

Sorry, no. But you could decrease the normal speed in the settings.

[moss]

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 !

I am not too much of a Linux expert but I asked ChatGPT and it showed several possibilities via ALSA, PipeWire, or JACK

[Invisble Man]

Hi Moss,
Your flexi script is the only way for me to configure my MP Midi controller to create a virtual mixer, with synced faders. (with midi learn it's not possible, if I move a parameter with the mouse, it's not visually synced on my controller).
But with the flexi script we can only have 8 tracks (volume, pan...). Is there a way to have 16 tracks or more ?

[moss]

Hi Moss,
Your flexi script is the only way for me to configure my MP Midi controller to create a virtual mixer, with synced faders. (with midi learn it's not possible, if I move a parameter with the mouse, it's not visually synced on my controller).
But with the flexi script we can only have 8 tracks (volume, pan...). Is there a way to have 16 tracks or more ?

Sorry, no.

[xiehniog]

Hi, first of all thank you for all the work you're putting in, Jürgen, it's very appreciated. I have a couple of questions that I couldn't find how to do in the docs or videos.
I have an APCMini, is there a way of setting the behaviour so that the clips and/or scenes are queued and triggered when the current one finishes playing? I can only seem to trigger them instantly.
And a bug (or at least on my system a malfunction) is that if I add more than 8 regions, the APCMini freezes, and the scenes buttons become flickery.
Thank you

[moss]

Hi, first of all thank you for all the work you're putting in, Jürgen, it's very appreciated. I have a couple of questions that I couldn't find how to do in the docs or videos.
I have an APCMini, is there a way of setting the behaviour so that the clips and/or scenes are queued and triggered when the current one finishes playing? I can only seem to trigger them instantly.
And a bug (or at least on my system a malfunction) is that if I add more than 8 regions, the APCMini freezes, and the scenes buttons become flickery.
Thank you

Are you talking about the Reaper version?

[xiehniog]

Are you talking about the Reaper version?

Yes, sorry. Reaper 7

[moss]

I have an APCMini, is there a way of setting the behaviour so that the clips and/or scenes are queued and triggered when the current one finishes playing? I can only seem to trigger them instantly.

See "smooth seek" in the DrivenByMoss manual under:
Known Issues -> Cockos Reaper -> Workarounds -> Scenes

And a bug (or at least on my system a malfunction) is that if I add more than 8 regions, the APCMini freezes, and the scenes buttons become flickery.
Thank you

I cannot reproduce this but I know that the APCmini is a problematic device and I had random freezes with it in different areas.

[xiehniog]

the APCmini is a problematic device and I had random freezes with it in different areas.

I'll try the Smooth Seek workaround. What controller would you recommend for live recording/ looping on reaper with transport control and clips/scene triggering? It's about time I upgrade from the APCMini. Thanks

[nowiamone]

Being ab le 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]

It is not an option of the layer but a parameter of the instrument selector device. What you can do is to map it to the e.g. 1st parameter of a remote control page and then use the set parameter value command to change it.

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

Sadly, both currently not available via the API.

Thanks alot for the clarification.

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.

quintenzirkel.jpg

[wimvandenborre]

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