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

[apoclypse]

Hi,
wouldn't it be nice to have the LEDs of the Keys (wich are showing the actual scale etc.) on the Novation SL MK3 follow the track colors in BWS? Like in its sequencer mode, this would be very nice I think. Is this possible?

Best regards.

The light guide is sadly not programmable.

Hmm. Looked into the Novations SL MK 3 programmers guide and found this:AcroRd32_ARjnoKRoMo.png

Where can I find this Programmer's guide? I would like to take a look through it.

[FergusL]

Hello, thanks for the wonderful work.
Just got an APC Mini solely for drum sequencing and... you've got the Fire working since the last time I checked! Do you need testers and help for developing for the Fire?
Does the APC Mini support Drum 4 and Drum 8 mode? If so, how do you access these modes?

[AFranke]

Next problem with mapping parameters to a device page. Mapped the midi channel selector of a hardware device to a device page. If I move the knob it shows and set up wrong values.

The right Values should be:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16

What the script show in the display:
Ch 1,Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15

What the script sets up in the hardware device:
Keep Channel,Ch 1,Ch 2,Ch 3,Ch 4,Ch 5,Ch 6,Ch 7,Ch 8,Ch 9,Ch 10,Ch 11,Ch 12,Ch 13,Ch 14,Ch 15,Ch 16

Talked with the BWS Support about this:

was auf dem Display angezeigt wird, kommt aus dem Script, evtl. ist da einfach ein Eintrag verrutscht.

Mit freundlichen Grüssen,
Bitwig Technical Support Team

The bug is confirmed now and (hopefully) will be fixed soon.
BTW all parameters which map to a list are affected.

So this problem is fixed now with the BWS 3.2.2 update. BUT! Now mapped parameters in the Device Pages are not reflected in the SL MK3s display anymore. The always show the original parameter names while in other contoller displays (SL MK2/Push1) they show up correctly.

[AFranke]

Hi,
so yesterday I mapped some controls of Arturias SEM V to a bunch of Device Pages in BWS 3.2 (DrivenByMoss-9.10-Bitwig). But many of the can't be controlled via my Hardware (61SL MK2,Push 1). In concrete any Parameter in Arturias SEM V that is a "switch" can be mapped, but it does not react to changes from the hardware controllers. If I move the same parameter in the device page of BWS with my mouse all works fine. But not by moving a knob on one of my controllers.

Don't have the Arturia plugins, so cannot test that. But I played around a bit with switches on some other plugins which behaved a bit strange. It worked but a bit jumpy, so this could be caused by rounding error.
Parameter changing is currently a bit hacky in DBM since I switched not fully to the new hardware API, will look into this in the future but might take a bit.

This problem is fixed since the BWS 3.2.2 update as far I can see.

[soehngenetic]

It should work like this but I think there is a bug in Bitwig in that area, could be caching or update issue. Could you please check if it is working after restarting Bitwig?
If you can reproduce it reliably, please report to Bitwig.

Thanks for your fast reply! - I just checked it. If the VSTi is on a track and I push the device button on Push2, the individual names of the first controller page are shown like I modified them. But as soon as I activate the button named "Banks" to show the other controller pages, the names of the individual controllers switch back to the original controller-names of the VSTi.

Ah, great. Fixed!

Does that mean, you were able to fix it? - Will it then be part of a future script update and when will this be available?
Thanks for all!

[moss]

Does that mean, you were able to fix it? - Will it then be part of a future script update and when will this be available?

These are actually 2 bugs. I was calling the wrong method which turns out to be buggy (reported to Bitwig and will be fixed). I call now again the correct method which fixes the issue as well.
The update will be available when its ready There will be lots of new stuff coming so it takes a bit longer than usual.

[AFranke]

Hi,
wouldn't it be nice to have the LEDs of the Keys (wich are showing the actual scale etc.) on the Novation SL MK3 follow the track colors in BWS? Like in its sequencer mode, this would be very nice I think. Is this possible?

Best regards.

The light guide is sadly not programmable.

Hmm. Looked into the Novations SL MK 3 programmers guide and found this:AcroRd32_ARjnoKRoMo.png

Where can I find this Programmer's guide? I would like to take a look through it.

Technical Docs: https://customer.novationmusic.com/en/s ... d_type=all

[moss]

