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

[Skelmy]

Hey Moss,

Love you work with Bitwig scripts by the way.

Just wondering if you've had a chance to test the new Novation SL MK2 with Bitwig 5 and Automap? As that should be the same as the ZeRo SL MK2? Just a thought.

Thanks Moss

Automap is a dead product and up to my knowledge does not even run on latest OSs anymore.

It's always worked fine on Windows 10 and still does, works fine with Reason 10 and Cubase 10 still, works fine with the last Bitwig 4 version and pass Driven by Moss extension script for Novation SL MK 2.
SL MK 1 and 2 both use Automap Server or they're pretty useless.

Are you dropping the SL MK 1 and 2 scripts in Bitwig 5? That would be such a shame.

These devices work totally fine without Automap.

They do, but how come it works with Automap in the last version 4 of Bitwig and the last version of Driven by Moss?
Be great if the Automap function worked with the latest Bitwig, real shame that it isn't, seeing as Automap works fine with Reason 10 and Cubase 10.

There is absolutely no need to use Automap with Bitwig. Everything that Automap does can be done directly in Bitwig.

Yes maybe so, but sitting down and mapping out every plugin and instrument as a Bitwig map that I can only use in Bitwig would take months on end, and the point of Automap is you can use the maps in any DAW, I have so many I have saved and rearranged as far back as I've had the ZeRo SL MK 2 at that's a lot, on a new install I just load up my maps as I'm going and set them as default and very on, now I can't with Bitwig which is such a shame.

Because of this situation I looked at the MPMIDI Model 2A, as that works with it's own plugin wrapper, but it's €780 and I just don't have that to spend on replacing a controller at the moment.

Be good if the Automap did work with Bitwig 5 though, is it because they changed something to do with how controllers work with Bitwig now?

[moss]

Yes maybe so, but sitting down and mapping out every plugin and instrument as a Bitwig map that I can only use in Bitwig would take months on end, and the point of Automap is you can use the maps in any DAW, I have so many I have saved and rearranged as far back as I've had the ZeRo SL MK 2 at that's a lot, on a new install I just load up my maps as I'm going and set them as default and very on, now I can't with Bitwig which is such a shame.

Because of this situation I looked at the MPMIDI Model 2A, as that works with it's own plugin wrapper, but it's €780 and I just don't have that to spend on replacing a controller at the moment.

Be good if the Automap did work with Bitwig 5 though, is it because they changed something to do with how controllers work with Bitwig now?

I am not aware of any such change. You can check back with Bitwig support.
One thing to check might be the plugin isolation setting.

[nowiamone]

Hello, Just a quick report
OSC/Generic Flexi Scripts not working in Bitwig 5.0.2 with drivenbymoss 20.3.1 on Windows 11 22H2

1.jpg

5.0.1 working fine, without above error-messages.

[moss]

Hello, Just a quick report
OSC/Generic Flexi Scripts not working in Bitwig 5.0.2 with drivenbymoss 20.3.1 on Windows 11 22H2
1.jpg
5.0.1 working fine, without above error-messages.

Workaround will be available later today...

[moss]

Here is a little bugfix release 20.3.2:

• All devices
  • Fixed: Workaround for an incompatibility with Bitwig 5.0.2.
• Generic Flexi
  • Fixed: Crash on startup when keyboard MIDI channel was set to Off.

Get it from https://mossgrabers.de

Enjoy!

[nowiamone]

Here is a little bugfix release 20.3.2:

• All devices
  • Fixed: Workaround for an incompatibility with Bitwig 5.0.2.
• Generic Flexi
  • Fixed: Crash on startup when keyboard MIDI channel was set to Off.

Get it from <span class="skimlinks-unlinked">https://mossgrabers.de</span>

Enjoy!

[nowiamone]

ha, this is funny, it seems like Bitwig fixed it too now. Double-fix!
Changes in Bitwig Studio 5.0.3 [released 21 July 2023]
FIXES

• Fixed a crash for controller scripts that make various assumptions about how keyboard shortcuts are categorized (such as the DrivenbyMoss Flexi script)

Edit: 20.3.2 seems to be working together with 5.0.3

[teknoman]

Hi Moss,

