I use the power supply! They visually jump. Quite badly, like almost from 2 to 3 o’clock in the worst cases (when using stepped controls).
Oh, that doesn’t sound good! I’d contact their support (they are helpful though in Aus so time zone can be a bit awkward) and/or the retailer
Have communicated with them about these jumps already (the device doesn’t seem to be very accurately responsive to MIDI itself).
I also mentioned this before, when fw 1.1.2 came out.
I don’t have massive jumps, but fine stuttering, like some short delay in sending/receiving midi info. Sensation is like i placed indent (which i haven’t).
But it used to happen more often before, now it’s very random and not as often.
I did change location where i plugged power brick in, so this could helped, not sure to be honest.
With original firmware i haven’t had this issue. So it could be this
Ah yes this is what I have too. Will keep on at their support then, they didn’t sound like they were aware of an issue. Not a huge problem but would be nice to solve
Did you by any case made/recorded some automation without knowing?
Check this as well because knobs will react to it
I also think the poor MIDI reception is what’s causing the Octatrack audio CC dump to fail (the Rotocontrol sends the message and the OT receives it and spits out all the CCs, but the Roto doesn’t update any of its values to reflect those CCs). Tested all this extensively. Melbourne’s support response glossed over the fundamentals entirely and haven’t seen any indication that they understand this is an issue as yet.
I have not really tried. As I use it more to create a preset atm.
It is very obvious if you set stepped controls. E.G. 7 Steps on the new Ableton SQ device for an octave step. It moves around as crazy. I thnk because the automatic CC values are very close to the threshold value between octaves. Only as small position error then leads to some back and forth between ableton and the knobs move with a big delay. Close to the delay of the screens when you switch pages…
I was thinking is it possible to implement light sensitivity for dark rooms, like we have for touch sensitivity? @Honeysmack
I have had the jumping knob problem once or twice. Yesterday the roto was getting stuck on one plugin no matter which one I’d select until I restarted ableton. I’ve also had it just stop working entirely until I reboot the device. Definitely some bugs with this thing so far but I’m hopeful that Melbourne will iron these things out with firmware updates. They’re a relatively new company doing some really cool new stuff that I’m really stoked on so I’ve got a lot of patience. I am just using this thing for recording though, I would not rely on it for live performance.
I’m unable to rename knobs anymore on the roto control. I rename one and it changes for a split second before resuming to the name it originally took from the “Configure” section in Ableton. It also does it for native plugins as well. Renaming buttons is fine if it’s set to steps but otherwise it’s the same issue as with knobs. Anyone experienced this and have any solutions? Thanks.
I got mine Tuesday, set up yesterday only to be so disappointed in how it works or lack of.
I tried numerous ways in a stand alone setting only, given there is a 2 page instruction manual that explains almost nothing for controlling hardware, the video tutorials are similar, I am in mind of returning my unit.
The major issue is, my Iridium Core, it only works via 5 pin Din, so both in and out are utilized on the Iridium with no ability to further sequence it. I did try the USB host function where the Iridium sees the Roto Control but it does not see any MIDI information at all. I have all settings correctly set in the Iridium, but again it only works with 5 pin MIDI din, which means I can externally sequence my Iridium.
Which brings me to my next point, using my HAPAX, as I have more than 1 input and 1 output, I was able to create the MIDI loop required, but after writing some MIDI automation, the knobs would cease movement are would require coercion to get them to work again, then they would cease.
I either have a faulty unit but it does not behave this way with the Iridium, The HAPAX USB host does not pick up the ROTO either.
I am simply missing something or the 2 page manual just not explain how to use the ROTO in USB mode to control hardware without having to create a closed 5 pin din MIDI loop that isolates that device from external sequencing.
I know there are work arounds like introduction a 5 pin din MIDI merger and splitter, which I have both, but a USB bi-direction 1 cable solution seems the best most viable option for this control surface.
Has anyone else experienced these issues or is my unit faulty?
Are you using the included power supply? I found that not using it caused flaky issues. Especially with the knob recording.
Yes I forgot to state this, I am using supplied PSU and if I don’t, I get a power warning for both the HAPAX and Iridium from the ROTO, which means they cannot power the ROTO from Host USB.
This bug has been fixed, grab the latest firmware version released today: Roto-Control firmware 1.1.4 and PDF manual
Also the Roto-Control PDF manual is also available to download.
Awesome stuff!
I’m not sure if this doesn’t exist yet, but the link in the manual where you say about getting Roto templates just sends to the home page.
awesome! please implement a page select in plugin mode. eg when clicking both arrows and then one of the buttons. maybe also a i to name pages in the roto app (rn “1-8” to something), those names are shown when clicking both arrows. to me this is the most crucial feature which is missing atm.
+100, I really wish we could do this. I actually hacked together my own version using Max and a remote script, where you can dedicate certain buttons as page switch buttons and then it sends the MIDI command to change page when you press them. It makes navigating large devices so much more pleasant. But a native solution like you describe would be nicer as you don’t have to give up buttons and do weird hacks!
Quite impressed so far - only used in Bitwig with the DrivenbyMoss script. Look forward to official support and how the box develops