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

Post Reply New Topic
RELATED
PRODUCTS
Bitwig Studio 6$399.00Buy Maschine

Post

Hey Moss,
I have an idea, but probably a little far-fetched... For Ableton there is the nanoKontrol Arsenal extension which lets you chose from a lot of different additional modes for the clip matrix. In the case of the Push 2 this is done by leaving the standard functionality as is while adding a lot of optional functionality to the user mode, see https://nativekontrol.com/arsenal-ps2.

I find split modes quite interesting, for example I never use more than two clips on a track, so I always want to access the clips of more than 8 tracks on my clip matrix.

So what about adding a kind of "virtual controller" to DrivenByMoss that sends and interprets MIDI messages in a standardised way across all your extensions for clip launchers? Then adding another MIDI out to send these messages while in user mode. There should be a MIDI channel that is not used by any of these controllers? With a virtual MIDI loopback cable we could receive these messages in our own scripts and then send statuses back to the virtual controller. This would allow me to adapt my custom script and use it with the user mode of a Push 2 for example, while still having all the functions you implemented. Or we could use Generic Flexi for it. This could be a fantastic user mode for all the individual ideas that don't really fit into DrivenByMoss.

Wünsche nen guten Rutsch ins neue Jahr!

Post

oyrgawd wrote: Wed Dec 30, 2020 10:43 pm Apologies if this has been covered elsewhere, but I'm not sure how to search it --

With Ableton (on Mac, Catalina), my Push 2 holds its state and control of Live regardless of the active application. Like, I can switch over to VS Code or anything else, and Push looks the same, and is immediately responsive if I hit the Play button, etc.

With Bitwig, when I switch the active application, after a few seconds, the Push pads and screen go out, and the buttons are not immediately responsive, like it takes a second to 'wake up.'

This might be a Bitwig thing vs. a (wonderful and very appreciated) Moss script thing. Maybe there's a way in MacOS to dedicate a thread? Maybe other controllers behave differently? It kind of tilts me toward using Live, because I like to be able to reach out and goof with a loop while doing real work during the day.
I tested a bit (on Big Sur) but cannot reproduce that. However, there are several squirks with Macos, I am aware of an issue with LEDs not updating when switching modes. I reported it to Bitwig, please do with you issue as well.

Post

TVbene wrote: Thu Dec 31, 2020 10:23 am I have an idea, but probably a little far-fetched... For Ableton there is the nanoKontrol Arsenal extension which lets you chose from a lot of different additional modes for the clip matrix. In the case of the Push 2 this is done by leaving the standard functionality as is while adding a lot of optional functionality to the user mode, see https://nativekontrol.com/arsenal-ps2.
Hi,
intertesting ideas in there but I do not want to go in the fully configurable direction.
Cheers!

Post

Having a weird display issue with Push 1 using DrivenByMoss-10.9.6-Bitwig. Cant seem to find the setting that is causing it, but goes away when disabling the controller.

[attachment=0]Push 1_weird.PNG[/attachment]
You do not have the required permissions to view the files attached to this post.

Post

Great work on all this, moss!

Just got a Beatstep Pro and saw it's no longer supported due to some bugs I believe. Any recommendations / tips to get it set up w/ Bitwig so I can utilize all 3 sequencers on separate tracks? Have it connected as a generic midi keyboard, but can't seem to trigger separate Bitwig tracks with the separate beatstep tracks (IE: BW drum machine on drum, BW sampler on sequencer 1, BW sampler on sequence 2)

Cheers, and happy new year!

Post

guitarfrenzi wrote: Thu Dec 31, 2020 10:42 pm Having a weird display issue with Push 1 using DrivenByMoss-10.9.6-Bitwig. Cant seem to find the setting that is causing it, but goes away when disabling the controller.
Can't see anything weird on the screenshot. What is your display issue?

Post

dirtydenver wrote: Thu Dec 31, 2020 11:22 pm Great work on all this, moss!

Just got a Beatstep Pro and saw it's no longer supported due to some bugs I believe. Any recommendations / tips to get it set up w/ Bitwig so I can utilize all 3 sequencers on separate tracks? Have it connected as a generic midi keyboard, but can't seem to trigger separate Bitwig tracks with the separate beatstep tracks (IE: BW drum machine on drum, BW sampler on sequencer 1, BW sampler on sequence 2)

