ardour/manual
13
0
Fork 0
Code Pull Requests Releases Activity

updates to add version feature added for OSX VST, and OSC

Browse Source
This commit is contained in:
Len Ovens 2017-02-02 08:03:18 -08:00
parent 8fa0f54153
commit 374491ad08
3 changed files with 17 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
_manual/13_working-with-plugins.html
View File

@ -14,14 +14,22 @@ title: Working With Plugins
</ul>
<p>Ardour does not come with any built-in signal processors of its own
(other than volume faders) and it also generally doesn't ship with any
plugins. They are written by 3rd parties, though we do provide <a href="/working-with-plugins/getting-plugins/">some
(other than volume faders) but does ship with a small group of
plugins starting at Ardour 5.0. The shipped plugins are listed as authored by "Ardour Team"
and named with "a-" as the start of the name (Like a-EQ) or Authored by
"Ardour LUA Task Force" in which case they are example (but still useful)
LUA scripts. The included plugins are LV2 or LUA scripts and use
Ardour's generic GUI. They work on all supported platforms so that
projects started on one platform will sound the same on another platform
if they use just these plugins or other plugins that
are cross platform.
They are written by 3rd parties, though we do provide <a href="/working-with-plugins/getting-plugins/">some
information on how to get them</a>.
</p>
<p>
<h4>
Ardour supports a variety of different plugin standards:
</p>
</h4>
<dl class="narrower-table">
<dt><abbr title="Linux Audio Developers' Simple Plugin API">LADSPA</abbr></dt>
@ -31,7 +39,8 @@ Ardour supports a variety of different plugin standards:
<dt><abbr title="LADSPA Version 2">LV2</abbr></dt>
<dd>An extensible, full-featured plugin API, audio and <abbr
title="Musical Instrument Digital Interface">MIDI</abbr>, plugins can provide their
own <abbr title="Graphical User Interface">GUI</abbr>s</dd>
own <abbr title="Graphical User Interface">GUI</abbr>s but may use the
one Ardour provides instead.</dd>
<dt><abbr title="Audio Unit">AU</abbr></dt>
<dd>OS X only, full featured, audio and MIDI, plugins can provide their own GUI</dd>
@ -40,8 +49,7 @@ Ardour supports a variety of different plugin standards:
<dl>
<dt>on Linux</dt><dd>(native) Linux VST plugins fully supported (VST2.4)</dd>
<dt>on Windows</dt><dd>(native) Windows VST plugins fully supported (VST2.4)</dd>
<dt>on OS X</dt><dd>Not supported, unless you use a VST&lt;&gt;AU
bridge plugin. Similar to Apple's Logic DAW.</dd>
<dt>on OS X</dt><dd>(native) macOS VST plugins fully supported (VST2.4) since Ardour 5.5</dd>
</dl>
</dd>

2
_manual/25_using-control-surfaces/01_controlling-ardour-with-osc/03_querying-ardour-with-osc.html
View File

@ -13,7 +13,7 @@ title: OSC&#58; Querying Ardour
as often as it needs this information. It may well make sense to use
regular feedback for things that need to be updated often such as
position or metering.
Here are the commands used to query Ardour:
Here are the commands used to query Ardour: (added in Ardour 5.5)
</p>
<dl class="bindings">

1
_manual/25_using-control-surfaces/01_controlling-ardour-with-osc/06_osc-personal-monitoring.html
View File

@ -6,6 +6,7 @@ title: OSC&#58; Personal Monitoring Control
<p>
Personal monitoring can allow a performer with a smart phone to set
their personal monitor mix for a floor wedge or inear monitoring.
In Ardour 5.6 OSC commands to allow this were added.
</p>
<h3>Setup</h3>
<p>