I have a feature request for Generic Flexi and perhaps other scripts as an option (I looked and didn't see it so I'm posting here). I was messing with tons of Max4Live customizations in Ableton and one of the cool devices was a way to control the last touched or active parameter (info here - https://elisabethhomeland.gumroad.com/l ... ut=profile). You map any knob/fader/button/etc on your hardware controller to the M4L device and then that knob will always adjust the last touched control in Ableton.

In BW this could work as follows - option in Generic Flexi under 'Selected Slot - Function' for 'Adjust Last Parameter', then we simply assign a knob to it. I'm not sure if the BW Controller API will allow this directly, but perhaps there is a clever way to emulate this if not.

I made the switch to using a laptop and my phone (using TouchOSC) for music production and thought about how useful this would be for people with limited space or on the go. You really don't realize how useful this is until you try it. FWIW the Ableton implementation was not good. Many 3rd party M4L devices are just not stable or usable.

I think something like this in Generic Flexi would help a lot of people to get things done quicker. Clicking around your project and adjusting things with a knob is easier/quicker/more precise than using mouse/trackpad to adjust them. It also let's you focus on production easier because you aren't stressing about whether or not you have the optimum layout for your controller (or going back and forth adjusting the controller assignments).

What do you think?

[moss]

Hi Moss,

I have a feature request for Generic Flexi and perhaps other scripts as an option (I looked and didn't see it so I'm posting here). I was messing with tons of Max4Live customizations in Ableton and one of the cool devices was a way to control the last touched or active parameter (info here - https://elisabethhomeland.gumroad.com/l ... ut=profile). You map any knob/fader/button/etc on your hardware controller to the M4L device and then that knob will always adjust the last touched control in Ableton.

In BW this could work as follows - option in Generic Flexi under 'Selected Slot - Function' for 'Adjust Last Parameter', then we simply assign a knob to it. I'm not sure if the BW Controller API will allow this directly, but perhaps there is a clever way to emulate this if not.

I made the switch to using a laptop and my phone (using TouchOSC) for music production and thought about how useful this would be for people with limited space or on the go. You really don't realize how useful this is until you try it. FWIW the Ableton implementation was not good. Many 3rd party M4L devices are just not stable or usable.

I think something like this in Generic Flexi would help a lot of people to get things done quicker. Clicking around your project and adjusting things with a knob is easier/quicker/more precise than using mouse/trackpad to adjust them. It also let's you focus on production easier because you aren't stressing about whether or not you have the optimum layout for your controller (or going back and forth adjusting the controller assignments).

What do you think?

That is sadly still missing in the API.

[drsyncenstein]

There is absolutely no need to use Automap with Bitwig. Everything that Automap does can be done directly in Bitwig.

Yes maybe so, but sitting down and mapping out every plugin and instrument as a Bitwig map that I can only use in Bitwig would take months on end, and the point of Automap is you can use the maps in any DAW, I have so many I have saved and rearranged as far back as I've had the ZeRo SL MK 2 at that's a lot, on a new install I just load up my maps as I'm going and set them as default and very on, now I can't with Bitwig which is such a shame.

Because of this situation I looked at the MPMIDI Model 2A, as that works with it's own plugin wrapper, but it's €780 and I just don't have that to spend on replacing a controller at the moment.

Making devices mappings is easy and doesn't cost that much time. There is a device panel thread here at KVR.
I don't know the total amount of panels, but i alone uploaded at least 120 panels.

I used to use automap too, with a zero sl. But automap has'nt been supported for years. With automap you have to load the wrapped vst, with device panels the panel gets loaded automatically with the plugin.

One of the reasons i went to bitwig is the combination of push 2 and device panels, i think it's better than zero sl with automap. Better than Live because you can rearange them on the pages you choose. A used push 2 is not that expensive anymore.

What i like most with push is that you see the pot names, values and panel pages in the display and can select them in banks of eight with a dedicated switch for each page. On 2 big displays. Makes it work like a well designed hardware synth.
Generic flexi can make any controller do advanced stuff. The sl should work too.

But if you really want to work with plugin wrappers you should also look at Nektar controllers.

The device panel thread is here:
viewtopic.php?t=480998
dropbox of aMUSEd, who started the thread and contributed lots of panels:
https://www.dropbox.com/sh/ie17173tybqd ... tzeUa?dl=0
my vst3 device panels:
https://1drv.ms/u/s!At4GWiADXlnHgeRw8iR ... g?e=rW9jgf

[kahtnipp]

Edit: I just saw your comment left on YouTube that you only support the mk1 version. Do you have any plans on supporting the mk2 in the future? Thank you again for everything!

Hey Moss, I really appreciate this script and all of the work you've put into it. Your dedication to your craft is super impressive.

I'm not sure what I'm doing wrong but I have been having a hellofa time trying to get the APCMini to work.

I can get the basic functionality to work with Bitwig's included controller script but the DrivenByMoss script is either unresponsive or minimally responsive.

I've double and tripled checked all of the files and locations and anything else that I could think of. I've been at this for several days now, I really wanted to figure it out without having to bother you.





When I have the DrivenByMoss driver going, the shift button doesn't respond at all.



It seems that this latest edition (From Amazon) might be a little different as the fader controls have been swapped compared to the one in your tutorial video for the APCMini.

I'm really at a loss on what to do from here. I appreciate any input you may have.

[guitarfrenzi]

Bitwig 5.03 DBM 20.3.2 - Push 1

Project Remotes - Navigating through multiple pages on the push1

Cannot navigate between pages smoothly, presses are ignored and will suddenly jump to the end page/ first page, skip multiple pages etc...

Thanks

[moss]

Edit: I just saw your comment left on YouTube that you only support the mk1 version. Do you have any plans on supporting the mk2 in the future? Thank you again for everything!

I tried several times to get a test device but it did not work out. So at least for the time being, no.

[moss]

Bitwig 5.03 DBM 20.3.2 - Push 1

Project Remotes - Navigating through multiple pages on the push1

Cannot navigate between pages smoothly, presses are ignored and will suddenly jump to the end page/ first page, skip multiple pages etc...

Thanks

Hmm, I noticed something similar. It looks to me as if the API responses are slower in the current Bitwig version. Maybe you can already report it to support.

[guitarfrenzi]

Ok, lodged under Ticket 174664