DrivenByMoss for Bitwig and Reaper


Can someone tell me if that REAPER script is able to recall all the mixer parameters (volume, pan, send, etc.) when opening a project? So that everything remains in sync all the time.

I know it’s plugin-dependant when working with parameter plugins (and this is a pity), but I am wondering if this is also the case with the mixer (controlled by the script) or if it’s automatic (no jump values).

If you open a different project, all values are updated on the controller.

Fantastic! Thanks Moss.

… I am still jumping to other pages accidentally. Especially from the Devices page, where it is more usual to be tweaking two knobs at once, one with each hand. Are other people finding themselves hitting three knobs in a row accidentally and frequently? If there is no way to differentiate top of the knob from body, another idea would be to require a longer simultaneous touch of the three knobs before jumping page.

Then, about the E1 in combination with the Launchpad Pro (I’m using Bitwig’s integration and I haven’t tested Moss’ one)…

The Launchpad Pro side works as expected. If you are in i.e. Notes and i.e. Polymer in Track1 is selected, that’s what you hear when you press the pads. If you select a different track with the E1 and you land in a different device (i.e. FM-4 in Track 3), the Launchpad Pro just follows and the pads now play FM-4. Very well, two controllers complementing each other.

The other way around isn’t as smooth, though. If you are in the E1’s Device page, tweaking knobs for Polymer Track 1, and then you change to Track 3 with the Launchpad Pro, the E1 will be still stuck in Track 1 Polymer, instead of moving automatically to Track 3 FM-4. Ideally the E1 would follow the Launchpad pro just like Launchpad Pro follows the E1, being both always in sync.

Regarding knob touch, it is already on my todo list to make this configurable.

I tested the track/device selection in both direction with the Bitwig an my implementation and it works fine.
Check if you enabled “PIN” on the Electra device page, then it will not change.


Ah ok, I haven’t tried the “PIN”. Will do.

And well, this is just a related rambling… things one think past midnight. :slight_smile:


I have a few questions regarding E1 used in REAPER mixer (please note that I don’t have an E1 yet) :

  1. Is it possible to create a remote control page only for specific named tracks?
    Example 1 : whatever their order, I want those tracks to be control on the same page (DRUMS, GTR, PNO, VOX).
    Example 2 : I want all the tracks containing the term “BUS” on the same E1 page

  2. If I hide a track from the MCP, is it also hidden from the E1 mixer?



  1. No.
  2. Yes.
1 Like

Thanks for your reply.

  1. is good news because we can use snapshots to do whatever we want to approach 1.

Another question, please: can we have 3 rows of 6 tracks to control volume/pan on the same page, instead of only 6, which is not enough in mixing sessions?

I have another question: is it possible to control REAPER track controls (the plugin parameters that we manually put in the TCP, one by one) in the same way we control Bitwig device/track/project remote controls?



I have currently no plans for that.

Bitwig track/project remote controls will be supported in the next release. Since these map to track controls in the Reaper version, yes, this will be work soon.

1 Like

This is very good news. Thanks Moss!

Okay. Do you think is it something we can program on our own? It’s important for me, and also probably for people who want to use E1 for mixing.

DrivenByMoss 21.5.0 is online!

Get it from

  • Requires Bitwig 5.0+ / Reaper 6.71+
  • Electra One MkI + MkII
    • Requires Firmware 3.5
    • New: All knobs are now relative.
    • New: New page for controlling project and track parameters. Touch knobs 9, 10 and 11 to activate.
  • Generic Flexi
    • Fixed: Set number of monitored browser results and filter column entries to 1 which speeds up the opening of the browser.



Thank you Jürgen, great work! Installed and all working well. Really appreciate your work on this and looking forward to seing what else we can achieve with E1 + Bitwig.

I have an interest in live performance with Bitwig, Oxi One and E1 (seeing if I can get a fun playable setup without too many boxes), so this update with the project and track parameter control makes me happy. I’ll let you know if I come up with any feature requests :smile:

Hi Jürgen, is there any particular advantage in using relative controls instead of absolute controls, given that the pots are endless anyway? (Asking to learn whether I should use them in my Ableton remote script too).

P.S.: Really like your design; inspires me to make some design adjustments to the presets I have been using.

Thanks Moss! Looking forward to use it with my MKI when out of Beta :slight_smile:

@jhh I think relative controls are great for relative movement in the timeline with the play cursor…


Yes, they are endless but behaved like absolute knobs. Therefore, I had always to reset their values which was quite performance intensive.

1 Like

Yes, and that’s definitely one that I will integrate in the Ableton remote script as well