But in the VSTi rack, knob#1 is mapped to volume. For example, in a particular VSTi, Arturia choose to map knob#1 to filter cutoff.
These parameters are viewable (& changeable) within the VSTi (& many have a lot more than 18 parameters!) but I tend to leave them, using my mouse for the rest.Īs I mentioned at the start, with QCs activated, the 8 assignments seem to override the VSTi mappings. when the controller is in ‘Analog Lab’ mode, the 18 knobs & faders are pre-mapped to 18 of the specific VSTi parameters chosen by Arturia to be the most useful. The Generic Remote is set up as INPUT: Keystation Mk3, OUTPUT: Not Connected.Īs a recap, the whole point of this is to be able to use my Arturia controller in the way Arturia intended with its V Collection VSTi’s, i.e.
Hi Martin, thanks - I’ve looked at MIDI Filter & nothing there. Why would these MIDI CCs not be registering? Cubase’s MIDI meter shows an input, & the corresponding controls on the VSTi move too - so why don’t they show up in the MIDI Monitor? I checked MIDI Filter under Preferences & couldn’t see anything odd. This time the knob assigned to MIDI CC 28 worked, but none of the others did. I then tried some more MIDI CCs - 20 to 28 for the knobs & 52 to 60 for the sliders. for brightness, timbre etc.) & all knobs/faders triggered a response with the CC number shown. Selecting Analog Lab mode (with ‘standard’ MIDI CC assignments like 74, 73, 76, etc. So I loaded up a MIDI Monitor Insert & sure enough the knobs/faders were not registering. Whilst they affected the VSTi controls in real time as desired, the MIDI wasn’t recorded. bank of MIDI CCs) & assigned the knobs/faders to MIDI CC 102 - 119 (undefined according to Arturia). However, whilst I played around with it in Cubase tonight I noticed something odd…Ĭertain MIDI CC messages were not recording. I think I’ve got my head round the differences between automation tracks & MIDI CC ‘automation’ (bad term I know). Haha, agreed! It was much simpler back in the early 90s when I first used Cubase on an Atari! I can only assume it’s a manufacturer-specific script that works behind the scenes in Cubase… I’m not sure a screen recording would illustrate it any better than what I have described?įundamentally, since these CCs are not the ones used for the QCs (neither Track nor VST) then technically automation shouldn’t be able to be written - but it is! That’s what I don’t understand. 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.
#Arturia analog lab as vst plus#
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)
