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

[moss]

Hi, now that there is Bitwig 5, is there something in the api that allows to do step automation with the sequencer on the Push 2 like with ableton ?
Thanks !

Sorry, no. Write your wish to Bitwig support.

[moss]

Is it possible (BW5) to assign static CC to something to always control the, lets say first 4, remote controllers of the selected device?

So the same CC when selct a new device controls the remote controllers of that newly selected device?

That's exactly what the remote controls are for. There is no need to deal with CC yourself. If your controller is not supported by DrivenByMoss use the Generic Flexi instead.

[moss]

DrivenByMoss 20.1.0 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 5.0+
• Launch Control XL
  • Fixed: Moving drum pad range was broken.
• Launchpad, Push
  • Fixed: Clip Length mode was not always recalled.
• MCU
  • New: Layer mode uses now the first instrument instead of the selected device.
  • Fixed: Device froze when there were no sends and send 2 was selected.
• OSC
  • Fixed: Moving drum pad range was broken.
• SLMkIII
  • Fixed: Set knob layout only when necessary.

Enjoy!

[da10us]

Is it possible (BW5) to assign static CC to something to always control the, lets say first 4, remote controllers of the selected device?

So the same CC when selct a new device controls the remote controllers of that newly selected device?

That's exactly what the remote controls are for. There is no need to deal with CC yourself. If your controller is not supported by DrivenByMoss use the Generic Flexi instead.

So Flex is the way to go. I'm fairly new to this. I don't see anything useful under category/action. Is there some video explaining this?

[ukjim]

Hi Jurgen!
I'm very impressed with your integration of the Novation Remote SL25 MkII with Bitwig. This has made me very happy that I can use my "old" midi controller.
Actually I bought this keyboard about 7 years ago, but for a number of different "life" reasons my music interests were put on hold and I have only recently been able to use it, and also assess different DAW's and wanted to try Bitwig.
Previously I had also set up the MkII with Reaper, which was a little tricky in itself (not DrivenByMoss), but gave me a flavour for what it was capable of as a DAW controller.

Initially I had some problems with installing the DrivenByMoss extension in Bitwig, I had downloaded the 20.0.0 zip (I have Bitwig 4.4.10 on 30-day trial), but when trying to assign the Remote SL MkII it didn't appear in the Settings>Hardware Controllers list? It seemed to be only listing the default BW supported (latest) controllers.

So instead I tried downloading the 19.2.2 zip, overwrote the 20.0.0 DrivenByMoss.bwextension file in the normal Bitwig Studios\Extensions folder, re-started BW and then the SL MkII appeared as a choice and obviously looked right with all the other advanced control settings. It seems to be working as described in your video for the RemoteSLMkII video.

I thought I would mention this in case SLMkII should be in the latest Zip file version, e.g. 20.0.0+?
Unless (being a BW newbie) I misunderstood and the Bitwig 5.0+ section was the wrong section to use for the download?

It looks like you're very busy with lots of new versions appearing in quick succession the last few days, so maybe you take the view that new controllers take priority over the old ones during new beta work!?

Although I believe the Novation MkII's are still a popular and viable keyboard even many years after they were first released.

I also get the impression your DrivenByMoss project is a real labour of love for many years now, and I thank you for your amazing work and enthusiasm.
Jim

[moss]

Is it possible (BW5) to assign static CC to something to always control the, lets say first 4, remote controllers of the selected device?

So the same CC when selct a new device controls the remote controllers of that newly selected device?

That's exactly what the remote controls are for. There is no need to deal with CC yourself. If your controller is not supported by DrivenByMoss use the Generic Flexi instead.

So Flex is the way to go. I'm fairly new to this. I don't see anything useful under category/action. Is there some video explaining this?

[moss]

Hi Jurgen!
I'm very impressed with your integration of the Novation Remote SL25 MkII with Bitwig. This has made me very happy that I can use my "old" midi controller.
Actually I bought this keyboard about 7 years ago, but for a number of different "life" reasons my music interests were put on hold and I have only recently been able to use it, and also assess different DAW's and wanted to try Bitwig.
Previously I had also set up the MkII with Reaper, which was a little tricky in itself (not DrivenByMoss), but gave me a flavour for what it was capable of as a DAW controller.

