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

[quincy]

Hi Moss. Firstly, thanks for all your work with these amazing controller scripts. The Bitwig community thanks you!

I wanted to ask if the new APC Mini or APC Key 25 are supported? I need a small clip-launching controller but I don't have the space for anything larger. It looks like APC Mini is supported but I didn't know if the new model still works with your scripts. The step-sequencing an other extra functions look very helpful too.

Happy new year!

[moss]

Hi Moss. Firstly, thanks for all your work with these amazing controller scripts. The Bitwig community thanks you!

I wanted to ask if the new APC Mini or APC Key 25 are supported? I need a small clip-launching controller but I don't have the space for anything larger. It looks like APC Mini is supported but I didn't know if the new model still works with your scripts. The step-sequencing an other extra functions look very helpful too.

Happy new year!

Nothing specific currently, maybe the new APCmini but no idea if and when.

[LarsDaniel]

Thanks for the quick answer.

[dnalord77]

UPDATE: I tested with DrivenByMoss 18.5 and track switching via dedicated buttons worked. Tested again with DrivenByMoss 19 and had the issue (cannot switch with dedicated track buttons) repeat.

Original post:

Hello Jürgen,

Thank you for your work on the scripts, I use a Maschine Mikro and a Launchpad Mini and they work great!

I just got a Launchpad Pro Mk3 and everything seemed to work fine. Initially, I was able to switch tracks with the dedicated buttons but suddenly, they just stopped working. (I was going through the manual checking all the functions). When I started then to work on something, I noticed I could no longer switch tracks using the dedicated track buttons; in short, I cannot do what you do here (on 03:05) :

(I see that the hardware detects the press by shortly turning off and back on the track button led, but regarless the track I select, Bitwig stays on the last track selected)

I have updated the Launchpad's firmware, installed the latest DrivenByMoss 19.0 extension, dis/re-connected the launchpad, rebooted PC and have the same issue. I can mute/solo tracks using the combination of Mute/Solo + track select buttons (as well navigate along the tracks with the back and forward buttons), but when clicking the track select buttons independently, they do not switch.

I can switch tracks using the session view, but the sole reason I got the Launchpad Pro was because of the dedicated track select buttons. So far, everything else seem to work as expected. Did I break something? Any ideas?

Thank you in advance!

[moss]

UPDATE: I tested with DrivenByMoss 18.5 and track switching via dedicated buttons worked. Tested again with DrivenByMoss 19 and had the issue (cannot switch with dedicated track buttons) repeat.

Original post:

Hello Jürgen,

Thank you for your work on the scripts, I use a Maschine Mikro and a Launchpad Mini and they work great!

I just got a Launchpad Pro Mk3 and everything seemed to work fine. Initially, I was able to switch tracks with the dedicated buttons but suddenly, they just stopped working. (I was going through the manual checking all the functions). When I started then to work on something, I noticed I could no longer switch tracks using the dedicated track buttons; in short, I cannot do what you do here (on 03:05) :
(I see that the hardware detects the press by shortly turning off and back on the track button led, but regarless the track I select, Bitwig stays on the last track selected)

I have updated the Launchpad's firmware, installed the latest DrivenByMoss 19.0 extension, dis/re-connected the launchpad, rebooted PC and have the same issue. I can mute/solo tracks using the combination of Mute/Solo + track select buttons (as well navigate along the tracks with the back and forward buttons), but when clicking the track select buttons independently, they do not switch.

I can switch tracks using the session view, but the sole reason I got the Launchpad Pro was because of the dedicated track select buttons. So far, everything else seem to work as expected. Did I break something? Any ideas?

Thank you in advance!

Argh, seems I broke something while fixing something else. Will be (hopefully) fixed in the next update.

[quincy]

Hi Moss. I bought a new APC Mini (as mentioned above I was considering it) and unfortunately your existing script doesn't seem to work. I'm a programmer myself and I've managed to make something that can control an 8x8 window around the session view clips and launch them, but I have no idea what MIDI messages I need to send back to set the state of the pads etc. The controller is "blank" with no pads lit up etc.

Are you able to find this information from official MIDI implementation guides online or is there another way to work it out? I googled extensively and I couldn't anything on the APC Mini at all, old or new versions. If you have any pointers I'd really appreciate it. I'm a half-decent coder (I should be after 15+ years) but I need some reference material!

