If I then went inside Analog Lab & assigned that knob#1 to LFO rate, a new automation lane would be created for LFO rate. So when I put the keyboard in Analog Lab mode with WRITE automation enabled, moving knob#1 writes automation for the LP filter cutoff. For example, knob#1 in Analog Lab mode is mapped to CC 74 which for many sounds is linked to LP filter cutoff. The automation parameters are all of the Analog Lab pre-mapped parameters such as cutoff & resonance, plus a few other things specific to whatever sound is loaded inside Analog Lab VSTi.Īnalog Lab mode on the keyboard is basically a read-only factory template of MIDI CCs. If I go into Remote Control Editor & reassign the 1st VST QC slot to filter cutoff using the learn function, & then set Track QC to follow the default VST QC, all is well. the 1st knob referenced above controls cutoff.
If however I deactivate QC (via the button in the inspector) AL behaves as per standalone mode, i.e. However, when firing up Cubase & loading up AL in a track, the 1st Track QC slot is labelled “Master”, which means that the 1st knob on the keyboard controls volume despite the GUI in Analog Lab showing it as controlling “Brightness” (aka LP filter cutoff) like it did in standalone mode. I ask since I get the occasional conflict with my Arturia KeyLab Mk2, a major selling point of which is that it auto-maps to Arturia’s Analog Lab VST, plus the majority of its V Collection VSTs.įor example, when loading up Analog Lab as a standalone VST, all the knobs & faders behave as designed. When viewing Remote Control Editor for both Steinberg & 3rd party VSTs, I’m curious what decides the default parameter assignments to the VST Quick Controls. Possibly one for an Arturia-specific forum but maybe some Cubase issues too…!
0 kommentar(er)
