So I stumbled across this:- If you download and install Yamaha MOXF Remote Tools it provides a controller extension in Studio Setup which has AI control included.
If you create the following mapping on an external controller:-
AI Wheel/Rotary = CC60 ( 2’s Complement*)
Jog Button = Note A#7 (Toggle)
Lock Button = Note B7 (Toggle)
*Values 1-63 for increments, 64-127 for decrements - At least I think that’s 2’s complement mode.
Then assign that MIDI device as the input of the MOXF extension you get the following control from a generic device:-
Quite handy now that the CC121 is near impossible to get hold of. I know some people are curious to get a taste, so this may be helpful for those.
Other elements exist within that extension, so you have to be careful not to send:
E5 to A#5 (Transport)
C3 to F3 (Assignable Switches)
F# to B2 (F1, F2, etc. buttons)
F#3 to B3 (Assignable Switch Banks)
And also MIDI CC28 to CC39 controls 4 band EQ mappings for Q, Freq & Gain.
So unless you want to map to those also, a virtual pipe may be preferred to separate the AI controls.
Even more than cool @skijumptoes !
I am setting up a page of 8 encoders as well the large wheel so that you can tap a knob n the plugin in and press the encoder button and it locks, locking up to 8 parameters on the fly.
What I mean is, sometimes when dialing in on a couple of tracks, its the interdependence of a number of parameters that might normally be on disparate areas etc.
It certainly opens up some nice options. The only thing that really irks me is that you can change pages on the VSTi racks using a mouse scroll. But the AI knob won’t change them!!! Arrrrggghhhh haha.
That would’ve been really nice to have paged instrument controls using the VST QC’s - AI knob locked on the page turn element… So close… yet so far…
Also I’d quite like to have been able to scroll through presets for inbuilt plugins like retologue when the browser screen is open.
Yeah the AI Knob in MIDI Remote works fine for me last time I tried it. Just hold mouse over a control that responds to mouse wheel movements (Such as console fader) and it controls it.
I presume the mapping, as screenshotted, works for other mapped parameters?
All the other remote mapping kind of works, except eg I have to open and close a plugin window twice so that it actually refreshes the focused plugin, you can force the inspector to open the IFX page as it only has next/previous etc yet the eucon protocol does all this ie there is no direct address of a page and a bunch of other frustrating half bakes…but I digress
I’ve never owned a 121 but I’m Making a large 75mm (like a skateboard wheel, but heavy) as a large endless scroll wheel (eg like a mod wheel) and a teensy board to manage the encoding and midi etc to usb. This is because using even using flip faders on nearly any surface…although much better than a knob is still clumsy and the knobs on the avid mix are very tacky in feel. They also then become visually cued. Ive found especially with FX its much better to close your eyes and have no idea of extents. It really improved mix automation and I trialled it with a pseudo version using mod wheel scrolling…its just WOW!
Then I restumbled on the 121 software…so I gather thats what it does. You can hold your mouse over any IFX knob, hit write and automate then move on. I can also lock the pointer focus and still be able to use the mouse. Do I have that correct?
I have boiled down my control hardware to basically and Artist Mix and Avid control on the ipad and a small iconpad with 8 knobs mostly just for IFX edit and a razer tartarus with gesturing so the ergonomics and reach radius can really be any smaller. Amazing…finally satisfied with most of that
Except
Going through the rigmarole, having to hook up QC etc, when a 1 off stuff especially, I thought wouldnt it be good to just hold my mouse over any control, hit write just like the 121
So excuse my naivety but I assumed you just map the AI value in remote to a surface element, then hold your mouse over a knob and the surface element should now do the scrolling?
The only thing you have to be careful of is that if you map '“Value at Mouse Pointer in Lock State” then that needs to map to a button that you can toggle on and off as it has to return to zero state to release.
If that remains in the ‘on’ state (i.e. non zero) then you will not be able to map on the fly as it’s locked. So perhaps that’s the issue you are encountering? The wording isn’t great as it reads as though that mapping is the value control but it’s not it’s the lock toggle.
You should be able to see when the AI knob is mapped as the MIDI Remote graphic goes orange.
Some VST’s don’t support the AI method depending on if their parameter exposes to the mouse wheel I think, so be sure to test it on something reliable such as the volume controls in Cubase.
