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

[krazzmann]

I thought the Akai fire script was developed by Richie hawtin and Bitwig. Is there a Moss script too? I couldn’t check because the website is down. In the Hawting script I don’t think there is a nudge and I was under the impression that nudge is not available through the API.

The Akai Fire is supported for quite some time with DrivenByMoss. The script from Richie is a very specific sequencer tuned to his needs. The latest DrivenByMoss version contains now a similar sequencer but adapted to fit into the rest of the existing Fire workflow.

When will the update of the Akai Fire script be released? AFAIK it is not included in 17.5, right?

[moss]

I thought the Akai fire script was developed by Richie hawtin and Bitwig. Is there a Moss script too? I couldn’t check because the website is down. In the Hawting script I don’t think there is a nudge and I was under the impression that nudge is not available through the API.

The Akai Fire is supported for quite some time with DrivenByMoss. The script from Richie is a very specific sequencer tuned to his needs. The latest DrivenByMoss version contains now a similar sequencer but adapted to fit into the rest of the existing Fire workflow.

When will the update of the Akai Fire script be released? AFAIK it is not included in 17.5, right?

As I wrote it is supported for quite some time and yes it is part of DrivenByMoss.

[n0j0e]

Hi i need a little help here with my AKAI MPK mini mk3 (latest firmware) and Generic Flexi 17.5.0. The finger drum pads on channel 10 didn't work anymore if i playing notes with it.
If i set the controller to the default Akai script for this device it works.
I can play then Bitwig's Drum Machine (Source: All) with keyboard (MC1) and the pads (MC10).

The strange thing is that Flexi detects the correct Midi Channel with note.

Windows 11, Bitwig 4.3.4

[moss]

Hi i need a little help here with my AKAI MPK mini mk3 (latest firmware) and Generic Flexi 17.5.0. The finger drum pads on channel 10 didn't work anymore if i playing notes with it.
If i set the controller to the default Akai script for this device it works.
I can play then Bitwig's Drum Machine (Source: All) with keyboard (MC1) and the pads (MC10).

The strange thing is that Flexi detects the correct Midi Channel with note.

Windows 11, Bitwig 4.3.4

Not sure if I understand your issue but the Generic Flexi does not split MIDI channels into separate inputs. As a workaround you can set it to All and then filter for the MIDI channel on the Bitwig track.

[n0j0e]

Flexi sends notes to tracks only on Midi channel 1?

How can i filter the Midi channel 10 if Flexi didn't forward the incoming notes on channel 10 to the armed track?

[moss]

Flexi sends notes to tracks only on Midi channel 1?

How can i filter the Midi channel 10 if Flexi didn't forward the incoming notes on channel 10 to the armed track?

In the keyboard configuration area at the bottom of the Flexi settings, there is an option to filter the MIDI channel. You can either set it to All then everything is simply routed to Bitwig or you can select a specific MIDI channel all others will then not routed to Bitwig.

[Ezzzer]

I have two launch pads and I want each on a different channel.
how can i change the launchpad channel to work on some other channel ?
this is very important for performing live.
maybe add an option in the setting for choosing the launchpad channel ?

[moss]

I have two launch pads and I want each on a different channel.
how can i change the launchpad channel to work on some other channel ?
this is very important for performing live.
maybe add an option in the setting for choosing the launchpad channel ?

There are 2 a bit older but still valid videos were I talk about this:

[n0j0e]

Flexi sends notes to tracks only on Midi channel 1?

How can i filter the Midi channel 10 if Flexi didn't forward the incoming notes on channel 10 to the armed track?

In the keyboard configuration area at the bottom of the Flexi settings, there is an option to filter the MIDI channel. You can either set it to All then everything is simply routed to Bitwig or you can select a specific MIDI channel all others will then not routed to Bitwig.

Great Moss. It works now. I can play a device with the pads (MC10) and a device with the keyboard (MC1).

Now my next question. Didn't find a program/bank change function (prev, next) for CC. I using often the u-he program/bank change option (needs to copy presets/folders to MIDI Programs in the u-he preset folder). Tried to find my answer in the DriveByMoss.pdf and here but find only on one thing about synthesizer as controller device.

