</p>
<figure class="right">
- <img src="/images/preferences.png" alt="The Preferences window">
+ <img class="mini" style="width:600px;" src="/images/preferences.png" alt="The Preferences window">
<figcaption>
The Preferences window
</figcaption>
<ul>
<li><a href="#preferences-midi-port-config">MIDI Port Config</a></li>
</ul>
-
<li><a href="#preferences-transport">Transport</a></li>
<ul>
<li><a href="#preferences-transport-chase">Chase</a></li>
</ul>
<li><a href="#preferences-plugins">Plugins</a></li>
<ul>
+ <li><a href="#preferences-plugins-gui">GUI</li>
<li><a href="#preferences-plugins-vst">VST</a></li>
<li><a href="#preferences-plugins-audio_unit">Audio Unit</a></li>
</ul>
<li><a href="#preferences-metering">Metering</a></li>
<li><a href="#preferences-performance">Performance</a></li>
<li><a href="#preferences-video">Video</a></li>
+ <li><a href="#preferences-triggering">Triggering</a></li>
</ul>
<h2 class="clear" id="preferences-general">General</h2>
<dfn>Verbose Plugin Scan</dfn>: adds information about the plugin in the
<a href="@@status-bar">Log window</a>.
</li>
+ <li>
+ <dfn>Open Plugin manager window when missing plugins are found</dfn>:
+ when enabled</b>, the Plugin Manager is displayed at session load if the
+ session contains any plugins that are missing, or plugins have been
+ updated and require a rescan.
+ </li>
<li>
<dfn>Make new plugins active</dfn>: when enabled, any plugin added to a track
will be in active mode. If unchecked, the plugins will be added in inactive
mode by default, hence have no processing effect on the track/bus.
</li>
- <li>
- <dfn>Show only one plugin window at a time</dfn>: when enabled, only
- one plugin window will be displayed on the screen; when disabled, you
- can open as many plugin windows as you like.
- </li>
</ul>
</li>
<li>
</li>
</ul>
</li>
- <li>
- <dfn>Plugin GUI</dfn>
- <ul>
- <li>
- <dfn>Automatically open the plugin GUI when adding a new plugin</dfn>
- shows the plugins GUI as soon as it is added to the processing box. If
- unchecked, the plugin will be added in the processor box but the GUI will
- only be shown when <kbd class="mouse">double clicking</kbd> it.
- </li>
- <li>
- <dfn>Show Plugin Inline Display on Mixer strip by default</dfn> allows Ardour
- to show, in the <a href="@@audiomidi-mixer-strips">mixer strips</a>, a
- visual rendering of the effect. These Inline Display are a special feature
- of Ardour, so not all plugins are able to show this display. Most of Ardour's
- <a href="@@plugins-bundled-with-ardour">own plugins</a> have an Inline Display.
- At any time, the plugin's Inline Display can be toggled on or off by
- <kbd class="mod3n"></kbd>double-clicking it.
- </li>
- <li>
- <dfn>Don't automatically open the plugin GUI when the plugin has an inline
- display mode</dfn>: this option, available only if
- <kbd class="option">Automatically open the plugin GUI when adding a new plugin</kbd>
- is checked, supercedes it and hides the plugin GUI at creation if it has an
- Inline Display, like Ardour's own <code>ACE *</code> plugins.
- </li>
- </ul>
- </li>
<li>
<dfn>Instrument</dfn>
<ul>
</li>
</ul>
+<h3 id="preferences-plugins-gui">GUI</h3>
+
+<ul>
+ <li>
+ <dfn>Plugin GUI</dfn>
+ <ul>
+ <li>
+ <dfn>Automatically open the plugin GUI when adding a new plugin</dfn>
+ shows the plugins GUI as soon as it is added to the processing box. If
+ unchecked, the plugin will be added in the processor box but the GUI will
+ only be shown when <kbd class="mouse">double clicking</kbd> it.
+ </li>
+ <li>
+ <dfn>Show only one plugin window at a time</dfn>: when enabled, only
+ one plugin window will be displayed on the screen; when disabled, you
+ can open as many plugin windows as you like.
+ </li>
+ <li>
+ <dfn>Closing a Plugin GUI Window</dfn>: this allows users deciding how
+ Ardour should treat plugin windows aftre closing them. Hiding means a
+ complex plugin window can be re-opened fast because it's saved in
+ memory, but it uses sustem resources. Destroying means the window isn't
+ saved, which frees up system resources, however some plugins will take
+ longer to showup on the screen.
+ </li>
+ </ul>
+ </li>
+ <li>
+ <dfn>Mixer Strip Inline Display</dfn>
+ <ul>
+ <li>
+ <dfn>Show Plugin Inline Display on Mixer strip by default</dfn> allows Ardour
+ to show, in the <a href="@@audiomidi-mixer-strips">mixer strips</a>, a
+ visual rendering of the effect. These Inline Display are a special feature
+ of Ardour, so not all plugins are able to show this display. Most of Ardour's
+ <a href="@@plugins-bundled-with-ardour">own plugins</a> have an Inline Display.
+ At any time, the plugin's Inline Display can be toggled on or off by
+ <kbd class="mod3n"></kbd>double-clicking it.
+ </li>
+ <li>
+ <dfn>Don't automatically open the plugin GUI when the plugin has an inline
+ display mode</dfn>: this option, available only if
+ <kbd class="option">Automatically open the plugin GUI when adding a new plugin</kbd>
+ is checked, supercedes it and hides the plugin GUI at creation if it has an
+ Inline Display, like Ardour's own <code>ACE *</code> plugins.
+ </li>
+ </ul>
+ </li>
+</li>
+</ul>
+
<h3 id="preferences-plugins-vst">VST</h3>
<ul>
</li>
</ul>
+<h2 id="preferences-video">Video</h2>
+
+<ul>
+ <li>
+ <dfn>Video Server</dfn>
+ <ul>
+ <li>
+ <dfn>Show Video Server Startup Dialog</dfn>: when using video inside Ardour,
+ this video is accessed via Xjadeo from a source file through a Video Server.
+ This options shows the server's startup dialog (useful for debugging a
+ malfunctioning video).
+ </li>
+ <li>
+ <dfn>Advanced Setup (remote video server)</dfn> can be used when the setup
+ is more complex than opening a local file with Ardour. The tools used behind
+ the scene by Ardour allow a lot of flexibility, so for a competent user,
+ the options below are provided to access a distant file (i.e. on another
+ machine). The default options for the two following fields ("http://localhost:1554"
+ and "/") are suitable for local files.
+ </li>
+ <li>
+ <dfn>Video Server URL:</dfn> Base URL of the video server delivering the video
+ through the network (<code>http://IP-or-address:port</code>).
+ </li>
+ <li>
+ <dfn>Video folder</dfn> is the server's local path to the document-root,
+ i.e. the files that can be delivered by the server.
+ </li>
+ </ul>
+ </li>
+ <li>
+ <dfn>Video Monitor</dfn>
+ <ul>
+ <li>
+ <dfn>Custom Path to Video Monitor (xjadeo) - leave empty for default:</dfn>
+ Ardour bundles offer xjadeo bundled, so it should run flawlessly. Though,
+ for custom builds or if a newer version of xjadeo is available, one can
+ specify a path to the wanted version of xjadeo.
+ </li>
+ </ul>
+ </li>
+</ul>
+
<h2 id="preferences-triggering">Triggering</h2>
<ul>
projects / ardour-manual / blobdiff