Hello,
I have a layer loaded with the VST Analog Lab Pro.
The keyboard is an Arturia KeyLab mk3 (not essential mk3 but the new mk3).
From the layer, when I go in edit of the VST, I can change the presets, edit them etc, everything seems fine except that the 9 rotary encoders and 9 faders from the the KeyLab just don’t work.
Normally they’re pre-mapped to control some parameters (timbre, color, morph, motion etc) in the presets.
In midiOX I see that those knobs do send the expected CC messages.
Am I missing something ?
… we’ll release today a new Pre-Release 2.1.4, later the day. Please re-try it with that version.
/Michael.
Hi Michael,
Thanks for the -as always- fast response.
Tried with 2.1.4 : the midi monitor works and shows the notes and CC messages.
Question : is it normal that we don’t get to see the midi channel on the monitor ? It could have helped me understanding the issue that follows.
There is a strange behavior of the KeyLab mk3 controller in the sense that when set to ch 11 for instance, it sends the notes on ch11, but the CCs of the rotaries and faders always remain on ch 1 ; I contacted Arturia to check if this is as expected.
Having understood this ch 1 issue, in Cubase I was able to use the AnalogLab VST almost as expected :
→ when set to any channel other than 1, notes work fine but faders and rotaries don’t.
→ but when set to ch 1 then everything works, including the faders and rotaries (you see them moving on screen, and hear the effect).
In VSTL, I tried to replicate but couldn’t get any fader or rotary moving on screen while I was physically actioning them on the controller.
After an hour of hair pulling I realized that while there’s no visual feedback on the VST window, the effect is anyhow applied and audible.
Is this “visual feedback issue” on the Arturia side or on the VSTL side ?
The status column shows it in the 2nd digit in hex notation - 0 to f, where 0-9, then a = 10, b = 11…up to f = 15. Add one if you count channels 1-16 instead 0-15.
So status 9d means note on on channel 13 (counting from 0).
Did you resolve your issue? It’s a bit hard to follow.
@musicullum
Sorry for the delay in responding, it took a while to sort this one out with Arturia.
Recap :
Running the Analog Lab VST on the pc.
Using Arturia’s Keylab mk3 controller.
Normally the controller has an “Arturia” mode that allows deep interaction with Analog Lab. It works fine when Analog lab runs in stand alone and it is supposed to also work when AL is as a hosted VST.
I couldn’t get this interaction to work neither in Cubase nor in VST L.
In Cubase, Arturia support had me deactivate the MIDI OUT port that the controller creates. This solved the issue.
They don’t support VST L (!) but I tried to apply the same method and removed from VST L the MIDI OUT port.
This allowed the controller to somehow finally “see” the instance of Analog Lab : the name of the preset loaded in the layer now appears on the controller screen, but the full interaction still doesn’t work.
It is still impossible to edit the preset from the controller and the faders and encoders on the controller still don’t have any effect.