manual/include/working-with-ardour-built-plugin-editors.html
Shamus Hammons 7a4c28bd86 Rearrangement and cleanup of Part I.
This includes rewriting out all of the "you" language that was peppered
throughout, fixing inconsistencies in layout, and removing <br>s
wherever they were misused and unnecessary (which was quite a lot).
2017-02-24 23:30:29 -06:00

30 lines
998 B
HTML

<p>
To view a plugin editor, double-click on the plugin within the
<a href="@@processor-box">processor box</a>.
A new window will appear showing the editor/GUI for the plugin.
</p>
<p class=fixme>Add a pic showing the generic GUI</p>
<p>
If a plugin does not have its own GUI, Ardour will construct a
<dfn>generic plugin editor</dfn> from a small set of common control
elements. Ardour will do this even for plugins that have their
own, if <kbd class="menu">Edit &gt; Preferences &gt;
GUI &gt; Use Plugins' own interface instead of Ardour's</kbd> is disabled.
</p>
<p>
The generic UI can be temporarily switched to by context-clicking on
a processor and selecting <kbd class="menu">Edit with generic controls</kbd>.
This is necessary in order to access the <a href="@@automation">plugin
automation controls</a>.
</p>
<p>
In the generic UI, any controller can be reset to its default state by
<kbd class=mod3n></kbd><kbd class=mouse>Left</kbd>-clicking on it.
</p>