From what I understand LV2 GUIs are created separately from their corresponding LV2 plugins themselves. LV2 plugins themselves are said to have no GUI they use a generic GUI based on what audio applications provide (some form of knobs,faders, etc)
The internal Ace plugins are said to be LV2.
They appear to use the generic GUI but they also seem to sometimes include graphical elements as well, for example the EQ and Compressor.
So I was wondering,
Do these Ace plugins contain a GUI that just looks like/uses some generic elements.
OR
Does LV2 plugin language allow for these graphical additions without the need for an actual separate GUI.
Not Important:
Also never thought about/have no reason to do this but because the Ace plugins are LV2 can they be used in other audio applications that support LV2 or are they specifically tied to Ardour in some way?
Thank you for responding but I do not think it pertains to what I had mentioned.
To what you said, Ardour also allows users to opt out of installing the Harrison Mixbus GUIs during installation if desired.
Regardless what I was mentioning was how is it that ACE plugins using the “generic” (no GUI) still can show graphical elements in them, such as the ACE EQ & Compressor, they have graphical elements and generic faders in the same plugin. I didn’t think LV2 would be able to do this without having to create separate GUI wrappers for them, exactly what Harrison Mixbus plugins are doing.
Thank You
If anyone has any answers to my original post questions above, please let me know.
It’s possible to develop multiple UIs for the same LV2 plugin. Unless I’m horribly mistaken, MOD multi-fx boxes have their own UIs for pre-existing LV2 plugins.