Has anyone used the Korg Triton VST and got it to midi learn for control knobs etc…?
What’s the problem with widget assignments?
Do you use widgets? Or do you try to direct-learn your midi controller to the VST?
If the latter: This would be no good idea and would work around GP biggest advantages, which is the use of widgets. 
Think you are correct…I was trying direct. I’m on a steep learning curve😀
2 Likes
Regarding widgets, it’s probably not as steep as you think.
Anyway it’s well worth the effort!
…and if there are questions: Just ask the people of this great community! 
3 Likes
Yeah, I tried that too (trying direct), but found out how easy and flexible it is to use widgets. The Documentation on Widgets does state: “A widget is an object (such as a knob, slider, button, or meter) used to control and/or display plugin parameters.” but the last two words (plugin parameters) didn’t register at the time. Duh!
I found it’s really valuable as early as you can in your learning curve to decide on a strategy of letting GP be the interface to your MIDI CC controls usage via widget mapping.
It would probably be a losing battle to try and qualify and quantify this for every possible VST, but I’ve found that having GP handle translating MIDI CC from your controller(s) sources to VST host controls is probably more reliable and performant than having each VST separately running its own MIDI processing, however well it may do that. Very much worth making sure you know how to do this early on. It also gives you a lot more options for exactly what you want those controls to do specifically.
Anecdotally I do think this approach can bring significant gains in reliability and performance overall. I’ve tried a lot of tests both ways and it feels that way to me.
3 Likes