From 19557e67c6f46c3785ef4f05167cb491c744f81e Mon Sep 17 00:00:00 2001 From: Paul Davis Date: Tue, 5 Mar 2013 09:44:24 -0500 Subject: [PATCH] new page on getting plugins, tweak working with plugins page --- _manual/11_working-with-plugins.html | 65 ++++++--- .../06_getting_plugins.html | 129 ++++++++++++++++++ 2 files changed, 172 insertions(+), 22 deletions(-) create mode 100644 _manual/11_working-with-plugins/06_getting_plugins.html diff --git a/_manual/11_working-with-plugins.html b/_manual/11_working-with-plugins.html index d36b03e..2f47346 100644 --- a/_manual/11_working-with-plugins.html +++ b/_manual/11_working-with-plugins.html @@ -4,34 +4,55 @@ title: Working With Plugins --- - -

Plugins are bits of software that get loaded by Ardour in order to:

+ +

Plugins are bits of software that get loaded by Ardour in order to:

-

Plugins are written by 3rd parties, and Ardour supports a variety of different plugin standards:

+ +

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 some + information on how to get them.. +

+ +

+Ardour supports a variety of different plugin standards: +

-
LADSPA
-
An early, simple, lightweight plugin API, audio effects only, plugins have no editors/GUI of their own
-
LV2
-
An extensible, full-featured plugin API, audio and MIDI, plugins can provide their own editors/GUIs
-
AudioUnit
-
OS X only, full featured, audio and MIDI, plugins can provide their own GUI
-
Linux VST
-
Plugins using Steinberg's VST plugin standard but compiled specifically for Linux
-
Windows VST
-
Plugins using Steinberg's VST plugin standard but compiled for Windows. Support for this plugin format is not available in regular builds of Ardour. Read more... -
-
-

Adding/Removing/Copying Plugins

-

Within Ardour, plugins are just another type of Processor and so the techniques for adding/removing/copying/moving processors apply to plugins as well. These techniques are covered on the Processor Box page.

- +
LADSPA
+
An early, simple, lightweight plugin API, audio effects only, + plugins have no editors/GUI of their own (Ardour provides one, however).
+
LV2
+
An extensible, full-featured plugin API, audio and MIDI, plugins can provide their own editors/GUIs
+
AudioUnit
+
OS X only, full featured, audio and MIDI, plugins can provide their own GUI
+ +
Linux VST
+
Plugins using Steinberg's VST plugin standard but compiled specifically for Linux
+ +
Windows VST
+
Plugins using Steinberg's VST plugin standard but compiled for + Windows. Support for this plugin format is not available in + regular builds of + Ardour. Read + more... +
+ + +

Adding/Removing/Copying Plugins

+

Within Ardour, plugins are just another type +of Processor and so the techniques for +adding/removing/copying/moving processors apply to plugins as +well. These techniques are covered on +the Processor +Box page.

{% children %} diff --git a/_manual/11_working-with-plugins/06_getting_plugins.html b/_manual/11_working-with-plugins/06_getting_plugins.html new file mode 100644 index 0000000..4277a48 --- /dev/null +++ b/_manual/11_working-with-plugins/06_getting_plugins.html @@ -0,0 +1,129 @@ +--- +layout: default +title: Getting Plugins +--- + +

Where do I get plugins from?

+ +

+The following list shows plugin packages. In some cases, a package contains just 1 or 2 plugins; in other cases, dozens. +

+ +

LADSPA

+ + + +

LV2

+ + + +

Linux VST (LXVST)

+ + + +

How do I install plugins?

+ +

Linux

+ +

+ Installation will vary a little depending on how you get plugins. If + your repository has a particular plugin package, just install it using + the normal software package management tool for your system. +

+

+ If the package isn't available, then you can build the plugins from + source (plugins are generally fairly easy to compile). LADSPA Plugins + need to be installed in either /usr/lib/ladspa, /usr/local/lib/ladspa + or in a directory mentioned in your LADSPA_PATH environment + variable. +

+

+ LV2 plugins are distributed as folders/directories. They need to + installed in either /usr/lib/lv2, /usr/local/lib/lv2 or a directory + mentioned in your LV2_PATH environment variable. +

+

+ Linux VST (LXVST) plugins are distributed as shared library + files. They are typically installed in /usr/lib/lxvst, + /usr/local/lib/lxvst or a directory mentioned in your LXVST_PATH + environment variable. +

+ +

OS X

+

+ Unless you're a particularly technical computer user, building and + installing plugins in the LV2 (or LADSPA) format is probably not + something worth planning on. Ardour releases for OS X ship with a + collection of many LADSPA plugins, some of which are very useful and + some of which are outright buggy. +

+ Most of the plugins you are likely to use on OS X will be in Apple's + AudioUnit format. These have their own installation process that tends to + just work. +

+ -- 2.37.2