Initially I had some problems with installing the DrivenByMoss extension in Bitwig, I had downloaded the 20.0.0 zip (I have Bitwig 4.4.10 on 30-day trial), but when trying to assign the Remote SL MkII it didn't appear in the Settings>Hardware Controllers list? It seemed to be only listing the default BW supported (latest) controllers.

So instead I tried downloading the 19.2.2 zip, overwrote the 20.0.0 DrivenByMoss.bwextension file in the normal Bitwig Studios\Extensions folder, re-started BW and then the SL MkII appeared as a choice and obviously looked right with all the other advanced control settings. It seems to be working as described in your video for the RemoteSLMkII video.

I thought I would mention this in case SLMkII should be in the latest Zip file version, e.g. 20.0.0+?
Unless (being a BW newbie) I misunderstood and the Bitwig 5.0+ section was the wrong section to use for the download?

It looks like you're very busy with lots of new versions appearing in quick succession the last few days, so maybe you take the view that new controllers take priority over the old ones during new beta work!?

Although I believe the Novation MkII's are still a popular and viable keyboard even many years after they were first released.

I also get the impression your DrivenByMoss project is a real labour of love for many years now, and I thank you for your amazing work and enthusiasm.
Jim

v20 requires Bitwig 5. Use 19.2.2 for Bitwig 4. Mk II is still supported.

[Rossimatic]

So admittedly I've used your Fire script for a few minutes

[wvshpr]

Quick question… do wireless game controllers work with DbM or USB?

[Rossimatic]

Or just learn to play piano and give up sequencing chords.

[Children of our Stars]

Hi Jürgen,

thank you for your outstanding coding work! I recently moved from Ableton to Bitwig and managed to integrate my launchpad with the DAW flawlessly. I got the latest firmware, downloaded the latest version of drivenbymoss and it got also autodetected. Although my launchkey mini mk3 won't get detected at all. The same here, latest firmware and so on...
When I add it manually, I can get it work as a normal midi keyboard (with the help of your specific midi in/out configurations). But it shows me only the "drum" and "custom" settings for the pads. I cannot enter the session mode. The launchpad on the other hand jumped instantly to session mode per default...

Any ideas how to get it working?

Thanks a lot!
Children of our Stars

[ansolas]

OK, got it.

Thank you very much ! you are awesome !

[ansolas]

Is there somewhare a way to asignt the MIX EDIT AND ARRANGE to the F keys ?
I haven't found a matching 'action' in the settings.
[EDIT]

already mappen to AUX BUS OUTPUTS buttons

[nowiamone]

Hello Jürgen,
i m testing your incredibly awesome OSC script, which works really fine (i will ask bitwig support soon about the "clip playback progress" function, which will be awesome I put some "dummy" midi input there, so i can activate the OSC controller. But although i can use Touch OSC smoothly with OSC adresses, as soon as i try to also use Midi CC, i got a problem, because Bitwig does not seem to send back Midi info!? I can assign my touch OSC controllers via Midi CC to Bitwig controllers like Volume without any problem. BUT, when i move those controllers in Bitwig, they don't send their new position towards Touch OSC.
I m using your "generic - flexi" script, with Loop Midi going in, and another Loop Midi Port going out. Those Loop Midi ports are properly connected to Touch OSC, i know this, since i tested it in Ableton and everything works smoothly there - bidirectional.
Now i realized: this also counts for my Komplete Kontrol S49mk2 Keyboard-Encoders! I can assign and use them via the Keyboard - but when i fiddle around within Bitwigs interface , i dont see any value-change in my KK Display! So this seems like a topic also affecting other midi controllers (i m also using your NI KK S-series script for the Keyboard).
This "no-midi-out-problem" persists, even when i deactivate the OSC script, or use the Touch OSC bridge instead of Loopmidi.
Bitwig 5, Beta v5, 20.1 drivenbymoss script.
Maybe you know what the problem could be? Thank you!

[HvdS]

Guten tag Jürgen,

First of all great work on your script, my Launchpad X works perfect with Bitwig,
really impressive what a functionally you put in there!

But one little question
Is there a way to switch pages instantly, from track 1-8 to 9-16 and back, which just one button press?
Now I have to scroll thru several tracks or use bird eye view.
Ideally is would like to use the left and right arrow in session view to go to next/previous page.
Or is there way I can map this myself?

thanks and keep up the great work!