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

[auricle]

Hi Jurgen,

Also having an issue. Using Bitwig 3.2 official release with DrivenByMoss 3.2beta8.
I'm using an X-Touch and X-Touch Extender set up in MCU mode.

All faders, V-Pots and buttons on the X-Touch and Extender work perfectly, however the LCD displays on the Extender do not show any information, they are blank. The LCDs on the X-Touch work fine, however.

[moss]

Hi Jurgen,

Also having an issue. Using Bitwig 3.2 official release with DrivenByMoss 3.2beta8.
I'm using an X-Touch and X-Touch Extender set up in MCU mode.

All faders, V-Pots and buttons on the X-Touch and Extender work perfectly, however the LCD displays on the Extender do not show any information, they are blank. The LCDs on the X-Touch work fine, however.

Have you tried the Mackie Extender setting in the settings? I not have those devices so I cannot test.

[AFranke]

Hi,
so yesterday I mapped some controls of Arturias SEM V to a bunch of Device Pages in BWS 3.2 (DrivenByMoss-9.10-Bitwig). But many of the can't be controlled via my Hardware (61SL MK2,Push 1). In concrete any Parameter in Arturias SEM V that is a "switch" can be mapped, but it does not react to changes from the hardware controllers. If I move the same parameter in the device page of BWS with my mouse all works fine. But not by moving a knob on one of my controllers.

Made a screenshot. All parameters like the ones with the red arrow don't react to controller knobs.
https://1drv.ms/u/s!AjgGhHvp8bcPldl1jmF ... g?e=gmTe8R

09.06.2020: I did the same today in Ableton Live and all works fine, so I think it's a bug in the script/extension

[auricle]

Hi Jurgen,

Also having an issue. Using Bitwig 3.2 official release with DrivenByMoss 3.2beta8.
I'm using an X-Touch and X-Touch Extender set up in MCU mode.

All faders, V-Pots and buttons on the X-Touch and Extender work perfectly, however the LCD displays on the Extender do not show any information, they are blank. The LCDs on the X-Touch work fine, however.

Have you tried the Mackie Extender setting in the settings? I not have those devices so I cannot test.

You're right, I checked the settings and I didn't realise there was 'Extender' and also a 'Mackie Extender'. I changed it to Mackie Extender from my original choice of 'Extender' and now it's working fine.

Sorry about that and thanks for the help!

[moss]

Hi Jurgen,

Also having an issue. Using Bitwig 3.2 official release with DrivenByMoss 3.2beta8.
I'm using an X-Touch and X-Touch Extender set up in MCU mode.

All faders, V-Pots and buttons on the X-Touch and Extender work perfectly, however the LCD displays on the Extender do not show any information, they are blank. The LCDs on the X-Touch work fine, however.

Have you tried the Mackie Extender setting in the settings? I not have those devices so I cannot test.

You're right, I checked the settings and I didn't realise there was 'Extender' and also a 'Mackie Extender'. I changed it to Mackie Extender from my original choice of 'Extender' and now it's working fine.

Sorry about that and thanks for the help!

No worries. Good to know what the correct setting is for the Behringer extender.

[srzorro]

I'm using OS Mojave and Bitwig 3.2, but had the same issue with High Sierra. Had the same issue with past versions of Bitwig as well. Recently changed my macbook, so it's probably not the problem. I have tested the responde with other DAWs and seems to work ok.

Hi Jürgen,
First of all, I just wanted to say that I really appreciate your work, you have fastened my workflow in so many ways, and made my interaction with Bitwig awesome.

I'm having an issue that is driving me crazy with the Novation SLMK3, whatever parameter I move on the DAW or on the controller, the refresh rate of the value of the position of the parameter in the controller has a lot of latency. The position of the knob shows just fine, but the value of the position just drags a lot. It is terrible specially when I have an automated parameter with lots of fast movement. I have to wait till it goes mad up and down till it finishes until I can do whatever else with the controller. Don't know if I f**ked up some configuration at some point, or is it an issue with something else.

Thanks a lot in advance,

What is you OS? Bitwig 3.2?

[deailes]

When checking settings it has added 5 versions of the controller. 3 of them enabled and 2 of them disabled. I delete them all and then manually add 1 back in. Close and reopen bitwig. Same thing happens. Some times its 5 instances of the controller, sometimes less.

I have the exact same MIDI error and behavior. The error occurs on every start of Bitwig and Bitwig is the only application running.

Could it be that the controller detection algorithm get's stuck in an endless loop and at one point runs out of memory and then exits the loop?

I'm on a Windows 10 machine with an NI M32 with the latest firmware.

Can you please check what are the exact names of the in-/output ports? But not in Bitwig but in e.g. MIDI-OX. And then please compare to the ones showing up in Bitwig.

Cheers

John

Yeah same as what Raketenbauer posted. Image below from midi ox

