Yes your method seems good to me, especially if you switch between DAW, and there are some case when you can only midi learn parameter that aren't exposed as VST parameter (i remember MOTU BPM has no vst parameter but only midi learn, and Fabfilter Pro Q give the ability to control the selected filter with midi learn but it's not exposed as VST Parameter - instead filter 1..N is exposed as vst parameter) , but two things i like from Control link more than midi cc learn , Control link can transmit data to controller (useful when you have ring led, screen or motorized fader) and you don't have to create a midi(instrument track).chk071 wrote: Fri Apr 16, 2021 9:24 pmI've been fiddling a bit with it recently. Still don't like it. The track quick controls are too limited, and the VST quick controls are something I probably will never get my head around. I read the manual, I read some explanation attempts on the Steinberg forums, and I still don't get it.jancivil wrote: Fri Apr 16, 2021 6:35 pm I'm glad I have not a lot of need for Cubase's quick control or vst control, it's kind of pathetic, insanely outdated.
The best implementation for me to date is Studio One's Control Link. I don't use it anymore though, because, when you learn your controller for it, you lose the ability to use VSTi's internal MIDI learn (obviously... it basically just overrides the "normal" MIDI CC messaging), which basically renders stuff like Komplete Kontrol useless.
I went the "no bullshit" route now: Don't learn the MIDI controller for Control Link at all, and use the softies internal MIDI learn. Means I have to use controller templates for Largo and V-Station, as they don't have a MIDI learn system, but, that's alright. Bit of work going through the MIDI CC lists of those instruments is a nice sideline as well.And, for V-Station, my keyboard even had a built in template, as it's from Novation.
There's something else i have not test is the difference in resolution, i have noticed for example that inside native instruments maschine software if you insert a vst ,the resolution to control a vst parameter is finer -i can access to extra step value- than using maschine in midi cc mode (do not remember how was the resolution in maschine mackie mode).
I noticed the same with Softube Console 1 , the resolution is finer when i control Console 1 plugin the way it was design for (with the additional software layer called Console 1 on screen display) than if i control Console 1 plugin with Console 1 hardware in midi mode.
Maybe it's because when these hardwares use their dedicated software there aren't using midi cc resolution... i don't really know
Not only related to cubase or s1 but according to you , problem with sample accuracy automation is more a DAW problem or more a plugin problem? (i remember that depending on the vst when i increase or decrease the sample buffer the timing of the automation moved - sonically not visually, i have to make some test because i ve read that it was a VST2 problem and should be ok with VST3)
regards
