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

[moss]

I am sure I am missing something obvious here. But how can I get Clip parameters in this menu to work on Track 1 - 8? I read through all the manual on Generic Flexi. This Clip parameters seems only for the currently selected track?

Yes, that is correct. It is not supported since this would require quite a bunch of commands and normally devices on which this would make sense need a specialised script/extension anyway.

Hello. I am not sure I understand why it would be difficult. All the commands is already there for selected track, would it not just be possible to copy these in the code and point them to track 1-8? Just like it is available for Mute / Solo / Arm etc.

In 99% of the cases the different controllers will just use note on / note off messages to launch clips and it is such an essential function for sequencers like Bitwig & Live. I feel the flexi is not complete without this basic functionality.

I didn't say that it is difficult. It would add 64 commands plus 64 more if you add alternative start. Furthermore, you won't have any feedback on the LEDs. That's why I said you would need a specific script anyway.

[TheWhistler]

Hello Jürgen,
first post here in this forum, thank´s for setting up DrivenByMoss.
May I please ask something?
I am getting a weird error with the latest version (26.6.2) that I have installed on a Notebook.
I was trying to run a Launchpad Pro MK2 that works wonderfully with the same version of the script on my main studio computer.
It is the first time I try to use the Launchpad on this very notebook.
Both on Win11.
The standard Bitwig script works with my launchpad. I also have a Generic Flexi running with another device (FaderFox EC4) that I ported from my desktop machine.
It says it can´t open midi out 2 of the Launchpad.
Is it possible that this has to do with the introduction of Midi 2.0 as a lot of people are complaining about something?
Maybe I am just dumb, but a bit desperate as well.
Would very much appreciate some advice. Thank´s in advance
Mario

[moss]

Hello Jürgen,
first post here in this forum, thank´s for setting up DrivenByMoss.
May I please ask something?
I am getting a weird error with the latest version (26.6.2) that I have installed on a Notebook.
I was trying to run a Launchpad Pro MK2 that works wonderfully with the same version of the script on my main studio computer.
It is the first time I try to use the Launchpad on this very notebook.
Both on Win11.
The standard Bitwig script works. I also have a Generic Flexi running with another device that I ported from my desktop machine.
It says it can´t open midi out 2 of the Launchpad.
Is it possible that this has to do with the introduction of Midi 2.0 as a lot of people are complaining about something?
Maybe I am just dumb, but a bit desperate as well.
Would very much appreciate some advice. Thank´s in advance
Mario

If your Win11 installation is up-to-date, you should have all the fixes and workarounds and everything should run smoothly. If the Bitwig script runs, DBM should too. Maybe one idea is to check the script console for errors (Press Ctrl+Enter to open the commander, then type "console").

[TheWhistler]

Hello Jürgen,
thank´s for the quick reply.
I was a bit unsure and intimidated by the Midi 2.0 thing.
I thought I would have to fix it by myself. That is a good.

Followed your advice. This is what the console spits out:

Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
MIDI output error: MIDIOUT2 (Launchpad Pro) Send sysex message: Undefined external error.
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Removed MIDI OUT: Launchpad Pro
Removed MIDI OUT: MIDIOUT3 (Launchpad Pro)
Removed MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: Launchpad Pro
Added MIDI OUT: MIDIOUT2 (Launchpad Pro)
Added MIDI OUT: MIDIOUT3 (Launchpad Pro)

It is cycling around a few times and then shut´s the launchpad off to "generic mode"
I did NOT choose Midiout3 actively. Of course Midi2!

This is the Bitwig error message:


I am on Win11 25H2 and constantly updating. Never had any issues so far.

[TheWhistler]

Thank you for your support.

[snupo]

I installed DBM 26.6.2. + Bitwig 6.0 and 6.1 on MacOs and on Windows. I configured the template to Maschine MK3
Transport, track volume and many more works.
But reading and changing the parameters of plugins does not work at all, exactly the same on both computers. I spent days trying to fix that, but I am at the end. I cannot find anything in the docs that I did not do.

New observation: paramters work for Bitwig devices but not for Arturia or NI devices for instance. I guess I need to add something for those to get to work. Any advice?

How can I diagnose and fix this issue?

[wanns0pul]

Hello Moss, first of all, thank you infinitely for all the work you provide for free.
It is truly exceptional.
I use an X-Touch and a Push 2 with Bitwig.
And not going out often from my home, I think I am almost sure that your script has maybe saved me more time in my life than the purchase of my car.
Sincerely, you, as well as Chris Johnson from Airwindows, I work almost exclusively thanks to your free code.
I feel a very pleasant emotion of gratitude.
I am a bit ashamed that my first message on this forum also has a selfish objective, as much as I would like it to sound only like an infinite thank you.
And so ..
I manipulate my plug-ins almost exclusively with the fader of my X Touch with the flip mode, and for example on the Valhalla future verb, I have a page dedicated to the echo and another to the reverb, so I juggle very regularly between these two to adjust it. And the message that occupies the eight LCD screens hides for a certain time the information of what the faders control.
I would have liked to know if there was a possibility to disable these notifications because my X Touch being positioned in front of my screen, I always see what I control.
Thank you again for your work,
Have a great summer
Swann