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

[AndyTuke]

How are you planning on implementing the Alt clip launch feature?

[Apheo]

Is there a way to access Bitwig controller script and make some changes?

[PieBerger]

Is there a way to access Bitwig controller script and make some changes?

The source code is all up on Github

https://github.com/git-moss/DrivenByMoss

[moss]

How are you planning on implementing the Alt clip launch feature?

Most of it is already done. Basically it is button combinations with Shift/Select depending on what is available on a specific controller.

[moss]

Is there a way to access Bitwig controller script and make some changes?

The source code is all up on Github

https://github.com/git-moss/DrivenByMoss

and Bitwigs' code is here: https://github.com/bitwig/bitwig-extensions

[AFranke]

...

AKAI MPK mini MK3, Arturia Keystep Pro and Arturia Beatstep Pro, which are also connected to the same USB-Hub were unaffected, they are connected via the Bitwig Generic script/extension.

Best regards
Andreas

Is this Windows 11?

Yes, it is.

I reported this to Bitwig.

So, I hoped that my problem with the extension would be gone in 5.0 beta, but unfortunately, it still exists.

I connected the SLMK3 and the Push to the extension, my APC40 I was connected via "Keyboard +8 Knobs" Bitwig stock script/extension (has no useful function though, but I only wanted to show up, that it will not "reset" like it would, if it was used with your extension). And this is how it looks now, if it's happening now:

Code: Select all

Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Closing MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Opening MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Closing MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Opening MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false

It's closing and immediately reopens the Push and the SLMK3, but not the APC40. Here you can see, what controllers were attached at the startup:

Code: Select all

Opening MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Opening MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: KeyStep Pro MIDI IN, osName: KeyStep Pro MIDI IN, isInput: true
Opening MIDI device: name: Arturia BeatStep Pro, osName: Arturia BeatStep Pro, isInput: true
Opening MIDI device: name: MPK mini 3, osName: MPK mini 3, isInput: true
Opening MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Opening MIDI device: name: Akai APC40, osName: Akai APC40, isInput: true

It's so frustrating.

Best regards
Andreas

[mevla]

Hello !

The manual says :

"Duplicate - Always duplicates the first selected clip on the current track if pressed with no other button."

How does the Duplicate function works on the Launchpad Mini ? When a clip is selected on a track in the Arranger, the Duplicate button (Shift + purple pad 1st column) is pressed and starts blinking, Bitwig shows 'Duplicate Active'. No duplication of the clip has yet occurred. Then what is the next expected action ? I tried clicking somewhere else on a track but still no copy is made.

OK, got it for the tracks. One activates Duplication then goes back to 'User' where a column of blue pads at the right indicates which track should be duplicated. Is it possible to also duplicate only clips ?

[KTlin]

Hi Moss
There seems to be a bug in the script for the Akai APC40 (the first one, not the MK2) regarding the A|B buttons. In the manual it says "A|B buttons (on first version press Shift+RecArm)" and I tried that but nothing happens.

[xtreme sounds]

hi sir with the new project remote settings in bitwig 5, how will the generric flexi work? what I would like to do is use my digitakts 8 knobs which are currently set to send on cc 70-78. But what I want it to have it grab whatever 8 knobs are in focus in bitwig. Any ideas how to make it instant and flexible?

The other catch it that the digitakt can send these messages for 8 different midi channels. yikes. it seems like a big setup in flexi.

[AlQuzMar]

As for bugs, for some reason after enabling controller script, drop-down menus become suppressed, generally right and middle-click actions stop working as well. if I try to use drop-down menus on mappings of gamepad controller it'll start learn-mapping to CC29 for some reason, or some other random CC. I can make a video example if you can't reproduce this. Given that there were some changes to API since 4.4 release, it's not really surprising that something breaks like that

Yes, a video would be helpful.

Alright, after few days tried again and it happened after few minutes of playing with this gamepad (it's Gulikit king kong 2 pro) except after trying to disable script (which makes bug go away) and then re-enable it, Bitwig just crashed, here's video:
https://clipchamp.com/watch/7tZ6rN9vNGE

It's a bit uncool to run a record label and use a pirated Bitwig, don't you think?

[jekblad]

Is it possible to use mackie protocol on other controllers to have them “work” with driven by moss?

I would like to use atom SQ from PreSonus with mackie protocol, connect as behringer x touch and have the screen tell me what the encoders are doing (like on behringer x touch)

[moss]

...

AKAI MPK mini MK3, Arturia Keystep Pro and Arturia Beatstep Pro, which are also connected to the same USB-Hub were unaffected, they are connected via the Bitwig Generic script/extension.

Best regards
Andreas

Is this Windows 11?

Yes, it is.

I reported this to Bitwig.

So, I hoped that my problem with the extension would be gone in 5.0 beta, but unfortunately, it still exists.

I connected the SLMK3 and the Push to the extension, my APC40 I was connected via "Keyboard +8 Knobs" Bitwig stock script/extension (has no useful function though, but I only wanted to show up, that it will not "reset" like it would, if it was used with your extension). And this is how it looks now, if it's happening now:

Code: Select all

Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Closing MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Opening MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Closing MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Closing MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Closing MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Closing MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Opening MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false

It's closing and immediately reopens the Push and the SLMK3, but not the APC40. Here you can see, what controllers were attached at the startup:

Code: Select all

Opening MIDI device: name: MIDIIN2 (Novation SL MkIII), osName: MIDIIN2 (Novation SL MkIII), isInput: true
Opening MIDI device: name: Novation SL MkIII, osName: Novation SL MkIII, isInput: true
Opening MIDI device: name: MIDIOUT2 (Novation SL MkIII), osName: MIDIOUT2 (Novation SL MkIII), isInput: false
Opening MIDI device: name: KeyStep Pro MIDI IN, osName: KeyStep Pro MIDI IN, isInput: true
Opening MIDI device: name: Arturia BeatStep Pro, osName: Arturia BeatStep Pro, isInput: true
Opening MIDI device: name: MPK mini 3, osName: MPK mini 3, isInput: true
Opening MIDI device: name: MIDIIN2 (Ableton Push), osName: MIDIIN2 (Ableton Push), isInput: true
Opening MIDI device: name: MIDIOUT2 (Ableton Push), osName: MIDIOUT2 (Ableton Push), isInput: false
Opening MIDI device: name: Akai APC40, osName: Akai APC40, isInput: true

It's so frustrating.

Best regards
Andreas

Did you check if there is any kind of MIDI tool active on your system which might block these ports? This is the only time I saw such error reports. If not, I can only suggest to try Bitwig support.

[LarsDaniel]

Hi Jürgen,
I have a question in the "luxury" department: It is about the big rectangle around the eight tracks in focus. For some time, for me it has been red. Now after updating to the newest DrivenByMoss it is a very bright green. I just happen to like the red rectangle a LOT more. Is there a way to get the red back?

[joris.roling]

Is there a way to get the red back?

Check the top constrols in the Controllers (in Settings) assignment of your controller, it has a color chooser, pick red

[moss]

Is there a way to get the red back?

Check the top constrols in the Controllers (in Settings) assignment of your controller, it has a color chooser, pick red

In Bitwig 5, yes. Prior to 5 it is randomly picked by Bitwig, no way to change that.