I had to jiggle some setting in the app to get an old template to send button presses, but after that it worked.
The update also turned on the internal clock setting which confused me at first.
All good after that.
1 Like
another confirmation that this works / thanks for the recommendation!
1 Like
Still haven’t manage to fix my issue, no time to deal with it at the moment
1 Like
I got a Roto Control and am using it with Ableton, and must say I love it!
After years of using devices with endless encoders, I must say knobs are so much better and precise to either move fast, or dial in a parameter!
The Roto has all the advantages of endless encoders with none of the negatives(like trying to get the velocity feel just right).
I used Codex and modified the remote control script to make knob 8 in the Selected Mix mode always control the currently selected parameter. This is very nice if you’re working with you mouse, as you can quickly edit any param instantly when you select it without needing a macro-rack or a device preset!
I may also try and hack it to auto-map a device if no map exists.
I mapped a couple effects and some synths from Fors and have had more fun using them than I have had with hardware synths. This thing is just great. I love switching devices using the mechanical keys, and I really love the haptics in the knobs. Using endless encoders to change mode parameters with multiple options either on Push 3 or with a Fighter Twister was always painful but with the Roto in stepped mode, it feels so nice and I’m excited to use the knobs to change modes!
While it may be a negative, not auto-mapping devices is a nice feature in my opinion. AutoMapped banks are always not in the order I expect parameters to be. It would be cool though if plugins worked like Instrument Racks in that they automap if there is no map, but you can start learning if you want a custom device map.
Issues/Ideas for Improvements:
- If I use a mouse to change a parameter that is not mapped on the Roto, the Roto jumps to bank 1 of the device. This is very annoying.
- Some devices like delay have different rate parameters for synced/time/frequency which all need to be mapped separately. It would be awesome if we could setup a knob to change multiple parameters to address this.
- Using the arrows to change device banks takes a while, it would be nice if there was a shortcut to jump to a bank, and also nice if you could name each bank. Perhaps you could press both left and right to bring up UI to jump to a bank.
- The Editor should provide a way to reorder banks. Maybe I mapped: Oscillators, Filters, Enevelopes each on separate banks but then want the first bank to just be mapped to my favorite parameters. I would have to redo all the mappings or edit the JSON and reimport.
- The Editor should provide a way to manage the built in device JSONs so we can manage them if we hit the limit of 64 devices and need to remove some.
- It would be cool to have more than 2 indents available, for example, for Semi-tones I might want an indent at 0, +12 and -12 semitones.
- Would be awesome to have up to 127 steps in step mode.
6 Likes
featurerequests@melbourneinstruments.com - might not get anywhere but you never know
2 Likes
These are all solid ideas. For those who have hit the 64 device limit, what happens then? Does a ‘new’ device displace an old one?
You could add macro maps to your plugins, save those, and use them instead of just loading the plain plugin in future. Then the roto will auto map to those.
1 Like
That is (80%) the bug in the Remote Script i was talking about in a recent post. It has a global device changed listener and triggering that causes a redraw. “My” solution was a device to listener map that basically first checks if the triggering device is the currently controlled one. You might be able to extend that with codex to fix this. RotoControlMappings/ROTO_CONTROL_TGE.py at main · MrMatch246/RotoControlMappings · GitHub
@Mistercharlie
Not sure what you’re suggesting? Is this not the default behaviour of the Roto Control? I setup a device or plugin mapping and it’s saved to the device and used next time I used that device or plugin, which is very nice. Though for some effects or plugins, especially those with just a few params, I might not want to waste a plugin slot for those, so it would be nice if it could automap them if there’s not a custom mapping setup.
Though having to manually map plugins and devices for me has been an amazing feature for me. I’ve very much enjoying digging through the devices I’ve mapped so far and exploring every parameter to come up with a mapping I find works well. I just mapped Collision and Echo, of which I hadn’t explored all the parameters before and ended up creating a really cool arped instrument rack that’s fun to play with. Since it doesn’t just work, it’s forcing me to sit down and explore these devices in depth.
@TheGreatElemonade
Would be nice to know what you’ve fixed in your control script mod? Looking at your commits it looks like the problem is from VSTs. Today I was only using built in devices and did not have the issue, but thinking about it, the issue was happening when I was mapping Fors Pivot and then used the mod matrix which I had not mapped.
I have put up my remote script and some mappings here: GitHub - Quixotic7/Q7RotoControlMappings: Mappings I have made for the Roto Control · GitHub
1 Like
I meant that you save mapped racks like this for your plugins, with the most-used parameters mapped to the rack’s macro knobs.
Then the Roto will pick up on the macros automatically. It’s a bit quicker than mapping on the Roto app, although obviously it has less options. Another advantage is that you can map two parameters to one macro knob, which solves another one of your problems. You can use the same knob for a synced and non-synced delay times, for example.
2 Likes
@Mistercharlie
Macro Mapping plugins like that is a good idea, especially for plugins with less parameters. Mapping the multiple params like Delays to a single macro is also a good idea. Only issue is you need to save these as racks and then use them instead of the raw plugin.
1 Like
I do this anyway, and it’s just a matter of getting used to loading your own racks instead.
1 Like
This is exactly how I’m using it, removes a ton of the BS
1 Like
I came up with a cool idea. By using a bunch of Map8 devices I can map multiple sections for things like Oscillators, Filters, Etc. The problem is renaming these will make the Roto see each as a new device. So I hacked the remote script to detect if the device is Map8 and always use the same hardware mapping.
Now I can hold SEL and select which settings I want which are all named.
The Params unfortunately will all be named Macro1, Macro2, Or anything you have in hardware mapping. I’ll see if I can get this to work similar to the Rack Macros so the names come through.
Here is the remote script.
3 Likes
yeah, this / i’m doing the same in bitwig (eg the midi cc device, tho in my case in tandem w/ the hw instrument device) and the roto just picks them up.
tho, as i mentioned above, i have them nested which requires clicking, a bit frustrating; hopefully similar functionality to the group feat that allows one to dig into nested devices. 
I’ve done some more Remote Script hacking with Codex, check it out!
Adding “_Step2-24” or “_Center” to the suffix of a parameter name in an instrument rack will make that knob have step or centered haptics.
I made my own version of Map8 called RotoMap16
This is setup so you can rename the device to whatever and it will still use the hardware mapping for RotoMap16.
I also added a feature so if a M4L device has a parameter that starts with “RotoMap_” than it will map to the device mapping for the suffix. Thus I could make a variation of RotoMap16 or any device and have it use the same hardware mapping, ex, “RotoMap_RotoMap16” would use my hardware RotoMap16.json layout.
I tried to add parameter support to RotoMap16 so it would render the parameters which get auto-detected when mapped, but could not figure out how to get these out of M4L.
Lastly, I made it so if you collapse devices they are not visible when holding the SEL button to navigate the chain.
With this in place you can map several RotoMap16’s or default Map8 which is also supported, then group these to a Rack to add parameter names and haptic settings. Now collapse the racks and you will just see the Audio Effect Racks when holding SEL on the Roto. Thus you could set up a mapping in which you have racks for things like “Oscillators”, “Filter”, “Envelopes”, “LFO’s”, etc.
The only lame thing with this is you don’t have button support on racks. I might see if I can come up with a way to map racks to buttons using “_But2” - “_But24” suffixes.
4 Likes
Here is a quick video of my modified remote script in action
7 Likes
I think this is an Ableton question but it concerns my Roto control, so I’ll post it here. I have a VST that has some parameters that can not be revealed in the plugin configure section. Interestingly this parameter does have a midi cc associated with it in the VST itself. How do I map this parameter to the roto control? Hopefully what I write makes sense…
Maybe map that cc first in ableton rack, then you can easily map rack to roto
Thanks. Unfortunately can’t do that either.
1 Like