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

[nowiamone]

[*]Komplete Kontrol MkII

• New: Make sure that the same slot is selected when switching tracks.

[*]MCU

It's working!
really nice, thank you!

Concerning the bi-directional midi control (my post of Mon May 01, 2023 9:33 pm), should i write bitwig support, or is there any hope you might do a script for that?

[moss]

[*]Komplete Kontrol MkII

• New: Make sure that the same slot is selected when switching tracks.

[*]MCU

It's working!
really nice, thank you!

Concerning the bi-directional midi control (my post of Mon May 01, 2023 9:33 pm), should i write bitwig support, or is there any hope you might do a script for that?

As someone else already commented, this works with Generic Flexi.

[luis_]

Hey Moss,

I ran into a bug while using your otherwise wonderful script with my Launchkey 49 MKIII. When I want to map parameters in Arturia Plugins in the plugin itself and not using remotes, the CC from the Launchkey isn't recognized. When I run the Launchkey as a Generic Keyboard + 8 Knobs, it works. I'm trying to use the user pad / fader / knob banks of course.

I suspect it might be necessary to explicitly include in the script that these 12 parameter banks don't get funneled into "Bitwig Control" if you know what I mean but are interpreted as regular Keyboard MIDI CC? Or is this on Novation?

Thanks for all your work.
Luis

EDIT: If this should be in fact something you change in the script, could you maaybe add it also in a version that's 4.3 compatible?

[Danilo Villanova]

Hi Moss and everyone,

I just bought a Nektar T6 and the Bitwig script is nice, but I would like to know if it's possible to use it with DrivenByMoss. Bitwig recognizes it immediately so I cannot uninstall the script. I guess I could try with MCU or Flexi scripts (it has a mode that sends MIDI CC) but thought of checking here first. Has anyone tried this? Does the display work?

Thanks!

[moss]

Hey Moss,

I ran into a bug while using your otherwise wonderful script with my Launchkey 49 MKIII. When I want to map parameters in Arturia Plugins in the plugin itself and not using remotes, the CC from the Launchkey isn't recognized. When I run the Launchkey as a Generic Keyboard + 8 Knobs, it works. I'm trying to use the user pad / fader / knob banks of course.

I suspect it might be necessary to explicitly include in the script that these 12 parameter banks don't get funneled into "Bitwig Control" if you know what I mean but are interpreted as regular Keyboard MIDI CC? Or is this on Novation?

Thanks for all your work.
Luis

EDIT: If this should be in fact something you change in the script, could you maaybe add it also in a version that's 4.3 compatible?

As you assumed it does not work like this in Bitwig. I am wondering why you do not want to use remote controls for this? If you need MIDI CC you could insert a CC device in front of the plugin (which IMHO makes only sense for hardware synths) but you will then get no feedback and parameter names on the controller.

[luis_]

Okay.. The reason why I want to do it like this is that the V Collection Plugins (over 30) all have a decent amount of internal mapping already. Setting up remotes for all 30 would be way more tedious than just using these pre-existing mappings, and for example won't allow me to change presets. And yeah, true, the MIDI CC device is a good point! But with that again I need to have multiple devices if I want to control more than 8 parameters and there are no buttons.

Shouldn't it be possible to just send the MIDI CC to the armed track? As I said, it works with the generic Bitwig Keyboard + 8 Knobs. The plugin then receives the CC as long as the track is armed. When using a Control Script, is there a way to change the scope of certain controller parameters?

Then I could simply set my four knob user banks in the Launchkey to the standard CCs that Arturia uses and have these banks as dedicated control without any further setting up and devices that I need to add everytime.

If you think it's possible but too much work for too little use, maybe point me in the direction and I will take a closer look and maybe do a pull request.

[luis_]

As you assumed it does not work like this in Bitwig. I am wondering why you do not want to use remote controls for this? If you need MIDI CC you could insert a CC device in front of the plugin (which IMHO makes only sense for hardware synths) but you will then get no feedback and parameter names on the controller.

Okay.. The reason why I want to do it like this is that the V Collection Plugins (over 30) all have a decent amount of internal mapping already. Setting up remotes for all 30 would be way more tedious than just using these pre-existing mappings, and for example won't allow me to change presets. And yeah, true, the MIDI CC device is a good point! But with that again I need to have multiple devices if I want to control more than 8 parameters and there are no buttons.

Shouldn't it be possible to just send the MIDI CC to the armed track? As I said, it works with the generic Bitwig Keyboard + 8 Knobs. The plugin then receives the CC as long as the track is armed. When using a Control Script, is there a way to change the scope of certain controller parameters?

Then I could simply set my four knob user banks in the Launchkey to the standard CCs that Arturia uses and have these banks as dedicated control without any further setting up and devices that I need to add everytime.

If you think it's possible but too much work for too little use, maybe point me in the direction and I will take a closer look and maybe do a pull request.

EDIT: Whoops, sorry for double posting

[nowiamone]

Concerning the bi-directional midi control (my post of Mon May 01, 2023 9:33 pm), should i write bitwig support, or is there any hope you might do a script for that?

As someone else already commented, this works with Generic Flexi.

