V.2.0 is feeling pretty tight for me, coming from the Bitwig beta version.
Things seem well thought out, my touch sensitivity issues are pretty much resolved, screen updates seem smoother now…
Bitwig doesn’t 100% every time register touch release when touch recording automation for me, but it is mostly spot on now. No other touch issues at all.
Feeling pretty good about early adopting the Roto as my primary controller of choice.
A few things that could be done yet to fully “bling” it up, will be sending some suggestions in, but yea, this is a solid piece of kit!
7 Likes
Can anyone using Live and Roto report if everything function well?
1 Like
-
I guess it’s stored in the RC as other “learn” devices ?
Using automapped rack/macros won’t impact internal memory. -
is the total limit still 64 ? (I need waaaaaaaay more)
This is currently correct, although you can import/export more! -
Is it linked to the name of the Rack (as, the name on the device title bar in Live ?)
Yes, giving racks unique names is essential as Roto looks for the name.
1 Like
Thanks.
The 64 limit is a big issue to me.
In my case, I use the Roto Control mostly with a custom M4L device. Since I want to customize the knobs + names of this device for each Live Set, the only way I can achieve it is to give the device its own unique name for each Live Set. So I reach the limit very fast.
At least having a separate 64 memory for Stock Plugins and another one for M4L would be ok.