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

[moss]

Hi, I'm using the generic flexi with an Akai MPK mini. Mainly I wanted to use the modes and map the rotaries to control track volumes, being able to switch to sets of 8 tracks. This somewhat works, but I'm having some issues. I've set a control to 'Modes: Item 1: Set Value'. When I use Relative (1-64 increments), the rotary only moves the volume in tiny amounts. If I then set 'Knob Sensitivity Default: +100' it is a bit better, but still requires a lot of knob turning. I tried the other knob modes and none work too well. One even makes both clockwise and counter-clockwise decrease the fader.

If I don't use modes and instead have Track: Track 1 Set Volume, it works better, but I have to set Relative (1-63 increments). The only problem is clockwise lowers the fader, and counter-clockwise raises it, and I'd like it opposite.

Ideally I'd like to use modes if I can get it working, to be able to switch to device modes, etc. But not sure how to fix the knob resolution issue.

Thanks.

I do not have that model but from looking at a picture of the device, aren't these absolute knobs?

It can be set to absolute or relative with the Akai configuration program. I tried both.

Any idea what I can try to resolve this? Happy to provide any more info.

Did you try again with the latest 12.3.1? I fixed an issue with relative CCs and clarified the naming of the different relative modes a bit.

[eliasy]

I was able to make the step sequencer work, partially. From this video I guessed the layout:

So I am missing the tags Sequencer, Poly Seq. Raindrop and Drum in my top row and the selection is inverted. Items on the bottom row are selected by the top pads below the display, while items on the top row are selected by the second pads below the display (see my picture "Clicking in notes " - you will see 4 highlight pads for the bottom row and 6 highlighted pads immediately below).


By clicking in the 4 pad on the second row (supposedly Drum), I am able to enter the Drum sequencer.
However, it is still not totally functional: selecting a note on the drum pad then selecting the respective timepad makes it sound a different note than the one that was selected. If I click again it adds what I think is delay. I can delete the original note, but not the delay by holding delete + pad.

Clicking in a timepad on the step sequencer

IMG_20210629_105426.jpg

The result - instead of selecting the pad it selected a previous pad and added delay (not sure).

IMG_20210629_105430.jpg

[eliasy]

Hi Moss! Thanks for your effort in this awesome extension, It is what makes bitwig the only linux viable DAW for me .

My problem: most things appear to work, but I am having some problems with the display and the step sequencer.

Hmm, this looks a bit like a hardware issue. Just to be sure I did a quick test with Push 1 and Linux but it worked fine for me.
If you have access to a Windows or Mac machine, you can try with the demo version of Ableton (which will also update your Firmware to the latest release).
Also try different USB ports and cables.

I will try that and report back .

[eliasy]

After installing Ableton Live 11 on a VM and updating the firmware on Push things improved.
Now the Sequencer is working.
But my display still doesn't show all the options nor the selection appears right.
Is there something I can do? I also tested with different cables and usb ports.

Check the display after pressing Notes:

IMG_20210629_120717.jpg

[moss]

After installing Ableton Live 11 on a VM and updating the firmware on Push things improved.
Now the Sequencer is working.
But my display still doesn't show all the options nor the selection appears right.
Is there something I can do? I also tested with different cables and usb ports.

Check the display after pressing Notes:
IMG_20210629_120717.jpg

Looks like the left upper area of the display is somehow broken.

[eliasy]

After installing Ableton Live 11 on a VM and updating the firmware on Push things improved.
Now the Sequencer is working.
But my display still doesn't show all the options nor the selection appears right.
Is there something I can do? I also tested with different cables and usb ports.

Check the display after pressing Notes:
IMG_20210629_120717.jpg

Looks like the left upper area of the display is somehow broken.

That was almost exactly right!
Thanks for the help Moss.

It was just a bad connection of the LCD tape.
I corrected it and now everything seems just fine.

I had to open my Push some time ago to remove the grease paint from the carcass (the mate finishing was peeling off), but when I reassembled it, the LCD display was functional but not perfect, and I hadn't noticed.

Besides the manual, is there an updated compendium/tutorial where I can see all the current features for the Push4Bitwig extension? It seems that a lot has changed over the years, so I am not sure on what to look for on the youtube channel.

Thanks again!

[valankar]

Hi, I'm using the generic flexi with an Akai MPK mini. Mainly I wanted to use the modes and map the rotaries to control track volumes, being able to switch to sets of 8 tracks. This somewhat works, but I'm having some issues. I've set a control to 'Modes: Item 1: Set Value'. When I use Relative (1-64 increments), the rotary only moves the volume in tiny amounts. If I then set 'Knob Sensitivity Default: +100' it is a bit better, but still requires a lot of knob turning. I tried the other knob modes and none work too well. One even makes both clockwise and counter-clockwise decrease the fader.

If I don't use modes and instead have Track: Track 1 Set Volume, it works better, but I have to set Relative (1-63 increments). The only problem is clockwise lowers the fader, and counter-clockwise raises it, and I'd like it opposite.