I m sorry, concerning the generic flexi, i was too unexperienced, to properly use it in the beginning.
What i m still hoping for is a bi-directionally working script which makes it possible to midi-cc-assign everything you see and can click on Bitwigs Interface, not via a dropdown-menue in the Controller-Preferences, but simply by clicking on it (=mapping mode).
But since you already are into an incredible amount of scripting, i guess i will leave that to a Bitwig-support-Feature request.

[ondrei]

Hi Moss is posible to Port chord Mode from launchpad pro mk3 yo launchpad x ? Thanks for you hard work

Possible yes. But not sure if I ever want to tackle this. Never was a fan of preconfigured chords and it involves some head-scratching.

Hi MOSS, thank you for great support. I am a Launchpad Pro mk3 user and I love all Bitwig integration functions you implemented. Just one Launchpad "factory" functionality I am missing - chord mode, capable to store chords defined by user. I have learned music from Hooktheory and it is very inspiring for me to create set of chords and make chord progression which is "not boring". By "not boring" I mean occasionaly change the key. I understand you are not "a fan of preconfigured chords", but chords precongured by user are very useful. Just in the case it is possible and required by more Launchpad users.

[ansolas]

Feature Suggestion
Since Bitwig 5 limit's the Plugin Parameter Map Item Count to only 8 Controls, it would be nice, if we could choose the device which should be used for controls.

For example when having 3 Behringer X-touches it would be more convenient to be able to use the X-Touch direct infront of you instead of the left device. This get's even more unconvenient for somone with 4 Devices.

Thank you very much for anything.
Without your script I wouldn't even consider trying Bitwig.

[quincy]

Hi Moss. I'm finding some possible bugs with Push 1. With new Bitwig 5 there is a controller icon in the top-right of the screen and in these settings there is a mode option with "any track / device selection", "track selection", "device selection" or "Project remotes". If I e.g. choose "track selection" then I would be expecting the device view (when I hit device button) to show the device remotes but I don't always get this. If I choose "Project remotes' then I expected to always se the project remotes no matter what track I select but if I select a track with no devices I get a message "select a device or press add effect".

I appreciate of course that Bitwig 5 is still in Beta. I'm generally getting inconsistent behaviour with Push 1 and your script. Another example is when I try to view track remotes, sometimes I can't see anything on push display (or a message to add a device) but the knobs are controlling the track remotes if, for example, they are controlling track parameters like volume or pan.

I also have one feature request - if I'm viewing e.g. the device page I'd love to be able to easily switch track focus with the arrow buttons or have the similar Ableton behaviour where I hold the track button, select a new track, and then when I release it flips back to the device view or whatever previous view I was on.

Thanks for all the effort with these scripts.

[moss]

Shouldn't it be possible to just send the MIDI CC to the armed track? As I said, it works with the generic Bitwig Keyboard + 8 Knobs. The plugin then receives the CC as long as the track is armed. When using a Control Script, is there a way to change the scope of certain controller parameters?

Then I could simply set my four knob user banks in the Launchkey to the standard CCs that Arturia uses and have these banks as dedicated control without any further setting up and devices that I need to add everytime.

Sure. In Flexi you can also select MIDI CC as a function to be sent to Bitwig.
Or write a very simple script which just routes everything to Bitwig.

[moss]

Concerning the bi-directional midi control (my post of Mon May 01, 2023 9:33 pm), should i write bitwig support, or is there any hope you might do a script for that?

As someone else already commented, this works with Generic Flexi.

I m sorry, concerning the generic flexi, i was too unexperienced, to properly use it in the beginning.
What i m still hoping for is a bi-directionally working script which makes it possible to midi-cc-assign everything you see and can click on Bitwigs Interface, not via a dropdown-menue in the Controller-Preferences, but simply by clicking on it (=mapping mode).
But since you already are into an incredible amount of scripting, i guess i will leave that to a Bitwig-support-Feature request.

You can do this by assigning "User: Set Parameter X" to a knob in Flexi. Then select the learn function in Bitwig and turn the knob.

[moss]

Hi Moss. I'm finding some possible bugs with Push 1. With new Bitwig 5 there is a controller icon in the top-right of the screen and in these settings there is a mode option with "any track / device selection", "track selection", "device selection" or "Project remotes". If I e.g. choose "track selection" then I would be expecting the device view (when I hit device button) to show the device remotes but I don't always get this. If I choose "Project remotes' then I expected to always se the project remotes no matter what track I select but if I select a track with no devices I get a message "select a device or press add effect".

That's work in progress (also on Bitwigs side).

[erickey]

Hello, I'm new to the forum.
I'm using the incredible DrivenByMoss script for the Akai Fire in Bitwig 4. Thanks for providing this, it's amazing!
I had two questions:
-How possible, or difficult, would it be to alter the script to have a button to control the up and down arrows on the Remote Control device for preset pages? It would be great to scroll through these without using the mouse.

Second, not for the Akai Fire, but an Arturia Minilab mk3:
- Is there a script to allow control of the device parameters, (like MIDI CC for example) similar to the AKAI Fire User page with the encoders? For example, on the Fire, the encoders always control whatever parameters/device are selected, and switch whenever a different device is in focus. Conversely, the Minilab encoders have to be assigned and once assigned they always control the same assigned parameters. It would be great if the 8 encoders functioned more ephemerally like the Fire.

Thanks again!!
Eric