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

[KTlin]

Hi. I have an issue using the Akai APC40 (mk 1) in Bitwig. The footswitch pedal I have connected to the APC doesn't do anything. It's supposed to "create a new clip on the selected track and slot, start play and enable overdub" but it doesn't do anything when pressed. I have it connected to the Footswitch 2 input, I'm using the latest DrivenByMoss extension and I'm on Bitwig 4.4. Also note that the pedal is working, there's nothing wrong with it. I can midi-map it to parameters in Bitwig and it works. Also it works in Ableton Live as expected (it starts playing/recording the selected clip when pressed).

And another problem: every time I open Bitwig the APC starts in Play mode, not in Session mode! Why is that? Isn't the Session mode supposed to be the default mode? This is quite frustrating!

[Jmf1928]

Hi. I've had no problem getting my Push 1 working with DrivenByMoss for Bitwig in the past, but currently I'm not getting expected functionality out of the arrow keys. I feel like maybe I'm just missing something obvious, but the left/right keys are never switching through the tracks. Sometimes they're shifting the full select of blocks, but never the individual selected track. The arrow keys on my keyboard move the selection no problem, and the push reflects the change. On the most recent of the extension as well as 4.4.2 on Bitwig. Am I missing something obvious? I have read the manual.

That was highly requested that the cursor keys directly switch pages since you can access the tracks of the page already with the buttons below the display.

I think I’ve gotten the hang of it now. A number of my tracks were missing when I had things grouped. I’ve ungrouped everything and am able to select any track, but I’m also wondering if I’m missing something functionally.

[moxxi]

When I installed DrivenByMoss and connected my Launchpad Pro Mk3, the Launchpad is not reset after quitting Bitwig.
What could cause this?

See the previous post.

Same problem here, but with DrivenByMoss 18.1.0 everything was fine before 4.4.2, so it’s not an issue with Moss extension, clearly Bitwig changed something after version 4.4.

btw temporary workaround for Launchpad Pro MK3 and maybe with other controllers - on macOS and if you're using Logic Pro, just start Logic Pro and exit it, it will reset the controller.

[moss]

I found a little issue. When either the drum 4 or drum 8 sequencers are active and I move sequncer page up/down with the octave up/down buttons, on the display it says I move by 16 notes, which is wrong and little confusing.

Can't see anything wrong. When I press Octave up it say "E1.." and if I down again "C1".

[moss]

Dear Moss,

I just updated to bitwig 4.4.2 and also to DrivenByMoss 18.1.0. I use Windows 10 Pro 64bit. I use the Akai APC40 mk1. Thank you for making the plug-in available to us.

Everything works fine, except:

After adding and selecting a Drum Machine, I can play the drum sounds in 'Play Mode'. I can see the MIDI-Note indicator on the left blinking, the note gets selected, it plays the sound. Everything as it should.

Good catch! Interesting noone else did notice this before, seems not that many people use MkI anymore.

Will be fixed in the next update!

[moss]

Hi. I have an issue using the Akai APC40 (mk 1) in Bitwig. The footswitch pedal I have connected to the APC doesn't do anything. It's supposed to "create a new clip on the selected track and slot, start play and enable overdub" but it doesn't do anything when pressed. I have it connected to the Footswitch 2 input, I'm using the latest DrivenByMoss extension and I'm on Bitwig 4.4. Also note that the pedal is working, there's nothing wrong with it. I can midi-map it to parameters in Bitwig and it works. Also it works in Ableton Live as expected (it starts playing/recording the selected clip when pressed).

Thanks for reporting, it is a bug. Will be fixed in the next update. While being at it I expanded the feature to have both footswitches configurable.

And another problem: every time I open Bitwig the APC starts in Play mode, not in Session mode! Why is that? Isn't the Session mode supposed to be the default mode? This is quite frustrating!

It is intentional but you are not the only one asking for it. It is already on my TODO list.

[moss]

When I installed DrivenByMoss and connected my Launchpad Pro Mk3, the Launchpad is not reset after quitting Bitwig.
What could cause this?

See the previous post.

Same problem here, but with DrivenByMoss 18.1.0 everything was fine before 4.4.2, so it’s not an issue with Moss extension, clearly Bitwig changed something after version 4.4.

btw temporary workaround for Launchpad Pro MK3 and maybe with other controllers - on macOS and if you're using Logic Pro, just start Logic Pro and exit it, it will reset the controller.

I did some tests now as well. The issue was introduced in 4.4.1.

[KTlin]

Hi. I have an issue using the Akai APC40 (mk 1) in Bitwig. The footswitch pedal I have connected to the APC doesn't do anything. It's supposed to "create a new clip on the selected track and slot, start play and enable overdub" but it doesn't do anything when pressed. I have it connected to the Footswitch 2 input, I'm using the latest DrivenByMoss extension and I'm on Bitwig 4.4. Also note that the pedal is working, there's nothing wrong with it. I can midi-map it to parameters in Bitwig and it works. Also it works in Ableton Live as expected (it starts playing/recording the selected clip when pressed).

