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

[moss]

Hi there! I am not able to dock floating expanded device views into the main window using Generic Flexi (Rel. 29.01.2025).

I thought it was due to the setting: Device ‘Floating window follows current track|, but that doesn't seem to be the cause.

Have I overlooked something? Thanks and greetings in advance.

I do not fully understand. Is this an Action you are calling? Please describe in more detail.

[moss]

Hey
Is there any progress with Push 3 being able to slide in scale (like in Live) in Bitwig?

Sadly, not. If someone knows how it works I would be glad to integrate it.

[moss]

Any chance that you will take a round and modify the AKAI Fire with a few more options for Reaper ?
For instance - it would be great if we could use the USER 2 mode - at the moment it is bound to Project and Track parameter - but if I am not mistaken, Project and Track and Parameter are not supported in Reaper but Bitwig - so why not use it for sending Midi CC Values for instance.... this way the Fire could be used for some more stuff then now.. for instance controlling "last touched parameter". maybe you could make some configuration window like for USER 1 but more generic...

And another thing would be nice - can we get an option - maybe in the settings - to configure the pads on the "shift view" ?
this way we could add some functions to control reaper on our own for pads that are unused right now...

Cheerz the Heavy

They are supported and map to the Track Parameters in Reaper. See the "Known Issues" section in the DrivenByMoss manual.

[moss]

Hello.

I am curious, is it possible to set an endless encoder to select scenes and launch and stop them with push buttons with the most recent version of the flexi script?

Sorry, no.

[moss]

Hello Jürgen, for the Push, seeing the played chords on the screen is an excellent idea, but after the Gb4, the notes are no more recognized on my Push 2 and the other keyboards. Weird. Is it a bug ?

Not sure what you mean. In which mode does this happen? Tried with the normal play view and could not see an issue.

[Unconformed]

Hi

Ty for your work. I am on Windows, using ht e most recent version of Bitwig (5.3.2 as I write this).

I have the installed the extension for my push 1 and it all seems pretty good so far.

I am following your second tutorial, and I can't seem to get the sequencer to work.



I have a drum machine with samples loaded in, and I have selected various sequencers such as drum 64, drum, raindrops and no matter what I try, not sequencer comes up to program drums. I am unable to bar length to the right of the drum rack, and I unable to select more than a single light where the sequencer would normally go.

It is probably user error, hoping you can help?

I have placed focus on the clip. added a clip with push and via GUI.

I have used push 1 with Ableton no issues in the past.

Here is an example image.

https://imgur.com/a/mJoTy0g

[moss]

It is probably user error, hoping you can help?

I have placed focus on the clip. added a clip with push and via GUI.

I have used push 1 with Ableton no issues in the past.

Here is an example image.

https://imgur.com/a/mJoTy0g

Please show me a screenshot of Bitwig as well.
It is hard to tell from your picture but it might be that the 1st page of the sequence is not selected.
The 4x4 square right to the drum pads select the loop and edit page. Try to press left/upper pad.

[Attuned]

Hi Moss. I'm on Push 2. On a drum machine track, I am not able to tweak a parameter of a sub-instrument (a snare for example) of a drum machine and play the corresponding pad at the same time. When I press the pad, the parameters disappear from the Push screen and I have to enter into the sub-edit screen again. How can I 'lock' the parameters in place while I play the pad? I want to tweak the sound and preview it, but that seems impossible. Here's a video of the issue.

https://share.icloud.com/photos/046_li3 ... 1by0klLXxQ

EDIT: I realised that it's a setting in the controller - "auto select drum settings".

It still feels a bit strange to me though - I would expect that if I'm play the same pad for the channel that I'm currently editing, it would stay on the page I've selected. Is this possible?

[moss]

Hi Moss. I'm on Push 2. On a drum machine track, I am not able to tweak a parameter of a sub-instrument (a snare for example) of a drum machine and play the corresponding pad at the same time. When I press the pad, the parameters disappear from the Push screen and I have to enter into the sub-edit screen again. How can I 'lock' the parameters in place while I play the pad? I want to tweak the sound and preview it, but that seems impossible. Here's a video of the issue.

https://share.icloud.com/photos/046_li3 ... 1by0klLXxQ

EDIT: I realised that it's a setting in the controller - "auto select drum settings".

It still feels a bit strange to me though - I would expect that if I'm play the same pad for the channel that I'm currently editing, it would stay on the page I've selected. Is this possible?

Tricky, since it can be anywhere it the sub-tree.

[moss]

DrivenByMoss 25.0 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 5.2+
• New: Added support for Melbourne Instruments ROTO CONTROL.
• Akai Force
  • Fixed: Scrolling tracks by 8 did not work.
