I use Reaper.
In short, automation host in not provided by GP but by the plugin itself?
Your explanation is really clear, I understand now why some plugins show meaningless captions or nothing in the mapping window.
And it is true that when midi control is enabled for these, modifications are not followed.
I understand better now the process.
Yes Host Automation is provided by the plugin and Gig Performe uses that.
When you see meaningless entries in the Parameter List you have to enable the Host Automation in the plugin itself to use it.
For example Kontakt or Omnisphere
Exactly - Gig Performer loads plugins and communicates with them directly via its SDK using function calls. So when a widget is âlearningâ a parameter, it is waiting for the plugin to call back into Gig Performer through a function when you touch or move a parameter in the plugin editor.
No MIDI involved.
Thank you everybody, Iâll sleep tonight less ignorant.
One note on this plugin. While it is an absolute steal for $9.99US, I had to buy two licenses for my two laptops as the iLok security strictly enforces only a single install per license.
Ah, it uses iLok â they just lost me as a potential customer.
The thing is, youâre not really learning MIDI â thatâs just the underlying mechanism. Youâre really learning an external control.
Saying âLearning MIDIâ here would kinda mean that instead of saying âLearn Parameterâ, we would have to say âLearn Index Numberâ
What about âCapture Controllerâ?
Interesting â love this brainstorming â your suggestion makes me think of this:
âAttach controlâ
I subjectively consider myself quite objective in terms of UI items being intuitive. The âLearnâ button in the âMidiâ settings is perfectly fine as it is IMO. So the one that could possibly change is the âLearn parameterâ. In terms of what the button is doing, it is giving you the option to map the parameter to the widget from the plugin window, rather than from the parameter list above. So a slightly longer button name called âMap from pluginâ with the corresponding tooltip when you hover your cursor over the button, is my suggestion.
If the word: Learn in âLearn Parameterâ should be changed to avoid confusion (it is suitable in midi parameters), why not âMap ParameterââŚ
As a non native English speaker, I am probably not the best to do suggestions regarding wording. But I think the difference between âlearnâ and âattachâ/âmapâ, is the notion of âlook at what I am doing and memorize itâ (learn from an example). So âlearn from MIDIâ and âlearn from pluginâ would be perfectly clear to me, while âattach controlâ or âmap somethingâ doesnât reflect that fact that it comes from a example from a MIDI controller or a plugin window.
Being (still) a newcomer in the world of plugins and having initially only an experience of MIDI for controlling hardware synths, the notion of âhost automationâ was not obvious to me and I thought that plugins were controlled by MIDI too. (booooh⌠loooser⌠OK, I knowâŚ
). I learned in this community that it is not the case. But I still remember that it was confusing to me, probably because I never found a clear explanation âthis is MIDI and this is host automationâ or perhaps I went through the explanation. Thus to tell that I can figure out where the confusion comes from.