Hello, thanks for the wonderful work.
Just got an APC Mini solely for drum sequencing and... you've got the Fire working since the last time I checked! Do you need testers and help for developing for the Fire?
Does the APC Mini support Drum 4 and Drum 8 mode? If so, how do you access these modes?

No, it does only support the normal drum mode. Fire is actually already finished but I have a blocker on Macos, which I would like to have a solution for first but not sure if this will happen.

[FergusL]

No, it does only support the normal drum mode. Fire is actually already finished but I have a blocker on Macos, which I would like to have a solution for first but not sure if this will happen.

I'd like to take a look at implementing it, most of the code probably already exists for Launchpad and Push. From my understanding, the "fader ctrl" buttons on APC Mini in drum sequencer mode aren't used, they could serve to select normal/drum4/drum8 modes.
Is there another place to discuss specifically about code/development?

[Tj Shredder]

Is there another place to discuss specifically about code/development?

It is this place, but not necessarily this thread...

[dot.solenoid]

Hello Jürgen,

Using on/off buttons on VST's (with the push 2) is not useful. Setting the rotation to max (on) or 0 (off) with the mouse is no problem. With the push, I keep rotating knobs and sometimes it's able to set to max but most of the time i need to use the mouse. rotary knobs work fine with normal values but with on and on/off switches the script seems to wait for a return value.

Would it be possible to add a double-tap input feature on each rotary knob to set it to the max (on), double-tab again to set to zero (off)? Alt: shift double-tap ?

[turbo_kev]

Hi mr MOSS
since I updated the extension to 9.10, 10
my icon platform m+ is no longer working correctly
the solo / mute / record buttons don't work, but they do light up if I use the same buttons on the track in bitwig
also the play button is a bit temperamental sometimes you need to hold it down to make it work

cheers
kev

[moss]

DrivenByMoss 10.0 is released!

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

• Requires Bitwig 3.2+
• The manual has now a known issues section
• New: Support for Akai Fire
  • Note: The display update of the Akai Fire is very slow on Macos and makes it nearly unusable
• New: Support for Native Instruments Maschine Mk3
• Akai APC40 / APC40mkII
  • Fixed: User mode did not work
• Maschine Mikro Mk3
  • New: Show more on-screen notifications (Tap Tempo, Fixed Velocity, value change speed)
  • New: Stop + Pad Mode - Selects the previous base note of the scale.
  • New: Stop + Keyboard - Selects the next base note of the scale.
  • New: Stop + Chords - Selects the previous note layout.
  • New: Stop + Step - Selects the next note layout.
  • New: Stop + Plug-In - Toggle the window (if any) of the selected device (if any).
  • New: Sampling - Brings up the Slice to Drum Machine dialog.
  • New: Stop + Sampling - Bring up the Slice to Multi-sample dialog.
  • New: Auto - Toggle write arranger automation.
  • New: Stop + Auto - Toggle write clip launcher automation.
  • New: Lock - Toggle arranger overdub.
  • New: Stop + Lock - Toggle clip launcher overdub.
  • New: Stop + Projects - Save the project.
  • New: Tap - Tap Tempo
  • New: Stop + Tap - Toggle metronome
  • Fixed: FX and Master track were missing in Select, Solo and Mute modes
• Push 2
  • New: Increased text size of list elements
• SL MkIII
  • Fixed: Updated MIDI port lookup names on Macos

Here are tutorial videos for the newly supported devices:



Enjoy!

[krtvu]

Hi Jürgen,
Thank you very much for integrating support for Maschine MK3!
I just installed the script and there seems to be a problem with the sequence of notes of the scale on the pads in play mode (no semitones and note F in duplicate in particular). Button increments does not seem to allow fine adjustment (example: impossible to reset the volume to 0db). Is there a way to fix this?
Thank you again for this great advance

[moss]

Hi Jürgen,
Thank you very much for integrating support for Maschine MK3!
I just installed the script and there seems to be a problem with the sequence of notes of the scale on the pads in play mode (no semitones and note F in duplicate in particular). Button increments does not seem to allow fine adjustment (example: impossible to reset the volume to 0db). Is there a way to fix this?
Thank you again for this great advance

Both are already on my TODO list for the Maschine (as many more details). I just wanted to release it since many users have been waiting for this.

But you can change the scale layout and activate chromatic mode (see the manual).
Also you can reset parameters by holding the Erase button and touching the knob.