• Elektra One
  • Fixed: The Parameter Page Buttons 2 and 5 were flipped on the Devices page. Upload the updated template to fix this.
• Kontrol MkI
  • Fixed: Option to dis-/enable 'Notify play chords' was missing.

Enjoy!

[Sekops]

Amazing, thanks for all the hard work on Roto Control support. A few things I’m not clear on:

Are third party plugins supported via Bitwig remote controls?

Is it still possible to store plugin parameters in the Roto control device, or would it be necessary to map them per project, or even per track inside a single project?

Might it be possible to remap the pots to control the volume / gain on a tool device on each track, or to a different parameter such as the “In” value of Kclip to push the volume into a clipper? I prefer to automate these, rather than record automation on the track volume. After all, recording analog automation is the killer feature of Roto Control.

Will it differentiate between multiple instances of native and / or third party plugins on different tracks? e.g. multiple instances of Polymer or Serum 2? How about the same plugins on the same tracks, e.g. two instances of EQ-5?

How does it handle hidden tracks in Bitwig? Are these ‘counted’ within the 64 track limit? How does it handle projects with more than 64 tracks? Is it just the first 64 that are usable?

How would this interact with their “Roto-Setup App”, for example is import / export of the config supported? Is the Controller script dependent on a particular version of the Roto Control firmware?

[moss]

Amazing, thanks for all the hard work on Roto Control support. A few things I’m not clear on:

Are third party plugins supported via Bitwig remote controls?

Yes. But you have to first map them to pages in Bitwig and then you need to learn them to the Roto-Control.

Is it still possible to store plugin parameters in the Roto control device, or would it be necessary to map them per project, or even per track inside a single project?

They are stored for each Plugin on the device. Only the MIDI mapping is per project.

Might it be possible to remap the pots to control the volume / gain on a tool device on each track, or to a different parameter such as the “In” value of Kclip to push the volume into a clipper? I prefer to automate these, rather than record automation on the track volume. After all, recording analog automation is the killer feature of Roto Control.

All instances of a plugin will have the same configuration.

Will it differentiate between multiple instances of native and / or third party plugins on different tracks? e.g. multiple instances of Polymer or Serum 2? How about the same plugins on the same tracks, e.g. two instances of EQ-5?

See previous answer.

How does it handle hidden tracks in Bitwig? Are these ‘counted’ within the 64 track limit? How does it handle projects with more than 64 tracks? Is it just the first 64 that are usable?

Hidden tracks are not counted. So, if you hide the first 64, you will see 64 more
You can access only 8 pages (8x8 = 64)

How would this interact with their “Roto-Setup App”, for example is import / export of the config supported? Is the Controller script dependent on a particular version of the Roto Control firmware?

You can configure the MIDI mode with whatever you want until you stay away from MIDI channel 16.
I tested with latest firmware 1.1.2. No idea, what changes might be coming in future updates.

[masterheavy]

They are supported and map to the Track Parameters in Reaper. See the "Known Issues" section in the DrivenByMoss manual.

ok, I got it, adding paramter to the TCP make them available for USER Mode 2. This is quite nice but needs a bit of setup and mess up the TCP really quickly.

Nevertheless it would be a real improvement if we could utilize the "last Touched parameter" function which only seems to take real Midi CC Values as input. is it possible to implement some Midi CC output Mode?

And another thing would be nice - can we get an option - maybe in the settings - to configure the pads on the "shift view" ?
this way we could add some functions to control Reaper on our own for pads that are unused right now...

and what about the second request ?

Thx for your efforts

[moss]

They are supported and map to the Track Parameters in Reaper. See the "Known Issues" section in the DrivenByMoss manual.

ok, I got it, adding paramter to the TCP make them available for USER Mode 2. This is quite nice but needs a bit of setup and mess up the TCP really quickly.

Nevertheless it would be a real improvement if we could utilize the "last Touched parameter" function which only seems to take real Midi CC Values as input. is it possible to implement some Midi CC output Mode?

"last Touched parameter" is something I will look into in the future since this feature just got introduced in Bitwig as well.

And another thing would be nice - can we get an option - maybe in the settings - to configure the pads on the "shift view" ?
this way we could add some functions to control Reaper on our own for pads that are unused right now...

and what about the second request ?

I have currently no plans for that.

[Attuned]

I'm struggling to replace a device (not a preset) in a Drum Machine with another device, using the Push 2.

I've got a kick on C1 which has a sampler as the device. When I press the Drum Machine and go down the hierarchy into the pads and then press the Kick, I'm then shown the Sampler parameters. I then click Browse. From here I can only replace the preset with another Sampler preset. I can see in the browser that the sampler stays selected in the device filter. How do I clear that filter using the Push?