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

[LarsDaniel]

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.

So in Bitwig 5 I get to choose? That is great.

[joris.roling]

I stand corrected...

[moss]

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 ?

I just tried rephrase it a bit in the manual to make clearer. What you need to do is this:
1) Select the Session mode
2) Activate Shift mode
3) Activate Duplicate (blue button in the first column)
4) Exit Shift mode
5) Press the pad with the clip you want to copy.
6) Press a pad with an empty (!) slot. You can repeat step 5) several times until you select an empty slot.

[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

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.

Moin Jürgen.
Yes, I checked this of course. But the ports are not blocked anyway. They close and reopen immediately, if they were blocked, Bitwig couldn't open then. We all know what's happening if the ports were blocked, we all know the nice warning message that comes up in Bitwig, if so.
And the error is just coming up if the controllers are attached to the extension, as I said so many times before, it has nothing to do with any hardware problem (USB Port or Hub, low power etc). If I use a different script/extension all works fine. What bothers me is, that I can't debug it by myself. And because I'm the only one where it happens, the support has no priority in my case.
So finally, I think I have to go back to Ableton Live, where my setup just works. What makes me really sad, because I hate Ableton Live for many other reasons.

Best regards
Andreas

[moss]

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.

Thanks for reporting! Seems to somehow got lost, will be added again in the next update!

[moss]

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.

Not sure yet since the API is also not fully finalized.

[moss]

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)

All controllers which can "speak" MCU can be used with my MCU implementation.

[moss]

Moin Jürgen.
Yes, I checked this of course. But the ports are not blocked anyway. They close and reopen immediately, if they were blocked, Bitwig couldn't open then. We all know what's happening if the ports were blocked, we all know the nice warning message that comes up in Bitwig, if so.
And the error is just coming up if the controllers are attached to the extension, as I said so many times before, it has nothing to do with any hardware problem (USB Port or Hub, low power etc). If I use a different script/extension all works fine. What bothers me is, that I can't debug it by myself. And because I'm the only one where it happens, the support has no priority in my case.
So finally, I think I have to go back to Ableton Live, where my setup just works. What makes me really sad, because I hate Ableton Live for many other reasons.

Best regards
Andreas

I am afraid I have no idea what I could do about it.

[AFranke]

Moin Jürgen.
Yes, I checked this of course. But the ports are not blocked anyway. They close and reopen immediately, if they were blocked, Bitwig couldn't open then. We all know what's happening if the ports were blocked, we all know the nice warning message that comes up in Bitwig, if so.
And the error is just coming up if the controllers are attached to the extension, as I said so many times before, it has nothing to do with any hardware problem (USB Port or Hub, low power etc). If I use a different script/extension all works fine. What bothers me is, that I can't debug it by myself. And because I'm the only one where it happens, the support has no priority in my case.
So finally, I think I have to go back to Ableton Live, where my setup just works. What makes me really sad, because I hate Ableton Live for many other reasons.

Best regards
Andreas

I am afraid I have no idea what I could do about it.

Maybe it's a problem like this, wich was fixed in beta 3:

Nektar controller extensions: were often crashing instantly [32009]

Just thinking...

Andreas

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

Thanks for reporting! Seems to somehow got lost, will be added again in the next update!

Great!
Thanks for the reply!

[machinesworking]

OK have to ask, are we getting a Bitwig 5 beta version or are we going to have to wait until it's out of beta?

[mevla]

How does the Duplicate function works on the Launchpad Mini ?

I just tried rephrase it a bit in the manual to make clearer. What you need to do is this:
1) Select the Session mode
2) Activate Shift mode
3) Activate Duplicate (blue button in the first column)
4) Exit Shift mode
5) Press the pad with the clip you want to copy.
6) Press a pad with an empty (!) slot. You can repeat step 5) several times until you select an empty slot.

Here's what I got on the Launchpad Mini mk3 and script version 19.2.1.

3) The blue button (5th from top 1st column) starts to blink.
4) I press again on 'User' to exit Shift mode, hence back to Session mode,
5) I press the pad of an existing clip,
6) I press the pad of an empty slot right beside it on same track.

Nothing happens, no clip is copied. Bitwig shows that the empty slot was chosen. I go back to Shift mode, the Blue pad is still blinking.

At step 5, should the Launchpad pressed pad change colour or otherwise show that it was selected to be copied ?

OK, got it, but only in part. Step 6) should be :

6) _Double-press_ (eg. like double click) the empty pad that will receive the copy.

The problem now is that even though I redo the whole procedure using other source clips, it's always the one that I first have chosen that gets copied.

Solved : the pad to copy must also be double-pressed. The actual source and target selections have to be chosen by double-pressing, not regular one-time press. At least on the Launchpad Mini mk3 with current firmware and script version 19.2.1 on Bitwig 4.4.10 (Linux).

[SDoo]

Moin Jürgen.
Yes, I checked this of course. But the ports are not blocked anyway. They close and reopen immediately, if they were blocked, Bitwig couldn't open then. We all know what's happening if the ports were blocked, we all know the nice warning message that comes up in Bitwig, if so.
And the error is just coming up if the controllers are attached to the extension, as I said so many times before, it has nothing to do with any hardware problem (USB Port or Hub, low power etc). If I use a different script/extension all works fine. What bothers me is, that I can't debug it by myself. And because I'm the only one where it happens, the support has no priority in my case.
So finally, I think I have to go back to Ableton Live, where my setup just works. What makes me really sad, because I hate Ableton Live for many other reasons.

Best regards
Andreas

I am afraid I have no idea what I could do about it.

Maybe it's a problem like this, wich was fixed in beta 3:

Nektar controller extensions: were often crashing instantly [32009]

Just thinking...

Andreas

Hi, I'm afraid I have to agree with AFranke. I too own a Push 1 and am experiencing incidental MIDI Port drop outs using the latest DrivenByMoss builds where the Push midi port closes and opens in a very short time. I'm back to an older version (v15.4) and that solved the problems!! It's a pity I can't use the latest and greatest, but perhaps it's a possibility for AFranke to stay here...

[teknoman]

edited, found what I needed.

[moss]

How does the Duplicate function works on the Launchpad Mini ?

I just tried rephrase it a bit in the manual to make clearer. What you need to do is this:
1) Select the Session mode
2) Activate Shift mode
3) Activate Duplicate (blue button in the first column)
4) Exit Shift mode
5) Press the pad with the clip you want to copy.
6) Press a pad with an empty (!) slot. You can repeat step 5) several times until you select an empty slot.

Here's what I got on the Launchpad Mini mk3 and script version 19.2.1.

3) The blue button (5th from top 1st column) starts to blink.
4) I press again on 'User' to exit Shift mode, hence back to Session mode,
5) I press the pad of an existing clip,
6) I press the pad of an empty slot right beside it on same track.

Nothing happens, no clip is copied. Bitwig shows that the empty slot was chosen. I go back to Shift mode, the Blue pad is still blinking.

At step 5, should the Launchpad pressed pad change colour or otherwise show that it was selected to be copied ?

OK, got it, but only in part. Step 6) should be :

6) _Double-press_ (eg. like double click) the empty pad that will receive the copy.

The problem now is that even though I redo the whole procedure using other source clips, it's always the one that I first have chosen that gets copied.

Solved : the pad to copy must also be double-pressed. The actual source and target selections have to be chosen by double-pressing, not regular one-time press. At least on the Launchpad Mini mk3 with current firmware and script version 19.2.1 on Bitwig 4.4.10 (Linux).

I just made some changes in that area, so maybe I fixed this unintentionally. Let's see...