[moss]

Hi Moss. I bought a new APC Mini (as mentioned above I was considering it) and unfortunately your existing script doesn't seem to work.

As expected since the Mk2 is not supported.

I'm a programmer myself and I've managed to make something that can control an 8x8 window around the session view clips and launch them, but I have no idea what MIDI messages I need to send back to set the state of the pads etc. The controller is "blank" with no pads lit up etc.

Are you able to find this information from official MIDI implementation guides online or is there another way to work it out? I googled extensively and I couldn't anything on the APC Mini at all, old or new versions. If you have any pointers I'd really appreciate it. I'm a half-decent coder (I should be after 15+ years) but I need some reference material!

Sometimes you get some documentation if not, you need to reverse engineer the protocol. Since the Mk2 is pretty new it is not surprising that noone looked into it so far.

[quincy]

Sometimes you get some documentation if not, you need to reverse engineer the protocol. Since the Mk2 is pretty new it is not surprising that noone looked into it so far.

Thanks, I thought that might be the case. Perhaps I’ll try to find some sort of MIDI monitor and see what’s going on with the Ableton behaviour.

[Serhii Kot]

Best implementation of my Launchpad X ever. I can not imagine how much work did you put in this project. Very appreciate it. Thanks.

[konXfront]

hi,
grateful for your work on this. i’m having problems with the launchpad pro mk3 on bitwig 4.1.6.

the drum machine interface seems to be working on a different protocol since the pads don’t correspond to the pads on the screen. is anyone else having the same problem?

best

k

[moss]

hi,
grateful for your work on this. i’m having problems with the launchpad pro mk3 on bitwig 4.1.6.

the drum machine interface seems to be working on a different protocol since the pads don’t correspond to the pads on the screen. is anyone else having the same problem?

best

k

Could you please elaborate a bit more? What do you mean by "the pads don’t correspond to the pads on the screen"? Did you select the drum sequencer mode on the Launchpad? Is a Bitwig drum machine device on the selected track?

[S950]

Push 2 in Ableton Live automatically maps whatever midi mappable parameter is clicked by mouse (VST synth knobs for example), to the left most knob on the push. It makes it easy to quickly adjust different parameters via the same knob without having to midi learn each time. Is it possible to do something similar with the Moss script?

Thanks,

[moss]

Push 2 in Ableton Live automatically maps whatever midi mappable parameter is clicked by mouse (VST synth knobs for example), to the left most knob on the push. It makes it easy to quickly adjust different parameters via the same knob without having to midi learn each time. Is it possible to do something similar with the Moss script?

Thanks,

This info is currently not available in Bitwig Studio. You can send your wish to Bitwig support.

[dnalord77]

Hello Jürgen,

Again, really grateful for your fantastic work on implementing controllers with Bitwig.

Found something in the Launchpad Pro Mk3 in DrivenByMoss v18.5 (haven't tested it on v19.0 as the track selection is considerably more important for me).

In note mode, when I am playing a melody/chord on the launchpad and change the octave with the up/down arrows, the note(s) cut off. This does not happen on the Launchpad Mini Mk3. In the launchpad mini, if I am holding a note/chord and I change the octave, the notes I am pressing continue playing. It is only until I press again that the change of octave becomes active.

Would be great to have the same behaviour in the pro as in the mini, as I tend to use the launchpad to perform/play.

Thank you again!

[moss]

Hello Jürgen,

Again, really grateful for your fantastic work on implementing controllers with Bitwig.

Found something in the Launchpad Pro Mk3 in DrivenByMoss v18.5 (haven't tested it on v19.0 as the track selection is considerably more important for me).

In note mode, when I am playing a melody/chord on the launchpad and change the octave with the up/down arrows, the note(s) cut off. This does not happen on the Launchpad Mini Mk3. In the launchpad mini, if I am holding a note/chord and I change the octave, the notes I am pressing continue playing. It is only until I press again that the change of octave becomes active.

Would be great to have the same behaviour in the pro as in the mini, as I tend to use the launchpad to perform/play.

Thank you again!

I tried it and I see the same behviour on both models. Notes are shut off when octave is changed, which is necessary since otherwise you would get hanging notes.
As a workaround you can either use a sustain pedal or use the fake sustain pedal on the lowest row (yellow button) which you can activate by pressing the Velocity button on the Pro Mk3.