Having similar experiences too.
Works great with Analog, Glue Compressor etc.
Does seem to be issues with Overbridge plugins and other VSTs, and they sometimes overlap.
Is there a way to delete learnt controls yet?
Having similar experiences too.
Works great with Analog, Glue Compressor etc.
Does seem to be issues with Overbridge plugins and other VSTs, and they sometimes overlap.
Is there a way to delete learnt controls yet?
Yes you can delete learnt controls by holding down learn then touching the relevant knob twice.
I think I need one of these.
Yeah, I can do this. But only by clicking on the triangle icon on the plugin so it expands into its non GUI version. See the photo below for an example.
Damn and it remembers different mappings for different 3rd party plugins?
Maybe I have an issue with my unit. Have tried Rhodes Anthology, Roland Juno, GForce OBX, Cherry Audio P-10 - the roto thinks they’re all the same plugin (i.e. whatever I map for one, shows up on the other)
@Honeysmack any guidance you can provide would be much appreciated. Thanks!
Did a quick test and I think I might be having the same issue as you. I can map different plugins when they are on their own channel, but if I have two effects on the same channel, I can only map one of them. I have also tried allocating one effect to the next page. pretty sure I was able to do this with native plugins?!? I also find the mapping to be quite random, sometimes it works and other times seems to be misbehaving.
When using 3rd party plugins, you’ll need to “configure” the controls you want to assign to Roto-Control first: click the triangle, then ‘configure’ on the plugin (all goes green), next choose the parameter you want to use from the plugin. Confirm by clicking ‘configure’ again (all the green overlay goes away). Now you should be able to LEARN from Roto-Control.
If you’re still experiencing issues please contact support@melbourneinstruments.com Subject your message “Roto-Control” and provide full details of your issue. Attaching your set-up or a little video will also be helpful.
I wound up ordering one. I’ll see for myself if I misjudged. The device memory in Live could be the big draw but if that deep integration is only limited to Live and not developed for other DAWs it would be a disappointment.
I went through something similar when I mapped the Faderfox EC4 to Live devices. I used Remotify - https://remotify.io/ and put my instruments into an Instrument Rack, and had the script tell the EC4 to control 12 macros as the top 12 knobs. As long as the rack is the first device the EC4 controls Freq/Q/Gain of 4 EQ bands. Doing it this way would allow a bit more flexibility in that you could have anything mapped to the macros in your third party plugins. Maybe easier to do it that way, I’ll know for sure when my unit arrives and I can spend some time with it.
hmmm as much as I love the hardware innovations of Melbourne Instruments for a reasonable price - in terms of MIDI controllers, Electra One and Intech Studio defined the new standard for customisability.
Going back under my stone, waiting for a compact version (only one but bigger display, 4 buttons beneath it and 8 encoders in 2 rows next to it) with higher software maturity.
Of course man! Will be adding to it in due course too
Thanks for update on display too, really appreciate all you are doing. Unit itself is fantastic!
Thanks mate, I’ve done this.
I should be able to map different sets of 3rd party plugins right? I.e. using the method you specify, one set of parameters for a Juno 106 plugin (which the roto remembers for all future instances of the juno 106 plugin), one set for the P-10 plugin….etc.
I.e. just like how it works for the stock Ableton plugins?
Doing this in the options.txt file automatically exposes all the plugin parameters in Ableton (saves a lot of clicking)
PluginAutoPopulateThreshold
Line to add to Options.txt file: -_PluginAutoPopulateThreshold=64
Auto-populates the plug-in parameter list if a plug-in has a number of less or equal than X parameters.
Default = 64
Min = 1
Max = 128
128 will always populate the list with max. 128 parameters, regardless of how many parameters the plug-in has.
I wish we could map 64 knobs or more and have a step sequencer like elektron/cirklon built in too. Anyways still a great controller!
Mine just arrived moments ago. It took all of 45 seconds to set up. I’ll have a bit more time later tonight to really dig in BUT one thing I’ve noticed right off the bat when controlling a third-party (non-Ableton) plugin/VST is that Live doesn’t remember what I’ve mapped in the Configure menu unless I save the device as the “Default Configuration”
So just a heads up - all the mapping you do won’t be saved along with the device in Live unless you right click on the instrument/plugin’s header and save it that way. Otherwise next time you load it up in Live you’ll be back at stage one with nothing mapped. The Roto Control remembers mapping, so if you screw up and have to redo it, Roto Control remembers when you re-link it, but Live will cause a headache if you don’t save the config.
I noticed some burn in as well. Do we need to worry about the screens?
It seems odd that there isn’t a configurable auto-off for the screens as well. Should/will there be?
(Also, loving this things so far!)
Mine wasn’t working until I noticed the “Select Ableton Live User Library” menu in the Roto-Control app (I have my library on my Dropbox so it wasn’t seeing it).
Some more info on setup is needed in the docs fwiw. Working great now though.
Think I’ll wait for some update and manual love before I purchase