If you use a Ableton CC Control Device you can assign knobs to send custom specific CC’s to the VST. See if the VST responds to that, if it does, rack CC Control Device and then macro the CC knob to the rack macro knobs and Roto Control will work.
Right, I have a small problem. In my vst I have 2 virtual faders that change function depending on what waveform is selected in the vst. Unfortunately the roto control isn’t smart enough to know this and so I’d have to map all the different fader functions separately to have them available. Does anyone know a way around this?
Maybe control the VST parameters with a rack macro, and map the macro to the Roto?
is it still possible to buy dif color key caps for this thing? I don’t have one but have been circling for a while and will eventually pick one up to try it out. I want those green or grey keys though !
Has anyone found a way to trigger Roto-Control functions remotely without needing to press physical buttons. My first use case is with the device lock button (plus sign inside round brackets - middle right button). I will be configuring the 1st 3 buttons to allow me to switch between 3 midi tracks, and the automapped VSTs on those tracks. The button commands will also need to deactivate the lock, then switch miditracks, then reactivate the lock (all to be done using ClyphxPro)…but I need access to the lock button remotely
Very cool. Plenty in here that looks like it could be really useful in setting up the RC for my live sets. I think you mentioned using Codex to hack the script. What is your level of coding like…interested whether it would be worth my while to dabble under the hood there. I’m technically savvy but def not a programmer…outside of VisualBasic.
I’m actually a senior software developed with 15 years professional experience. My main languages are C# and C++. However, I’ll be honest, I completely Vibe-Coded this Ableton control script using Codex and barely looked at the code. This was with the $20 a month subscription. If you’re technically savvy and can explain to the LLM how you want things to work, what isn’t working, and know how to install and use Ableton Control scripts, you should be able to rework this and make it work for your needs.
You can also just explain what you want and ask the LLM if this script can work as is for what you are trying to do. My modifications make it quite nice and easy to just use a bunch of parameter banks in Ableton and have things all working nicely with haptics.
Codex or Claude Code would work great for this. If you’re on the $20 Claude Code subscription, stick with the older Opus 4.6 or Sonnet models which will burn through usage slower. I’m sure you’ll have success in dabbling under the hood!
So I turned on my Roto with Ableton the first time after a while… Plugin mode does not work anymore. Even with a simple device as Utility, the knobs don’t snap to the parameter values. Has someone else the same issue? I used the newest firmware.
Mine has acted strangely if it is not getting enough power over USB. I just always use a separate power cord now. Maybe check your connections.
This actually hasn’t changed. I always use two usb cables. But I will double check. Thanks!
Also try reinstalling the roto-control Ableton script, especially if you’ve done a firmware update using new version of the app. I forget the exact process but there is a menu item in that app which involves the ableton user library and this is how the script can be reinstalled. And of course make sure that control script is setup properly in Abletons settings, ie pointing at the right MIDI device.
I’m genuinely interested in the specs of the Roto’s USB port, not the one for power, but the main USB port. I use the original USB-C to USB-C cable and have it connected to a powered USB 3.0 hub with USB-A ports. I tried a gazillion different USB-C to USB-A adapters but only those made by Basesailor deliver enough power to the Roto. Using any other adapter results in the Roto to display “Connect Power”. This is so strange and I’m not even sure if either the USB-C adapter from that brand is wired up out of spec or if the Roto is at fault.
I find it sensitive to power reqs, especially if there are others relatively greedy things on the same hub. I now feed the power USB from a repurposed iPad charger. No issue since the switch.
I do think they should have just specced it with a dedicated PSU (and switch!)
Just got an email from the retailer where I bought it - apparently Melbourne Instruments are offering a 10 year warranty on the motorised knobs, as long as you register: 10-YEAR WARRANTY — Melbourne Instruments
Wow !! That’s confident
has anyone of you registered and received a confirmation email from them? I have not heard back from them at all and I accidentally registered twice …
I’m having a strange thing with roto and bitwig.
Im using bitwig to route midi between roto and rytm… works perfectly except on channel 3, no CC’s are getting through on ch3.
I substituted OT’s midi tracks for Roto and that works perfectly so I think theres something fishy between roto and bitwig. I also tried the same thing with ableton and that works perfectly.
When I googled there was mention of driven by moss scripts potentially blocking channel 3, but deleting the driven by moss scripts hasnt solved it. the only other controller script in my bitwig extensions folder is the Roto Control script.
I’ve contacted melb instruments support, so hopefully they’ll have a solution soon. but I’d be interested to know if anyone else is having the same experience.
hey - I have now the same Problem with my rotocontrol… in the beginning some little bugs… can’t mute two tracks at the same time… or lightning led on the buttons for page 1 and when move to page 2 the buttons still shining . all fixed by firmware updates. but now , my rotocontrol in Ableton jumps very often to track 4 … so its extremely sensitive … it happens when I touch the whole unit a little bit. or mute track 1 and 2 or touch knob 3 … unusable ![]()
Support of Melbourne told me knob 4 on the roto has a fault. and I can use warranty … but I think its not only the unit. sometimes it works. its absolute frustrating. its would be great when it works , but for now its overpriced for what it is .
I mean not to state the bleeding obvious but I’d just follow whatever instructions support @ Melbourne provide that should help you get it back to working again surely ?
That’s unfortunate man. Welcome to the club. The CEO jumped into this exact thread under a burner account to claim my unit was a freak, 1-in-10,000 anomaly and made it sound like I had a home studio in CERN generating radioactive interference. Turns out the hardware just has massive QC issues. From what I remember he replied to me both here and in the NINA thread. Save yourself the headache and just use it in Plugin mode. I sold it to my nephew at a loss and that’s what he does.