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

[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.

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.

Thank you for clarifying the general flexi usage, now i understand it better.
But: Do i understand it correctly, that there are only 8 "Set Parameter" Slots free? The list only shows me User: Set Parameter 1 - 8. But i hope this restriction is due to me using the 8-Track Beta Version? I need around 300 Slots if i would assign my whole OSC/PILOT Touch Interface to midi cc functions in Bitwig! I got many device-assignments , FX sends, etc.

And still, it is a great pity, that Bitwig has not implemented a easy way of bi-directional midi assignment.
I m coming from Ableton - and would like to finally change to Bitwig. But it's a real struggle to have inconvenient steps, when they don't seem necessary:
1. In the drivenbymoss general flexi script: Selecting one of 300 Slots
2. touching the controller,
3. pressing SET
4. going to Selected Slot Function, selecting the User: Set Parameter 1-8 there.
5. finally selecting the function i want to midi-map,
6. touching the controller again

compared to the much faster and intuitive mapping workflow which consists of Just steps 5 and 6! Please don't get me wrong, i m happy that it is even working at all, but i had to make this comparison.

[jekblad]

For the akai fire chord sequencer, I have two questions. Great script first off, thank you.

1. There is not a way to edit clips on arranger, only in "session view". Is this a choice or a limitation of the API?
2. I would love to be able to select a step in the top two rows of the Fire, and see the notes assigned to it. This way it is easier to program in the inversions, as you can see all the notes for any step you select. Right now selecting existing steps erases them. Also curious if this is a limitation of the API.

thanks

[Pati ETP]

Hi

When I start Bitwig 4.10 on Windows 11, my Launchpad pro mk3 starts to act weird.
The custom modes are empty after the DAW is started.

Also when I press the buttons below the 64v grid, the modes (chords/notes/etc.) jump randomly in between.

I reinstalled the USb driver, firmware is up to date. Moss script is 19.2.2

Please help. Thanks a lot!

[moss]

Hello, ok,
I didn't see the option, sorry. how to adjust it? I want to record on a new clip with one click, then on the next click end the loop, then double click to create a new clip next to it?

That's not available. Closest is either "New clip" or the "Clip Based Looper" (see explanation in the manual).

[moss]

I have now Komplete Kontrol Mk II new and wanted to ask, if there is a workaround, when switching between tracks with Komplete Kontrol loaded each, the display on the keyboard does not change to the Kontrol instance on the current selected track. Instead it get stuck in tha last loaded instance. The same on the Bitwig provided script.

So what I need to do to get it working properly?

You can try to reinstall the Komplete Kontrol software. It sometimes just breaks since their architecture is quite complex with several background services and virtual MIDI drivers...

[moss]

I guess it was unnecessary to create a new post and that I should have posted inside this topic instead. So here goes:

I tried the Push 1 with moss script before and there was a problem with the screen becoming completely unresponsive in MacOS, like data messages where getting stuck and gathering up.
The screen would process things you where doing a long time ago and one had to wait to get it responsive. I was contacted by another kvraudio member who had the exactly same issues with Push1+Moss+MacOS.
When I tried the Push 1 in Linux Bitwig with the same computer everything ran smoothly.
Since I am using MacOS as the standard audio system I had to give up on the Push 1 since it just would not work normally and I sold it.

Now I am on another system, Monterey with M1 and I am curious if other people are running their Push 1 problem free in Bitwig with MacOS these days. If the script would work it would be a great controller since it can be found quite inexpensive second hand.

I am not aware of any issues with Push 1 on Macos.

[moss]

And still, it is a great pity, that Bitwig has not implemented a easy way of bi-directional midi assignment.
I m coming from Ableton - and would like to finally change to Bitwig. But it's a real struggle to have inconvenient steps, when they don't seem necessary:
1. In the drivenbymoss general flexi script: Selecting one of 300 Slots
2. touching the controller,
3. pressing SET
4. going to Selected Slot Function, selecting the User: Set Parameter 1-8 there.
5. finally selecting the function i want to midi-map,
6. touching the controller again

compared to the much faster and intuitive mapping workflow which consists of Just steps 5 and 6! Please don't get me wrong, i m happy that it is even working at all, but i had to make this comparison.

Generic Flexi is designed for banks of 8 parameters.

What you want, can be done with Bitwig in the same way as with Ableton. Simply choose a generic driver which routes all MIDI data to Bitwig and map your MIDI CC by right clicking on the parameter and choosing MIDI learn. If you want to have the same setup in each project, store it as a template.

[moss]

1. There is not a way to edit clips on arranger, only in "session view". Is this a choice or a limitation of the API?

This is broken since Bitwig 2 and sadly still not fixed. I am bringing up the topic regularily. But it is linked to the access of the arranger which needs some more thinking, that's why I takes time.

2. I would love to be able to select a step in the top two rows of the Fire, and see the notes assigned to it. This way it is easier to program in the inversions, as you can see all the notes for any step you select. Right now selecting existing steps erases them. Also curious if this is a limitation of the API.

You can activate the note edit mode (see the manual) to select notes.

[moss]

Hi

When I start Bitwig 4.10 on Windows 11, my Launchpad pro mk3 starts to act weird.
The custom modes are empty after the DAW is started.

Also when I press the buttons below the 64v grid, the modes (chords/notes/etc.) jump randomly in between.

I reinstalled the USb driver, firmware is up to date. Moss script is 19.2.2

Please help. Thanks a lot!

There are no cutom modes in my implementation. Which see the manual and my Youtube tutorials.

[nowiamone]

What you want, can be done with Bitwig in the same way as with Ableton. Simply choose a generic driver which routes all MIDI data to Bitwig and map your MIDI CC by right clicking on the parameter and choosing MIDI learn. If you want to have the same setup in each project, store it as a template.

Sorry for being so dumb, but i really don't know what "generic driver" means in this context, to achieve this. Where do i get this?

I have no problems sending midi TO bitwig, and using the simple Ableton-style mapping mode with that. My problems occur when trying to have Bitwig sending Midi OUT to my interface (=moving the knobs in Bitwig isnt moving the knobs in my interface) - the general flexi 8 parameter banks work with Midi OUT, but arent enough, and sadly i dont understand your suggested generic driver solution.

[questionaire]

Morning Juergen,

There is a small issue with latest script 19.2.2 and i guess also with the 20 version, i'm using Launchkey mk3 and when i have once chosen to go into drum mode and then go back to session mode the following happens: Whenever i choose a new instrument track with right click mouse and add a new device into the instrument track the script will change to drum mode instead of staying into session mode. So somehow the script is not resseting the drum mode after changing to session mode and keeps it in memory it looks like it is remembering the drum mode and keeps on reverting to it with each new added new device?

I would expect that whatever and no matter how you add a newly device, it would stay in the mode you are working in?

When i draw a device directly from the browser and drop it into the working area the session mode stays active by the way so that works fine.

Hope this one can be fixed? It is not a dealbreaker ofcourse but it would be cool to have this corrected.

Using Bitwig 4.4.10 windows 10.

By the way totally agree with what troy 808 said one post above.

Regards,
Wilfred.

This should not be the case. Will check.

EDIT: Will be fixed in the next update!

Thanks for that! May it be possible to fix it in 19.2.2 aswell? To keep Bitwig version 4 compatible?
Otherwise i'm forced to update my subscription with another year, and i'm not ready for that yet.
It is not your problem ofcourse but it would be great if the 19 version could get this fix!

[SamDi]

I have now Komplete Kontrol Mk II new and wanted to ask, if there is a workaround, when switching between tracks with Komplete Kontrol loaded each, the display on the keyboard does not change to the Kontrol instance on the current selected track. Instead it get stuck in tha last loaded instance. The same on the Bitwig provided script.

So what I need to do to get it working properly?

You can try to reinstall the Komplete Kontrol software. It sometimes just breaks since their architecture is quite complex with several background services and virtual MIDI drivers...

Hm, I fear that's not the solution, since I have the same behaviour on Windows and Mac consistently on BW. On other DAWs I just tested Ableton and Logic up until now, where it works correctly. It's a BW problem. On both scripts (stock and Moss), the truck change just doesn't bring the right Komplete instance on the HW. In the meanwhile, I have found, that some other guys have the same problem and the workaround is, that you can press a button in the Komplete plugin, to make this the active instance on the keyboard.

But do you want to say that track changing and right instance gets active on Keyboard works for you in BW?

[nowiamone]

I have now Komplete Kontrol Mk II new and wanted to ask, if there is a workaround, when switching between tracks with Komplete Kontrol loaded each, the display on the keyboard does not change to the Kontrol instance on the current selected track. Instead it get stuck in tha last loaded instance. The same on the Bitwig provided script.

So what I need to do to get it working properly?

You can try to reinstall the Komplete Kontrol software. It sometimes just breaks since their architecture is quite complex with several background services and virtual MIDI drivers...

Hm, I fear that's not the solution, since I have the same behaviour on Windows and Mac consistently on BW. On other DAWs I just tested Ableton and Logic up until now, where it works correctly. It's a BW problem. On both scripts (stock and Moss), the truck change just doesn't bring the right Komplete instance on the HW. In the meanwhile, I have found, that some other guys have the same problem and the workaround is, that you can press a button in the Komplete plugin, to make this the active instance on the keyboard.

But do you want to say that track changing and right instance gets active on Keyboard works for you in BW?

Hello,
For me, changing tracks with the Komplete Kontrol S49mk2 is working properly, changing the Display-content of each plugin, too. So i think your problem might be a wrong Plugin Hosting Mode. Go to Settings -> Plugins -> Plugins Hosting Mode, and choose "Together".
If it's still not working, i don't know the solution for you.

[SVRVDX]

Hey Moss! As I understand it, the problem with choosing the first device in the device panel has broken on all controllers and is still limited by the API. There is another problem, I consider it as a "step back" above, this new method of launching clips was written about it is very bad. The Clip Launcher stops working if you disable the Selecting clips in Clip Launcher checkbox in the Behavior settings. In version 19.2.2 it still works correctly, the old method could be added to new versions.

[moss]

What you want, can be done with Bitwig in the same way as with Ableton. Simply choose a generic driver which routes all MIDI data to Bitwig and map your MIDI CC by right clicking on the parameter and choosing MIDI learn. If you want to have the same setup in each project, store it as a template.

Sorry for being so dumb, but i really don't know what "generic driver" means in this context, to achieve this. Where do i get this?

I have no problems sending midi TO bitwig, and using the simple Ableton-style mapping mode with that. My problems occur when trying to have Bitwig sending Midi OUT to my interface (=moving the knobs in Bitwig isnt moving the knobs in my interface) - the general flexi 8 parameter banks work with Midi OUT, but arent enough, and sadly i dont understand your suggested generic driver solution.

You should direct that question to Bitwig support.