Ideally I'd like to use modes if I can get it working, to be able to switch to device modes, etc. But not sure how to fix the knob resolution issue.

Thanks.

I do not have that model but from looking at a picture of the device, aren't these absolute knobs?

It can be set to absolute or relative with the Akai configuration program. I tried both.

Any idea what I can try to resolve this? Happy to provide any more info.

Did you try again with the latest 12.3.1? I fixed an issue with relative CCs and clarified the naming of the different relative modes a bit.

Works great now, thanks!

[minortom]

Moss, off the wall code question that I will ask in this giant thread: when mapping user controls on Maschine Jam, how are you preventing slider touch from registering before slider position? I have a HarwdareButton matched to slider touch MIDI data that registers first (this part makes sense). I've tried temporarily setting its pressed/released action matchers to a nonsensical matcher, but then Bitwig simply maps the touch event as raw MIDI CC, as if it's getting passed straight through to Bitwig.

Couldn't tell easily from the code, thought I'd ask.

[artsense]

OSC is broken in Bitwig 4.0 beta 5
At least in my configuration @ DrivenByMoss-12.3.0-Bitwig

Thanks for the info. I can reproduce that, too. I reported it to Bitwig.

woohoo
fixed in beta6

moss.jpg

[moss]

Moss, off the wall code question that I will ask in this giant thread: when mapping user controls on Maschine Jam, how are you preventing slider touch from registering before slider position? I have a HarwdareButton matched to slider touch MIDI data that registers first (this part makes sense). I've tried temporarily setting its pressed/released action matchers to a nonsensical matcher, but then Bitwig simply maps the touch event as raw MIDI CC, as if it's getting passed straight through to Bitwig.

Couldn't tell easily from the code, thought I'd ask.

Please create a separate thread for such questions.

[luroc]

Hey,
I don't know if this is a regression or the intended behaviour and I just didn't notice before, but it disrupts my flow a bit on Push 1:
I just upgraded to Bitwig 3.3.10 / DrivenByMoss 12.3.1 and I noticed, that when I am in the User view and I touch and release the Master knob (upper right), I get thrown into Track view, instead of returning to User view.
Is that how it is supposed to work?

Edit: Apparently I'm not thrown to the Track view necessarily, but to whatever view I have been on before switching to User view.

[moss]

Hey,
I don't know if this is a regression or the intended behaviour and I just didn't notice before, but it disrupts my flow a bit on Push 1:
I just upgraded to Bitwig 3.3.10 / DrivenByMoss 12.3.1 and I noticed, that when I am in the User view and I touch and release the Master knob (upper right), I get thrown into Track view, instead of returning to User view.
Is that how it is supposed to work?

Edit: Apparently I'm not thrown to the Track view necessarily, but to whatever view I have been on before switching to User view.

Did a test but it jumps back to user mode for me. Sorry, no real idea here.

[sandrodc]

Hello folks.

Since this seems to be a thread with lots of brilliant minds knowledgeable of the KK, I thought of asking the question here: I have gone a long way into customising the Controller Panel to fit my needs, having managed to reassign, rename and add/delete individual controls and sections but I'm struggling to rename Pages.

So as it is the customisation is only half useful as I know that if I spend a few weeks without using a plug-in I will have forgotten what 'Page 1' or 'Page 14' mean :[]

The manual is very detailed on everything else but makes no mention of how to do this bit, which leads me to believe it can't be done.

Does anyone know?

[moss]

Hello folks.

Since this seems to be a thread with lots of brilliant minds knowledgeable of the KK, I thought of asking the question here: I have gone a long way into customising the Controller Panel to fit my needs, having managed to reassign, rename and add/delete individual controls and sections but I'm struggling to rename Pages.

So as it is the customisation is only half useful as I know that if I spend a few weeks without using a plug-in I will have forgotten what 'Page 1' or 'Page 14' mean :[]

The manual is very detailed on everything else but makes no mention of how to do this bit, which leads me to believe it can't be done.

Does anyone know?

In the editor for the remote control pages, click on the name of the page (the header) while holding down the Alt-key (on Windows/Linux). Haven't checked Mac but I guess it is option.

[sj1]

Hello,

I'm trying to get MPE to work with my launchpad pro mk3, but to no avail.
When checking it with midi monitor, I can see that the message is sent, but I can't for the life of me find the way to assign it.

I have poly aftertouch set to convert to "Poly aftertouch", and the latest driven by Moss and Bitwig Studio.

Edit:
Got it to work shortly after, while checking a yt video I had missed. One has to enable MPE from the launchpad when NOT connected to Bitwig. From there it's smooth sailing

In case others can use this info, the video mentioned above was probably this one here:




To get to the AFT setup page, on the LPP Mk3, hold down the small Setup button at the lower left corner, then touch the 3rd soft-button from the left along the bottom row (above the Solo button).