[moss]

Hi,
so yesterday I mapped some controls of Arturias SEM V to a bunch of Device Pages in BWS 3.2 (DrivenByMoss-9.10-Bitwig). But many of the can't be controlled via my Hardware (61SL MK2,Push 1). In concrete any Parameter in Arturias SEM V that is a "switch" can be mapped, but it does not react to changes from the hardware controllers. If I move the same parameter in the device page of BWS with my mouse all works fine. But not by moving a knob on one of my controllers.

Don't have the Arturia plugins, so cannot test that. But I played around a bit with switches on some other plugins which behaved a bit strange. It worked but a bit jumpy, so this could be caused by rounding error.
Parameter changing is currently a bit hacky in DBM since I switched not fully to the new hardware API, will look into this in the future but might take a bit.

[AFranke]

Hi,
so yesterday I mapped some controls of Arturias SEM V to a bunch of Device Pages in BWS 3.2 (DrivenByMoss-9.10-Bitwig). But many of the can't be controlled via my Hardware (61SL MK2,Push 1). In concrete any Parameter in Arturias SEM V that is a "switch" can be mapped, but it does not react to changes from the hardware controllers. If I move the same parameter in the device page of BWS with my mouse all works fine. But not by moving a knob on one of my controllers.

Don't have the Arturia plugins, so cannot test that. But I played around a bit with switches on some other plugins which behaved a bit strange. It worked but a bit jumpy, so this could be caused by rounding error.
Parameter changing is currently a bit hacky in DBM since I switched not fully to the new hardware API, will look into this in the future but might take a bit.

In Ableton Live all works fine with Push & 61SL MK2, tested this a few minutes ago, so I think there is a problem with your script/extension, also because the mappings work just fine if you change the parameter by mouse inside of BWS. I think Arturia has demo versions of the plugins. Btw. I'm running W10.

[sj1]

Hi,

Working with Bitwig Studio, which offers no Stop Button on the clip for populated clips, I wonder if it would be technically possible for a controller script (for Novation Launchpad Pro, in my case) such as DrivenByMoss to be aware that a clip has already been triggered On and when that clip's (Launchpad) button is pressed again then the controller script sends the "track stop-all-clips" message (as if the singular Stop button provided only at the track level had been pressed)?

Another way to put it is that I would like to be able to toggle a Bitwig clips On/Off from it's own button the same way that operation can be done in Ableton Live.

I love many things about Bitwig, but losing my one-touch control of clips from the Launchpad Pro is not one of them!

With so many other unique and clever features implemented in DrivenByMoss over the years, I wonder if this one might be a possibility too.

[moss]

Working with Bitwig Studio, which offers no Stop Button on the clip for populated clips, I wonder if it would be technically possible for a controller script (for Novation Launchpad Pro, in my case) such as DrivenByMoss to be aware that a clip has already been triggered On and when that clip's (Launchpad) button is pressed again then the controller script sends the "track stop-all-clips" message (as if the singular Stop button provided only at the track level had been pressed)?

Yes, that is possible and you can already do that with the clip stop mode (which you can also use temporarily if you keep the mode button pressed).

Another way to put it is that I would like to be able to toggle a Bitwig clips On/Off from it's own button the same way that operation can be done in Ableton Live.

Could be an interesting option. Will add it to the wishlist.

[sj1]

Thank you kindly for your reply, and for adding to the wish list!

[Jimantronic]

I realised this week that I can use a regular foot pedal into my Push 2 to start clip recording and it all just works great, so thank you Jurgen
So simple, but quite an upgrade for me in terms of workflow

[Gummiball]

Hello.

Sorry for my bad english.

Today my Launchpad Pro MK3 arrives and I want to test the behavior with Bitwig. At the moment I can get it to run.

This are the settings for Launchpad Pro MK3 wich was autodetected:

Bildschirmfoto 2020-06-12 um 17.50.12.png

MidiIn:

Bildschirmfoto 2020-06-12 um 17.53.01.png

MidiOut:

Bildschirmfoto 2020-06-12 um 17.53.13.png

No button works like in the description for DrivenByMoss. The button session is not activated and I don't can select it.

I am on Mac with Catalina (10.15.5), Bitwig in version 3.2.1 and DrivenByMoss in version 9.10

I hope someone can help me

[Axis08]

Hi !

I'm using Bitwig 3.2.1 (Windows 10) and have the same problem as deailes and Raketenbauer for my midi controller - Native A61

"Komplete Kontrol A61 Midi : Could not open MIDI Ouptut. There is not enough memory available for this task. Quit one or more applications to increase available memory, and then try again".

Even if I get this message at every Bitwig launch I can play with the controller.

Also I do have a problem with my Push2 and the hardware push buttons only light up if I press one (for example the Browser button is always dark until I press it). Quite hard to use the push2 then.

bests