For the sake of completeness, I also tested the CC1 with ProTools 2025.12 under macOS 14.4.1 in HUI-mode (obviously).
It works to a certain extent, but integration is half-baked. Channel selection between screen and device is not synced automatically and not easy to grasp visually, either (… that’s more of a ProTools GUI-specific issue, though). While volume fader and panner movements are written and read, even the most basic automation rides using the fader suffer from strange jumps when releasing the fader physically:
… bottom line: HUI-Mode is a nice add-on, but certainly no reason to buy this little box. What’s more, I didn’t succeed using HUI-Mode with Nuendo 12 (which isn’t supported by CC1 natively, like pointed out above). But maybe I’m just missing important settings. YMMV!
EDIT: PS: Oh, that’s an issue in Nuendo 14, too. 8-/
I have a Nektar CS12 at the editing station, which handles auto-banking flawlessly. It has 12 freely programmable potentiometers for each individual plugin. I also have an Elgato Streamdeck, which allows for very complex control of Nuendo. In principle, this combination replaces the CC1. The CC1 is too late for me in this regard.
And at another workstation, additionally, the Softube Console 1 Fader. Flawless autobanking.
The CC1 would have been interesting a few years ago.
Yet another addition to my findings: CC1 in fact will control Nuendo 12 in HUI Mode! This depends on the settings in CC1’s “Control Center” app which has to be used to invoke the mode by selecting ProTools as the target DAW. Quite logical, isn’t it? ;-D
Nevertheless, the implementation achieved that way is cumbersome, to say the least. There is no indication of selected tracks, let alone a bidirectional dependency between the selection on the screen and on the device. In short, apart from occasional fader movements, this is useless in Real Life.
Oddly just purchased this and this top page “SelectCH Control Basic” is missing for me. Any idea how to get it on there? When I add + for a CC1 Demo…it’s oddly there, but not on my actual device. Ugh.
Doesn’t Steinberg/Yamaha have product managers to interact with the user base? I have an Avid S3 and whenever I’ve needed help, Eddie on Avid’s forums has always been around to support and bug fix.
If the CC1 is currently not configurable, wonder if this is something they are planning on opening up?
I’ve always been interested in the AI knob, but how different is it from using a mouse scroll wheel? Does it control parameters which is not controllable by the scroll wheel?
I have already returned my test device, so I can’t check and say it with 100% certainty, but if I remember correctly, you simply have to move the mouse pointer over any parameter value in Nuendo to change it by turning the wheel as long as that “AI”-button is lit. - But then, I might as well have tried only features that react to the mouse-wheel, too.
No, it’s the opposite way, in fact. Some parameters are controllable by the scroll wheel, but not via the AI Knob.
The main advantage is that using a knob often feels much more comfortable (and natural) in comparison to use scroll-wheel.
Another advantage is that you can Lock AI Knob to a dedicated parameter. Then you can Write and automation and focus on the sound (not to keep the mouse over the given field, etc.).
Hi, you can use any midi controller with knobs on it to assign one knob to Ai knob in remote devices. Works quickly on all the Steinberg Channel strip parameters/EQ etc. You will have very limited mileage with third party plugins.
Unfortunately this AI knob thing is badly implemented. Simply because it works on some stuff and doesn`t work on others. That alone for me kills it. I dont want to remember where it works and where it doesn`t. And to be honest I don`t really feel a need for using a knob unless it is a dedicated controller (for an EQ or pan, for example). Mouse scroll (with shift for fine adjustments) works perfectly and every time, I got used to the feel by now. Ive had other AI knob products and in the end didnt bother with it.
This controller not being completely customizeable, even if only within Yamaha`s own environment, i.e. Cubendo, is absolutely ridiculous.
But it is also the responsibility of third party VST3 plugin developers to implement the correct code for knobs to be controlled with the Ai control……… But maybe that was never gonna happen!
Yeah well I`ve yet to see a VST that doesnt accept scroll as an input for knobs and faders. So if Steinberg cant figure a way to make the marvellous and revolutionary AI Knob work where any mouse works, for me that`s a problem. Not to mention that you still you have to hover you mouse at the control and then use your other hand to turn the knob, instead of just scrolling.
I dunno, maybe older people have a muscle memory for turning knobs or something, and it really makes a diference for them, but for me the scroll really works just fine.
Now, if they gave me a dedicated EQ surface, with HPF and LPF, and knobs for LR and FR pans, including stereo combined pan, where I can just go about turning multiple parameters at once and listening at whatever channel I have selected, then I would say that is useful.
One knob to just do less then what I already can with the mouse scroll, no thanks!
I agree, but not being a programmer I can’t understand how the ‘mouse’ hover over a knob, fader, slider of any VST could be then captured for any paramater command control (on any available VST/Vsti) it might be possible to implement, I donno. I do get what you’re saying about the limitations:-)
Hopefully I don’t have my hopes too high but I’m hoping we get access to whatever protocol Yamaha/Steinberg is using to assign the commands they currently have and we can assign the AI knob or the other knobs to duties like fades, trim, moving events, event volume handle, etc. - things that you can do with an avid transport or dock. There are default knob commands for zoom (although only horizontal (?)) and jog. It’s 2026…we were supposed to have flying cars by now- seems like this ain’t too much to ask for.
…