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

[moss]

Hey Moss.

I have an odd behaviour with my Push 2 in Bitwig.
When I have a synth in monophonic mode and I press a pad (keep it held down) then press a second pad all sounds good and as expected. But now when I release that second pad the sound reverts to the first pad (that is still being held down) HOWEVER the velocity is super low. I have tried with accent on/off and the behaviour is the same. But if I go to Ableton and try it, it works correctly. The behaviour I am expecting (and how it works in other DAWs I've tested) when you keep the first note held and press and release a second note, the sounds should revert back to the first note at the same velocity.
So I tested something else to be sure it was the Push 2 that was doing this. I simulated the same keypresses using Bitwig's piano roll and it works normally. So it just seems to be an issue with Push 2 only.
Please could you advise me? Maybe I have some setting wrong?

Thank you

Never experienced something like this. Can you give me a hint with which synth and sound you have this issue?

[jmg8]

I was testing it with Melda Production - MSoundFactory.
As for the sound, well if you load the synth and turn to monophonic mode and simply add a single OSC, it will behave in the way I described.
Thanks for the reply.

[zengel]

Hello ! I have found a bug on the push 2 with the Drum 64 layout.

when you put a Drum machine instrument on a track and add a pad with nothing ( Clic on "ok" without selecting something in the browser) . you have an empty pad.
While the drum machine is selected then you can move the pad put another color etc without bug. now add a sampler on the pad (with a wav preset or just a sampler) and move the pad without selecting the Drum machine (the sampler is unselected while you move the pad but the Drum machine neither). the current position of the pad is not refreshed on the push 2. select again the drum machine and it is still not refreshed .the colored pad on the push 2 is stucked in the position before you moved it without selecting the Drum machine. when you play on the colored pad , it stills play (and show) the old note before moving the pad on another. You can delete the drum machine and the bug does not disappear. The position of the colored pad on the Push 2 is not the one on bitwig when you add a new Drum machine on the same track (didn't try on another track) . then bitwig crash if i still continue to play with the bug ...

[moss]

I was testing it with Melda Production - MSoundFactory.
As for the sound, well if you load the synth and turn to monophonic mode and simply add a single OSC, it will behave in the way I described.
Thanks for the reply.

I am afraid I cannot help you with Melda. If you can reproduce it with a Bitwig stock plugin or I own all of NI, u-he and Omnisphere.

[avoca]

Hi Moss,

On the Launchpad Pro Mk3, if for example I am in Drum64 Note Mode, and I go to Session Mode to start recording on a given pad, and then I go back to Note Mode, I am brought to Scale Mode. (It takes 3 presses of "Note" to get back to Drum64). Is there a way to make it to go straight back to the mode I was in, i.e. Drum64 mode?

Thanks, and many thanks for your great extension.

Windows 7 and Ubuntu 20.04
Bitwig 3.2.7
Driven By Moss 10.6.4

Thanks, will be fixed in the next update!

Fantastic! Thanks

[zengel]

Hello ! I have found a bug on the push 2 with the Drum 64 layout.

when you put a Drum machine instrument on a track and add a pad with nothing ( Clic on "ok" without selecting something in the browser) . you have an empty pad.
While the drum machine is selected then you can move the pad put another color etc without bug. now add a sampler on the pad (with a wav preset or just a sampler) and move the pad without selecting the Drum machine (the sampler is unselected while you move the pad but the Drum machine neither). the current position of the pad is not refreshed on the push 2. select again the drum machine and it is still not refreshed .the colored pad on the push 2 is stucked in the position before you moved it without selecting the Drum machine. when you play on the colored pad , it stills play (and show) the old note before moving the pad on another. You can delete the drum machine and the bug does not disappear. The position of the colored pad on the Push 2 is not the one on bitwig when you add a new Drum machine on the same track (didn't try on another track) . then bitwig crash if i still continue to play with the bug ...

Forgot Spec : Windows 10 , bitwig 3.2.7, DrivenByMoss 10.6.4 .
Could you confirm if you can reproduce it or if it's specific to my computer. Then i will re-install Bitwig and the script to try to correct it . thanks

[moss]

Hello ! I have found a bug on the push 2 with the Drum 64 layout.

when you put a Drum machine instrument on a track and add a pad with nothing ( Clic on "ok" without selecting something in the browser) . you have an empty pad.
While the drum machine is selected then you can move the pad put another color etc without bug. now add a sampler on the pad (with a wav preset or just a sampler) and move the pad without selecting the Drum machine (the sampler is unselected while you move the pad but the Drum machine neither). the current position of the pad is not refreshed on the push 2. select again the drum machine and it is still not refreshed .the colored pad on the push 2 is stucked in the position before you moved it without selecting the Drum machine. when you play on the colored pad , it stills play (and show) the old note before moving the pad on another. You can delete the drum machine and the bug does not disappear. The position of the colored pad on the Push 2 is not the one on bitwig when you add a new Drum machine on the same track (didn't try on another track) . then bitwig crash if i still continue to play with the bug ...

Forgot Spec : Windows 10 , bitwig 3.2.7, DrivenByMoss 10.6.4 .
Could you confirm if you can reproduce it or if it's specific to my computer. Then i will re-install Bitwig and the script to try to correct it . thanks

Sorry, cannot reproduce that. But I doubt that reinstalling fixes that.
Please check if you see any exceptions in the javascript console and check the Bitwig log files for crash information.

[zengel]

Hello ! I have found a bug on the push 2 with the Drum 64 layout.

when you put a Drum machine instrument on a track and add a pad with nothing ( Clic on "ok" without selecting something in the browser) . you have an empty pad.
While the drum machine is selected then you can move the pad put another color etc without bug. now add a sampler on the pad (with a wav preset or just a sampler) and move the pad without selecting the Drum machine (the sampler is unselected while you move the pad but the Drum machine neither). the current position of the pad is not refreshed on the push 2. select again the drum machine and it is still not refreshed .the colored pad on the push 2 is stucked in the position before you moved it without selecting the Drum machine. when you play on the colored pad , it stills play (and show) the old note before moving the pad on another. You can delete the drum machine and the bug does not disappear. The position of the colored pad on the Push 2 is not the one on bitwig when you add a new Drum machine on the same track (didn't try on another track) . then bitwig crash if i still continue to play with the bug ...

Forgot Spec : Windows 10 , bitwig 3.2.7, DrivenByMoss 10.6.4 .
Could you confirm if you can reproduce it or if it's specific to my computer. Then i will re-install Bitwig and the script to try to correct it . thanks

Sorry, cannot reproduce that. But I doubt that reinstalling fixes that.
Please check if you see any exceptions in the javascript console and check the Bitwig log files for crash information.

It helped ! i had error on the console because of a path to a script i made long time ago . I think it had consequences on the push 2 script ? It seems to work now . Thanks !

[brunobeltran]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hi, sorry moss for double-posting, only saw the instructions to post here after I opened an issue on Github already!

I'll copy/paste what I said there:

Summary

After installing this extension, none of the buttons on my Launchpad Pro MK3 seem to control Bitwig Studio at all. Instead, it appears to largely function as it would if I added it as a generic midi keyboard, except that Bitwig appears to not receive input from certain pads (which pads changes with which mode but might correlate to a particular midi cc value?)

In the controller script console, pressing one of the notes that "doesn't work" with the extension installed results in:

```
Mini Note on ## should be handled in framework...
Mini Note off ## should be handled in framework...
```

What I've tried

I copied the `.bwextension` file for DrivenByMoss v10.6.4 I got [here](http://www.mossgrabers.de/Software/Bitw ... g.html#3.2 (http://www.mossgrabers.de/Software/Bitwig/Bitwig.html#3.2)) into `~/Bitwig Studio/Extensions`, and the extension automatically detects and adds the Pro to my list of controllers. Other than that, it's a branch new launchpad and a brand new bitwig install with nothing else in it.

Removing the extension verifies that these pads normally do work.

System info

Running Arch Linux, `cat /proc/version` says:

`Linux version 5.8.7-arch1-1 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000`

Bitwig's "about" says "Version: 3.2.7, Extension API Version: 12, Build date: 2020-08-11".



Let me know if there's anything I can do to help diagnose the issue! (I'm a MIDI/Bitwig neophyte, but will start trying to read the dev docs).

[porkloin]

Hi, sorry moss for double-posting, only saw the instructions to post here after I opened an issue on Github already!

I'll copy/paste what I said there:

Summary

After installing this extension, none of the buttons on my Launchpad Pro MK3 seem to control Bitwig Studio at all. Instead, it appears to largely function as it would if I added it as a generic midi keyboard, except that Bitwig appears to not receive input from certain pads (which pads changes with which mode but might correlate to a particular midi cc value?)

In the controller script console, pressing one of the notes that "doesn't work" with the extension installed results in:

```
Mini Note on ## should be handled in framework...
Mini Note off ## should be handled in framework...
```

What I've tried

I copied the `.bwextension` file for DrivenByMoss v10.6.4 I got [here](http://www.mossgrabers.de/Software/Bitw ... g.html#3.2) into `~/Bitwig Studio/Extensions`, and the extension automatically detects and adds the Pro to my list of controllers. Other than that, it's a branch new launchpad and a brand new bitwig install with nothing else in it.

Removing the extension verifies that these pads normally do work.

System info

Running Arch Linux, `cat /proc/version` says:

`Linux version 5.8.7-arch1-1 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000`

Bitwig's "about" says "Version: 3.2.7, Extension API Version: 12, Build date: 2020-08-11".



Let me know if there's anything I can do to help diagnose the issue! (I'm a MIDI/Bitwig neophyte, but will start trying to read the dev docs).

I don't have a Mk3, but my understanding is that the MIDI config is more complicated given that the Mk3 is designed to allow multiple MIDI out/in channels. Are you sure the Launchpad is communicating with Bitwig on the correct MIDI channel?

[porkloin]

Hey Moss!

Is there any possibility of adding a dedicated toggle for the “enable groove” button? It’s very nice to have the tempo and swing controls built in for the launchpad devices now, but I keep finding myself going to adjust the swing on a new project and then I realize I don’t have groove enabled. I am able to do the vast majority of my workflow on the controller but this is one area that sticks out where I reach for the mouse every time. On a related note, I also wonder whether it would be useful to be able to adjust other groove parameters (accent, phase, rate) via the controller.

[Wavethings]

Hi Moss
First of all I wanted to thank you for the enormous work you have done with the integration of the Akai Fire in Bitwig. Is awesome.

Now I wanted to ask if a couple of functions could be added to Shift mode.
Could you put two buttons to Duplicate Clip and duplicate content?
This is something that can greatly improve the workflow when we work on the Clip Launcher.

Thanks for all this great work.

[brunobeltran]

I don't have a Mk3, but my understanding is that the MIDI config is more complicated given that the Mk3 is designed to allow multiple MIDI out/in channels. Are you sure the Launchpad is communicating with Bitwig on the correct MIDI channel?

Yeah, in fact the extension *forces* the correct MIDI out/in channels to be used (if you try to choose a different one, it automagically creates a new "controller" entry in Bitwig using the correct one).

I am getting MIDI messages in Bitwig (again, some notes actually work), but none of the advertised extra functionality of the extension works, and the note values seem scrambled (and some are ignored...).

I also tried doing this on Windows, same bug.

The LP works on Ableton on that same Windows machine, so it's something specific to the extension....

[zengel]

Hello !
I have a request .
Would it be possible to make a "pseudo" gate function on the session pads ?
So that the clip play immediately (or depending the quantification) as long as i have my finger on a pad and stop immediately or depending on the quantification when i remove it ?
I really miss the gate function of Ableton ....
And we can activate it as an option (in the parameters of the push 2 ?)
Thanks for all Moss !
Have a good day !

[moss]

Hey Moss!

Is there any possibility of adding a dedicated toggle for the “enable groove” button? It’s very nice to have the tempo and swing controls built in for the launchpad devices now, but I keep finding myself going to adjust the swing on a new project and then I realize I don’t have groove enabled. I am able to do the vast majority of my workflow on the controller but this is one area that sticks out where I reach for the mouse every time. On a related note, I also wonder whether it would be useful to be able to adjust other groove parameters (accent, phase, rate) via the controller.

I thought about this in the past but decided you sometimes have to stop adding things
However, will put it on the todo list but no promises here if this will ever happen.