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

[moss]

Hey Jurgen, thanks for your work!
I'm using your script on icon p1-m+ extender and it works very well, better than Bitwig one's.
there's only one thing I think it's missing, I can't figure out the way to switch between devices pages controls, while in Bitwig's you can switch between pages with up/down function it doesn't in yours.

Also, it would be nice to take advantage of the extender(/s) to show more than one page at the time.
Thanks for your time.

They are changed with the CHANNEL LEFT/RIGHT buttons. If I see that correctly iCON did not add these buttons to the P1-M?! But you should be able to program them on this new touch display.

You are right, i felt like a bad person after re-reading the manual and realizing i missed it, sorry for that.

Is the possibility of showing more than one bank at time something that can be implemented?

Thanks for your work and have a good day!

Not sure which bank you are asking about.

[brainztain]

Hello Mr. Moss and thank you for sharing your creation.

On Akai Fire, bitwig crashes when changing note lengths in note edit mode with the knobs.

This happens if notes overlap after increasing their length. The notes also disappear on the software but not on the Akai fire. The crash happens only sometimes after notes disappear.

I've tried latest two versions and got the same results. I've also searched here and found one mention of it but no replies.

Any solutions for this?

Thanks again!

Please give some specific steps to reproduce this. I fiddled around with this a bit but could not create a crash.

I think I found the exact way to reproduce it on Windows 11, Bitwig 5.2

1. Create new project, cear all tracks, load empty drum machine.
2. Create a 1-bar clip via alt+rec.
3. Select any pad and program in 16 16th notes.
4. At this point you may want to clone this clip several times to test the bug again if the crash doesn't happen in 1st try.
5. In currently playing clip, select all 16 notes via alt+step.
6. Turn 3rd knob left, effectively shortening the duration of all notes.
7. Turn 3rd knob right, this will always cause overlapping notes to get wiped out and *sometimes* (about 50% of the time) there will be a crash. The crash *seems* to happen more frequently if the knob is turned faster to the right.

