Roto-Control for Bitwig Discussion

[gurulogic]

I could not find a dedicated thread here for discussing Melbourne Instruments Roto-Control, Bitwig Implementation, features and general usage.

Within reason, I will try to keep this post updated by consolidating feature suggestions that have been posted, bugs or any other relevant info.

On that note, there is a new Roto-Control/Bitwig beta (0.1.1) out today.
https://www.melbourneinstruments.com/support

"Firmware Release Notes
ROTO-CONTROL v0.1.1 Beta

New features:
2 June, 2025
•Haptic control added to plugins with positive/negative control, Roto-Control knobs will automatically have a centre detent.
•Touch automation now works when overdubbing in the arranger.
•MIX Mode: Roto-Control will automatically jump to the matching page when a track is selected in Bitwig Studio.
• Arrow keys will move the play head (scrub) when transport button engaged in PLUGIN and MIX Modes on the Roto-Control

Bug fixes:
•Learn function is now working for VST plugins.
•Changing between remote pages using Roto-Control now works.
.Remote pages and Learn function now work correctly on tracks with more than 8 plugins."
• Fixed reliability issue in PLUGIN Mode when using lock function with Remote pages.
.Group tracks now display correctly on Roto-Control when folded in Bitwig Studio.
• Fixed issue where Pan control was not correctly aligned to zero position when operating MIX mode.
•Fixed reliability with Bitwig Studio startup in some cases.
• Deleting controls from a Remote page now update effectively on Roto-Control.

[pdxindy]

Do you have one?

I'm interested to buy one, but will wait for a V1 firmware.

[teknoman]

Thanks for the update. Updated mine. This controller has so much potential and I can't wait to see what they add to it.

[gurulogic]

Do you have one?

I'm interested to buy one, but will wait for a V1 firmware.

I have had mine for a couple weeks now. Unfortunately with being swamped with other stuff I haven't had much time to dig in deep, but initial impressions are good so far.
"touch" is a little touchy, hopefully that is able to to be better optimized. Definitely feels a bit barebones in function, lots of room to grow, especially in terms of more customizable options for use specific cases. However, what it does it seems to do well.
The haptic response of the pots is realllly slick for sure. I look forward to seeing this controller mature. But even if it were left as is, I am perfectly happy with my decision to purchase.

[pdxindy]

Do you have one?

I'm interested to buy one, but will wait for a V1 firmware.

I have had mine for a couple weeks now. Unfortunately with being swamped with other stuff I haven't had much time to dig in deep, but initial impressions are good so far.
"touch" is a little touchy, hopefully that is able to to be better optimized. Definitely feels a bit barebones in function, lots of room to grow, especially in terms of more customizable options for use specific cases. However, what it does it seems to do well.
The haptic response of the pots is realllly slick for sure. I look forward to seeing this controller mature. But even if it were left as is, I am perfectly happy with my decision to purchase.

Thanks for the feedback!

[n9research]

Got mine this morning

Impressions:

• Weighty, solid feeling

• Buttons have the feel of Cherry MX Red (linear) keyswitches

• Encoder feel is excellent. Resistant endstops for potentiometer mode and multiway switch segmentation feel excellent

• Encoders appear to be high resolution - I don't have a way of measuring exactly, but when operating as a potentiometer with endstops, seems to be 10, 11, possibly 12-bit

• It doesn't seem to have a way of addressing Project or Group-level remotes (outside of unidirectional, low-res MIDI CC). This is a bit disappointing for me, as I bought this device specifically to use as a dedicated Project remote. Of course, the Bitwig script is only beta right now, so I fully expect this to be implemented soon. I've contacted Melbourne regarding this, will update when a response is received.

[pdxindy]

Thx for the feedback. Addressing project/group remotes would be a big plus for me too.

[n9research]

Thx for the feedback. Addressing project/group remotes would be a big plus for me too.

I had a reply to my ticket, confirming that Project/Group remotes are not accessible - but, crucially, "at the moment" - which I'll take as an indicator that it's being worked on.

In fact, after some more back-and-forth, it is possible to access the group/project remotes from the controller in plugin mode - but getting them to show up involves trial and error. If, in Bitwig, you switch the selection from a plugin to one of the remotes, it sometimes works, and sometimes doesn't. It seems to depend on whether the plugin you switch from has a control that's represented in the remote - but not always. And the lock function doesn't work when you get there.

So it seems like I'm exploiting something a bit buggy in the script. But I can work with this until it gets properly implemented. My highest recommendation stands.

[pdxindy]

So it seems like I'm exploiting something a bit buggy in the script. But I can work with this until it gets properly implemented. My highest recommendation stands.

[SLiC]

Do you have one?

I'm interested to buy one, but will wait for a V1 firmware.

I’m waiting until you an switch between Live Stream and Bitwig (not load either or)

[n9research]

Thx for the feedback. Addressing project/group remotes would be a big plus for me too.

I had a reply to my ticket, confirming that Project/Group remotes are not accessible - but, crucially, "at the moment" - which I'll take as an indicator that it's being worked on.

In fact, after some more back-and-forth, it is possible to access the group/project remotes from the controller in plugin mode - but getting them to show up involves trial and error. If, in Bitwig, you switch the selection from a plugin to one of the remotes, it sometimes works, and sometimes doesn't. It seems to depend on whether the plugin you switch from has a control that's represented in the remote - but not always. And the lock function doesn't work when you get there.

So it seems like I'm exploiting something a bit buggy in the script. But I can work with this until it gets properly implemented. My highest recommendation stands.

2.0.0 is here, and no project / group-level remote

the glitchy workaround I described above is now also locked out.

kinda inexplicable that this wasn't a core feature, roto is so obviously the perfect solution for a macro controller for BW live recording/performance.

[teknoman]

I think they made it worse somehow, not sure. I don't feel like using it as much as before. Takes too long to switch parameter pages and you have to do it a lot if you want to get in depth and actually tweak anything. Idk, I really wanted to like this controller, but it is collecting a little dust already.

[icaria36]

I have a question. When mixing a project, I have the Bitwig's mixer in the main screen area, and then the Master track underneath in the device panel, to check the Limiter etc as I tweak the volume of each track. Is there a way to fix the Master track in the device panel.

In the setup above, if I use the Roto in Mix mode, the device panel will change to the track whose volume I'm tweaking, which forces me to select the Master track manually to see again how is the Limiter etc doing after a tiny volume change.

I thought I could achieve this by pinning the Master track in the Roto controller dialog (the little keyboard icon in the top right), but it doesn't seem to do anything. All this in Bitwig 6 beta 3 (I know there is a beta 4 but I'm about to finish this project and I'd rather not update yet).

[Frank_GianaBrotherz]

i tested it at superbooth and the feeling of the knibs is awesome

[zipidowski]

I just got roto-control. I'm using bitwig 6 beta 4. Replika xt doesn't seem to work right. For example bottom left corner "single/dual" setting goes infinite loop of changing back and forth after changing that setting in roto-control. All other stepped knobs have same issue in replika xt. I mapped couple Valhalla supermassive knobs to stepped value and they seem to work just fine.