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

[moss]

I don't see this much because as a rule I either create remote controls for any device I am using when I first get it or for more complex synths I make a NKS mapping

Except for very basic plugins with just a handful of knobs I find the default mappings are rarely optimal for me

Dito. I just wanted to raise this "issue".
But the actual problem is the handling issue laid out in my post as well

There are some issues in the current implementation. E.g. when you add/remove devices, the selection freaks out. The problem with the protocol is that it is not only important what you send but also when you send it. Quite a nightmare... I started to compare with the Bitwig implementation but this is no fun...

[thomba]

What I have noticed is: The script works absolutely fine when using Bitwig devices only. But the moment third party plugins are getting involved it becomes rather clitchy.

[moss]

What I have noticed is: The script works absolutely fine when using Bitwig devices only. But the moment third party plugins are getting involved it becomes rather clitchy.

The problem was with NKS devices (Kontrol, Kontakt) since this special mode is not notified. Will be fixed in the next update (and some other issues as well).

[thomba]

Sorry for the above hassle and thank you very much for all your support. Thom

[thomba]

Probably off-topic. If so - I do apologise: I have two MIDI controllers. Controller 1 (SL Mixface, all faders, knobs are activated within the script) is assigned to an arpeggiator plugin, Controller 2 (Komplete Kontrol) to a synth. Both are situated on the same track. How can I save and later recall the mapping for Controller 1, so that whenever I use the arp plugin, its knobs are automatically linked only to this controller? The goal: I would love to be able to adjust two different devices - in this case the arp plugin and the synth - simultaneously with the help of both controllers.

[moss]

Probably off-topic. If so - I do apologise: I have two MIDI controllers. Controller 1 (SL Mixface, all faders, knobs are activated within the script) is assigned to an arpeggiator plugin, Controller 2 (Komplete Kontrol) to a synth. Both are situated on the same track. How can I save and later recall the mapping for Controller 1, so that whenever I use the arp plugin, its knobs are automatically linked only to this controller? The goal: I would love to be able to adjust two different devices - in this case the arp plugin and the synth - simultaneously with the help of both controllers.

You can lock one controller to a device but I am not sure if this restores the state after a reload of the project.
Alternatively, I suggest to use Project or Track parameters with one device where you can map whatever you want.

[thomba]

Thanksssssss

[thomba]

Another shortish question to the community: Can you permanently link a Bitwig Shortcut to a midi controller element? thanks

[Mantras]

Would it be possible to implement in the flexi in the scene section "Selecting scene without launching" ?

[pdxindy]

Does DBM support Novation Launch Control XL 3?

[handed]

Hi Moss,

Really appreciate the work you've put into this project. If you ever decided to create a script for Ableton Move, it would be incredibly appreciated. In my mind they are a perfect match.

[moss]

Does DBM support Novation Launch Control XL 3?

No.

[pdxindy]

Does DBM support Novation Launch Control XL 3?

No.

Thanks for the reply

[moss]

DrivenByMoss 26.2 is online!

Get it from https://mossgrabers.de

• Native Instruments Kontrol Mk3
  • New: In device mode up/down changes tracks.
  • Fixed: First track of the current page could not be muted/soloed.
  • Fixed: Selecting devices did not fully work after removing/adding a device.
  • Fixed: Fixed several issues caused by the presence of a NKS device (Kontrol, Kontakt 7/8). Note: Since the special NKS mode is not notified, device and track modes cannot be changed when a NKS device is selected!
• Push 2
  • New: Added a graphical visualisation for the pad sensitivity curve.
• Push 3
  • New: MPE Pitchbend does now work with the selected scale!
  • New: Added support for configuring the pad sensitivity curve incl. a graphical visualisation.

Enjoy!

[betaveld]

Hello Moss,
thanks for the latest update. While working with the Maschine JAM, I noticed that an unselected channel assigned the color turquoise shows the color blue in the “Group Buttons” A-H instead. It seems to be the same case for the Maschine MK2/MK3.

This minor flaw is only noticeable because the rest of the implementation is so excellent.