Cheers, and happy new year!
Create 3 tracks. In the channel settings set the MIDI channels accordingly:

1) Drum track: 10 -> Same
2) Seq 1: 1 -> Same
3) Seq 2: 2 -> Same

If a device require MIDI channel 1, do e.g. 10->1
BeatstepProSetup.png
If you want control tracks and devices too, use the Generic Flexi to map the knobs in device mode.
You do not have the required permissions to view the files attached to this post.

Post

[quote=moss post_id=7990325 time=1609496679 user_id=25218]
[quote=guitarfrenzi post_id=7990052 time=1609454535 user_id=290262]
Having a weird display issue with Push 1 using DrivenByMoss-10.9.6-Bitwig. Cant seem to find the setting that is causing it, but goes away when disabling the controller.
[/quote]

Can't see anything weird on the screenshot. What is your display issue?
[/quote]


A swathe of the clips have borders around them and a white square on the clip it'self. Disappears when the Push 1 is disabled.

Post

guitarfrenzi wrote: Fri Jan 01, 2021 11:23 am
moss wrote: Fri Jan 01, 2021 10:24 am
guitarfrenzi wrote: Thu Dec 31, 2020 10:42 pm Having a weird display issue with Push 1 using DrivenByMoss-10.9.6-Bitwig. Cant seem to find the setting that is causing it, but goes away when disabling the controller.
Can't see anything weird on the screenshot. What is your display issue?

A swathe of the clips have borders around them and a white square on the clip it'self. Disappears when the Push 1 is disabled.
Ah. That is actually a feature. :-)

The clips with the borders are the ones which are currently available on the pads in the session view. The highlighted one is the cursor clip.

Post

moss wrote: Fri Jan 01, 2021 11:37 am
guitarfrenzi wrote: Fri Jan 01, 2021 11:23 am
moss wrote: Fri Jan 01, 2021 10:24 am
guitarfrenzi wrote: Thu Dec 31, 2020 10:42 pm Having a weird display issue with Push 1 using DrivenByMoss-10.9.6-Bitwig. Cant seem to find the setting that is causing it, but goes away when disabling the controller.
Can't see anything weird on the screenshot. What is your display issue?

A swathe of the clips have borders around them and a white square on the clip it'self. Disappears when the Push 1 is disabled.
Ah. That is actually a feature. :-)

The clips with the borders are the ones which are currently available on the pads in the session view. The highlighted one is the cursor clip.
wowzers, is there a way to banish that curious feature :)

Post

I finally checked Open Stage Control out, since I believe that Lemur is not future proof.

Using the Bitwig Template by Moss I can toggle the buttons, all the track names display correctly, but I can not use the faders at all. Any ideas?

Post

wvshpr wrote: Fri Jan 01, 2021 10:46 pm I finally checked Open Stage Control out, since I believe that Lemur is not future proof.

Using the Bitwig Template by Moss I can toggle the buttons, all the track names display correctly, but I can not use the faders at all. Any ideas?
Some more info would helpful:
- What is your OS? Which version of Open Stage Control are you using?
- Did you check if the fader commands are sent by OSC? Are they received in Bitwig (turn on logging in the settings)?
- Did you change any of the settings? The template uses the lowest resolution (128).

Post

I have a question, and forgive me if it's been asked and answered before.
Can I use 2 different scrips at the same time in Bitwig.
I'm currently using the MOSS script for my NI S88MKII, and I would like to add tablet functionality using OSC.
I'm just wondering if there would be any strange conflicts.
Thanks so very much!

Post

pranaearth wrote: Sun Jan 03, 2021 1:46 am I have a question, and forgive me if it's been asked and answered before.
Can I use 2 different scrips at the same time in Bitwig.
I'm currently using the MOSS script for my NI S88MKII, and I would like to add tablet functionality using OSC.
I'm just wondering if there would be any strange conflicts.
Thanks so very much!
Yes, that works fine. I am running 9 at the same time :-)

I did a video about it some time ago:

Post

Hi Moss,

I'm using your script with the Launchpad X. Is there any way to stop individual clips from playing while in session mode?

I used to use Maschine Jam and you could play/stop any clip by pressing the same pad which made live playing very fast.

Anyway you could have that on the Launchpad? Press to play and press again to stop?

Thanks
Fender Studio Pro 8.1 Mac OS Tahoe 26.5

Post Reply

Return to “Controller Scripting”