Update: also managed to reproduce the crash while not playing. (While bitwig's sequencer is completely stopped)

[moss]

Hello Mr. Moss and thank you for sharing your creation.

On Akai Fire, bitwig crashes when changing note lengths in note edit mode with the knobs.

This happens if notes overlap after increasing their length. The notes also disappear on the software but not on the Akai fire. The crash happens only sometimes after notes disappear.

I've tried latest two versions and got the same results. I've also searched here and found one mention of it but no replies.

Any solutions for this?

Thanks again!

Please give some specific steps to reproduce this. I fiddled around with this a bit but could not create a crash.

I think I found the exact way to reproduce it on Windows 11, Bitwig 5.2

1. Create new project, cear all tracks, load empty drum machine.
2. Create a 1-bar clip via alt+rec.
3. Select any pad and program in 16 16th notes.
4. At this point you may want to clone this clip several times to test the bug again if the crash doesn't happen in 1st try.
5. In currently playing clip, select all 16 notes via alt+step.
6. Turn 3rd knob left, effectively shortening the duration of all notes.
7. Turn 3rd knob right, this will always cause overlapping notes to get wiped out and *sometimes* (about 50% of the time) there will be a crash. The crash *seems* to happen more frequently if the knob is turned faster to the right.

Update: also managed to reproduce the crash while not playing. (While bitwig's sequencer is completely stopped)

Thanks, I could reproduce it and did report it to Bitwig.

[moss]

DrivenByMoss 24.5 is online!

Get it from https://www.mossgrabers.de

• New: Added support for APCmini mk2.
• New: Updated to Bitwig API 19.
• APCmini mk1
  • New: Added option to toggle 'Notify played chords' on/off.
• Fire
  • Fixed: Drum 64 view: Shifting the notes up/down with select knob did not work.
• Fire, Launchpad, Push
  • Fixed: Drum 64 view: Notes were not in sync with pad colors.
• Push
  • Fixed: Drum XoX view was missing from preferred view selection in settings.

Enjoy!

[xtreme sounds]

thanks for you work on this stuff. definitely a labor of love

[LayersOfSilence]

Thanks for updating, Jurgen!
As i can see from a manual for Launchpad pro mk3.

Shift Mode
If you press and release the Shift button the grid changes to the Shift mode. If you keep the Shift button
pressed and execute one of the functions of this mode, it will close automatically when the Shift button is
released (except in the Session mode).

But for now it's not work as intended i think. If i press shift and execute alternative function of a button (for example Record or Duplicate) shift menu is still active. Or is it a normal behavior? Anyway it's a bit annoying

Launchpad pro mk3 with laterst firmware, DrivenByMoss 24.4 and 24.5.

[xtreme sounds]

Ableton just made something that looks like the akai fire. Called Move

[AFranke]

Moin Jürgen,
did you get your hands on a Korg Keystage (49/61) Midi keyboard so far? I ordered one today because it has polyphone aftertouch and I realized that there is support in Ableton for this thing. But as usual there is no native support in Bitwig, as far as I know.

[moss]

Moin Jürgen,
did you get your hands on a Korg Keystage (49/61) Midi keyboard so far? I ordered one today because it has polyphone aftertouch and I realized that there is support in Ableton for this thing. But as usual there is no native support in Bitwig, as far as I know.

Sorry, no.

[AFranke]

Moin Jürgen,
did you get your hands on a Korg Keystage (49/61) Midi keyboard so far? I ordered one today because it has polyphone aftertouch and I realized that there is support in Ableton for this thing. But as usual there is no native support in Bitwig, as far as I know.

Sorry, no.

Damn...

[SDoo]

Hi Jurgen, Related to 24.5:
Push - Fixed: Drum XoX view was missing from preferred view selection in settings.

My Push 1 gives me a missing view name. I guess that should be the XoX view??
I'm on Bitwig 5.2.4 btw..

 

[moss]

Hi Jurgen, Related to 24.5:
Push - Fixed: Drum XoX view was missing from preferred view selection in settings.

My Push 1 gives me a missing view name. I guess that should be the XoX view??
I'm on Bitwig 5.2.4 btw..

 

Will be fixed in the next update...

[darougeadam]

Hey Jurgen, thanks for your work!
I'm using your script on icon p1-m+ extender and it works very well, better than Bitwig one's.
there's only one thing I think it's missing, I can't figure out the way to switch between devices pages controls, while in Bitwig's you can switch between pages with up/down function it doesn't in yours.

Also, it would be nice to take advantage of the extender(/s) to show more than one page at the time.
Thanks for your time.

They are changed with the CHANNEL LEFT/RIGHT buttons. If I see that correctly iCON did not add these buttons to the P1-M?! But you should be able to program them on this new touch display.

You are right, i felt like a bad person after re-reading the manual and realizing i missed it, sorry for that.

Is the possibility of showing more than one bank at time something that can be implemented?

Thanks for your work and have a good day!

Not sure which bank you are asking about.

I'm talking about "device pages"

[moss]

Hey Jurgen, thanks for your work!
I'm using your script on icon p1-m+ extender and it works very well, better than Bitwig one's.
there's only one thing I think it's missing, I can't figure out the way to switch between devices pages controls, while in Bitwig's you can switch between pages with up/down function it doesn't in yours.

Also, it would be nice to take advantage of the extender(/s) to show more than one page at the time.
Thanks for your time.

They are changed with the CHANNEL LEFT/RIGHT buttons. If I see that correctly iCON did not add these buttons to the P1-M?! But you should be able to program them on this new touch display.

You are right, i felt like a bad person after re-reading the manual and realizing i missed it, sorry for that.

Is the possibility of showing more than one bank at time something that can be implemented?

Thanks for your work and have a good day!

Not sure which bank you are asking about.

I'm talking about "device pages"

If you are asking about the 8 parameter limitation, it is the most requested feature. Write to Bitwig and join the choir

[Dirkitator]

Hallo Jürgen,

gestern habe ich ein Komplete Kontrol M32 gekauft. Nun bin ich traurig, weil es nicht so funktioniert, wie von mir erhofft. Mir ist es wichtig, die Remotes bedienen zu können. Leider kann ich dort nicht in den Pages blättern. Wie von dir in der Anleitung beschrieben, funktionieren die Pagetaster des M32 nicht.

Ich möchte daher einen anderen Workflow vorschlagen:
Wenn ich im Device/Parameter Mode bin, dann ist es zumindest mir sehr unwichtig den Playback Cursor zu bewegen. Kannst Du das bitte so umändern, dass ich im Device-/Parameter Mode mit dem Drehen des Hauptencoders in den Pages der Remotes blättern kann?

Wenn ich zwischen Projekt-, Track- und Device Remotes schalten möchte, finde ich es sehr irritierend, dass Die Auswahl entgegengestzt zum Drücken des Encoders läuft.
Befinde ich mich zum Beispiel in der Projektremote, muss ich den Encoder nach links drücken, um nach rechts zur Trackremote zu gelangen.

Zum anderen ist mir aufgefallen, dass in Bitwig nicht die Tracks angewählt werden, wenn ich die Encoder berühre. Im M32 werden mir dann die entsprechenden Daten der Tracks angezeigt, aber in Bitwig wird nicht der entsprechende Track angewählt.

Liebe Grüße, Dirk



English translation:

yesterday I bought a Komplete Kontrol M32. Now I'm sad because it doesn't work as I had hoped. It is important for me to be able to operate the remotes. Unfortunately, I can't scroll through the pages there. As you describe in the instructions, the page buttons on the M32 don't work.

I would therefore like to suggest a different workflow:
When I'm in Device/Parameter mode, moving the playback cursor is very unimportant, at least to me. Can you please change this so that I can scroll through the pages of the remotes by turning the main encoder in device/parameter mode?

When I want to switch between project, track and device remotes, I find it very irritating that the selection runs in the opposite direction to pressing the encoder.
For example, if I am in the project remote, I have to press the encoder to the left to go to the track remote on the right.

On the other hand, I have noticed that the tracks are not selected in Bitwig when I touch the encoder. The corresponding track data is then displayed in the M32, but the corresponding track is not selected in Bitwig.

Kind regards, Dirk