So I’ve encountered, in some Live instruments, that certain parameters can’t be mapped. For example, the Frequency Mod buttons on the Drift instrument. Is there a reason?
Thanks for this. Convinced me to try it even if I’m not sure eits exactly what I want 
excited to get it!
I poked around a bit and I think I might be able to modify the Ableton remote script to do what I want 
will see when it arrives!
Curios what were you planning to do by changing script?
I have some minor ideas for some changes like, volume level limitations to 0db, but never coded or used python.
1 Like
This would be great. For me, just a detent at 0dB would be best, so I could go over if required.
1 Like
At a high level, I wanted to make it so that if I’m using a certain device (some kind of Max “8 macros” device, to map 8 parameters from across my set, rather than one specifc device), then it should send updates when the device’s parameter names change, so I can control a whole song with the correct labels. Not 100% sure it’s doable but let’s see.
I think for the volume that would be a firmware level change, which isn’t possible to make (without lots and lots of work at least). I’d suggest reaching out to Melbourne with a feature request!
1 Like
I had some experiences, not sure what caused it, that volume would jump to max value when quickly switching modes or tracks. But it would happen randomly without possibility to repeat the issue.
So just for security reasons (and i never go above 0db on a track anyway) i would like to set this up
I did reach out via email, hopefully they can do something about it
Since the last update I have way more parameter jumps. It event happens that the Param changes, without that I touch something. Usually very litte, but still… Does someone experience this as well?
Is there anyone that has successfully tried to map any controls for 2020 semi modular beat machine by dub russell?
1 Like
Has anyone tried pairing the Roto Control with the Synthstrom Deluge? I’m trying to think through the best approach to pairing since Deluge does not have predetermined midi CC numbers.
I wrote a small program that generates a Roto-Control configuration file mapping all knobs and buttons to a range of CC numbers. Currently it sets different colors to each button and knob and starts mapping from CC number 64. I’m not sure if there is a common starting number, as the lower ones are used for things like pitch-bend by default.
3 Likes
It would be great if you could share that!
Right now the program is simply a command line tool without any parameters, that generates the configuration file. Here’s a link to the generated Roto-Control midi configuration file. As a new user I can’t attach the file.
3 Likes
Yes I’m seeing this too 
I emailed them about it
1 Like
Thanks!
1 Like
Here’s a set of generic MIDI templates for use with Roto-Setup, that I generated with my software tool. I’ve added a version with 14-bit values (16384 steps fine CC), NRPN (coarse) and NRPN (fine).
4 Likes
Is there anyway to define custom MSB/LSB value pairs for finer control? I’ve attempted to map values for my Pro-800 but the device uses a different LSB value than what the Roto-Control defaults to when adding the MSB. I’ve had a look at the JSON files as well, don’t see a value in there.
I noticed that as well, I have no idea why it is this way, but it does look like it cannot be changed right now.
Its probably that way because the official MIDI spec had those fixed pairs for 14 bit CC. But clearly there are some manufacturers who did 14 bit differently.