I know i can use the Bitwig MIDI Program Change Module and the Knobs for Paramters but it is not very comfortable. Auto Send didnt work for banks!

[catzilla]

Bitwig supports u-he presets natively as if they were Bitwig stock devices' presets. You can even filter prestes by tags. Just have to add sound location where u-he presets are located in your system. i think it's more convinient way to change u-he presets than thru MIDI program change.

[moss]

Now my next question. Didn't find a program/bank change function (prev, next) for CC. I using often the u-he program/bank change option (needs to copy presets/folders to MIDI Programs in the u-he preset folder). Tried to find my answer in the DriveByMoss.pdf and here but find only on one thing about synthesizer as controller device.

I know i can use the Bitwig MIDI Program Change Module and the Knobs for Paramters but it is not very comfortable. Auto Send didnt work for banks!

Using the Bitwig Program Device is also the only thing I can suggest. Depending on the capabilities of your MIDI controller you could try to simulate a relative knob with 2 buttons.

[n0j0e]

Bitwig supports u-he presets natively as if they were Bitwig stock devices' presets. You can even filter prestes by tags. Just have to add sound location where u-he presets are located in your system. i think it's more convinient way to change u-he presets than thru MIDI program change.

Nope, i think it work's only if Bitwigs browser is open. That is no problem with Flexi. With normal MIDI Progam/Bank change it works immediately.

[TommyC81]

Some bug reports (I think):

When scrolling using OSC '/track/bank/+' and '/track/bank/-' and the selected track goes out of range (i.e. outside of the normally 8 tracks), there is no OSC message being sent indicating that a previously indicated "selected" track is no longer selected. In practice, this normally means that Track 1 or Track 8 remains indicated as Selected.

When pressing the "OSC" text in under Settings -> Controllers -> Any 'Open Sound Control' item, a web page is generated that doesn't contain any information, only headers:

Code: Select all

OSC address space
Methods

OSC address space
Methods

'Open Sound Control' devices don't seem to work unless an MIDI input device has been selected (Normally 'TouchOSC Bridge' in my case).

Maybe I'm missing something, happy to accept guidance and corrections

Using:
Bitwig 4.3.4 (on Windows 10)
DrivenByMoss 17.5.0 for Bitwig (Aug 29, 2022 release)
TouchOSC 1.1.5.145 (Aug 18, 2022 release)

Another oddity:

When using a RADIAL for setting panning; if the panning is reset to default, and you then click to send a new value, it randomly goes to -100% for no obvious reason. This does not seem to occur if previous message was not a '/pan/reset', and it also doesn't make a difference if sending INT32 rather than FLOAT.

Edit: This is not only for -100%, it's all kinds of random values being returned on the first change following a '/pan/reset', the temporary locking to '100%' and '-100%' does however stand out.

Message log from TouchOSC below:

Code: Select all

23:58:59.156 | SEND       | ENDPOINT(192.168.0.101:8000) ADDRESS(/track/4/pan/reset)
23:58:59.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/update) INT32(1)
23:58:59.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/track/4/panStr) STRING(0.00 %)
23:58:59.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/track/4/pan) INT32(64)
23:58:59.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/update) INT32(0)
23:59:07.157 | SEND       | ENDPOINT(192.168.0.101:8000) ADDRESS(/track/4/pan) FLOAT(19.984459)
23:59:07.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/update) INT32(1)
23:59:07.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/track/4/panStr) STRING(-100 %)
23:59:07.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/track/4/pan) INT32(0)
23:59:07.177 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:59620) ADDRESS(/update) INT32(0)

[BoogerSnot]

For the Launchpad Mini MK3, is there a way to turn off the LEDs when not in use?

Default way to do it is hold down Session and then press the pad in the lower right, then to turn it back on again just press any button.

If it’s not in the DrivenByMoss extension, maybe it could be added? It’s a small but useful feature.

[BoogerSnot]

For the Launchpad Mini MK3, is there a way to turn off the LEDs when not in use?

Okay probably not needed, as you can just go to the settings in Bitwig and turn off the controller, which reverts Launchpad to the default state at which point you can turn of the LEDs.

There are some spare buttons in the User section used for settings though, in case you want to add it anyways.