Thanks for reporting, it is a bug. Will be fixed in the next update. While being at it I expanded the feature to have both footswitches configurable.

And another problem: every time I open Bitwig the APC starts in Play mode, not in Session mode! Why is that? Isn't the Session mode supposed to be the default mode? This is quite frustrating!

It is intentional but you are not the only one asking for it. It is already on my TODO list.

Great! Thank you!

[moss]

DrivenByMoss 18.2.0 is out!

Get it from https://mossgrabers.de

• Requires Bitwig 4.3+
• Added header to manual.
• Play position can now be changed during playback and is adjusted to the grid.
• APC40
  • New: Footswitches are now configurable in the settings.
  • Fixed: Cursor left/right to select the previous/next browser tab did not work.
  • Fixed: 12th page pad was off in drum mode.
  • Fixed: MkI: Drum pads in Drum Mode did not send notes.
• Generic Flexi
  • Added new functions: 'Device: Reset Parameter 1-8'
  • Added new functions: 'User: Reset Parameter 1-8'
• Komplete Kontrol MkII
  • New: Added detection for VST3 version of Komplete Kontrol plugin.
• Maschine / Jam
  • New: Footswitch options contains now the option to send sustain (CC 64).
• OSC
  • New: Added message: /device/param/{1-8}/exists
  • New: Added message: /device/page/{1-8}/exists
  • Fixed: Fixed velocity should not be applied to aftertouch.
• Push
  • New: Changing play position now show also measures in the display.
  • New: Select + Master knob: Zoom in/out of arranger.
  • New: Clip view is now the default for audio tracks.
  • New: Note edit mode has now presets for recurrence patterns. Press Shift and use the 1st row buttons.
  • New: Footswitch options contains now the option to send sustain (CC 64).

Enjoy!

[catzilla]

I found a little issue. When either the drum 4 or drum 8 sequencers are active and I move sequncer page up/down with the octave up/down buttons, on the display it says I move by 16 notes, which is wrong and little confusing.

Can't see anything wrong. When I press Octave up it say "E1.." and if I down again "C1".

The issue is not with the lower note of the range, but rather with the higher note.
For example, for the drum 4 it says 'C1 to Eb2', 'E1 to G2', et cetera. How it can be more than an octave if it only can sequence 4 pads at once? Same with drum 8.
It's really a minor issue though. I already got used to it, but the first time I tried using drum 4 it was disorienting a bit.

[sonderBUILDS]

You are awesome! Thank you so much!

[sonderBUILDS]

Regarding the APC40 problem: There is still something wrong with the drum pads. Counting from the bottom up:

-The first row works fine, now. The drumpads play and select the according pads on the drum machine. (Row content: Kick1, Snare, Hi-Hat, Hi-Hat)
-The second row to the bottom only selects the drumpads from the second row of the drummachine, but no sound is triggered. Just like before the update. (Row content: Kick2, Clap, Rim, Snare)
-The third row from the bottom selects the drumpad from the third row, but plays the drumpad from the second row.
Shaker selected, Clap played (Row content: Kick3, Shaker, Clave, Cowbell)

You are still awesome!

[catzilla]

It's such a bummer we can't change gain/pan/pitch/timbre/pressure spread value via the Bitwig API. Since you can assign those expressions to any parameter in Bitwig, that would turn Push into a very powerful step sequencer where you would be able to add desired amount of randomness to any step to up to five different parameters.
Where to submit a feature request? https://github.com/teotigraphix/Framework4Bitwig ?

[rxyml]

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,

I released another version, which fixes some errors/cosmetic, enables animations, and adds the layer mixer

https://github.com/ylmrx/ludwig (https://github.com/ylmrx/ludwig)

see a demo here : https://www.instagram.com/p/Cklo6M4PrTR/ (https://www.instagram.com/p/Cklo6M4PrTR/)

Do not hesitate to report on any issue

[kmonkey]

Hello mister moss. AKAI Fire and Bitwig 4.4.2 seems to have issue with your script.

Since the latest Bitwig update (4.4.2) Your script and AKAI Fire does not work properly and entirely anymore.

In a way that prior to this 4.4.2 update when I was shutting Bitwig projects then the FIRE controller said goodbye, and it shut down itself (turned lights off). After update 4.4.2 it does not work like that any more it stays open all the time, no matter which Bitwig project is closed or opened, and I need to unplug USB. Everything else seems to be working it just does not turn off controller anymore.

Now I am unsure is this Bitwig issue or your script issue, perhaps they changed something?

Can anyone confirm?