X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fgetting-more-plugins.html;h=eb7a301f3803874ce44eab260a1a1893ca1f5327;hb=92eedba4c74daf267fc1b17a561458cb15dc7ec1;hp=688f6339a009d29beb16b6e3c879e56e5d3210ed;hpb=081e7af0b6f6dec0ca685d3a538eacf20394c2cc;p=ardour-manual diff --git a/include/getting-more-plugins.html b/include/getting-more-plugins.html index 688f633..eb7a301 100644 --- a/include/getting-more-plugins.html +++ b/include/getting-more-plugins.html @@ -9,64 +9,37 @@
- 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. Most - Linux distributions that are good for audio work will have most of - the LADSPA and LV2 plugins mentioned above available in ready-to-use - forms. + Installation will vary a little depending on how the plugins have + been obtained. If a particular plugin package appears in the local repository, + installing it using is done by using the normal software package management + tool for the system. Most Linux distributions that are good for audio work + will have most of the LADSPA and LV2 plugins mentioned above available in + ready-to-use form.
- Finding them will typically require searching your + Finding them will typically require searching the distribution's repository to find the name of the package. The tools for doing this vary from distribution to distribution. A good place to start searching is with the name of the package (e.g. "caps" or - "calf"). There are no fixed rules about what different Linux + "cmt"). There are no fixed rules about what different Linux distributions call their packages for a given set of plugins.
- If the package isn't available, then you can build the plugins from - source (plugins are generally fairly easy to compile if you've ever - done this sort of thing before). + If the package isn't available, then the plugins can be built from + source (plugins are generally fairly easy to compile and well-documented).
LADSPA plugins are shared library files. They need to be installed in either /usr/lib/ladspa, /usr/local/lib/ladspa or in a directory - mentioned in your LADSPA_PATH environment variable. + mentioned in the local LADSPA_PATH environment variable.
- LV2 plugins are folders/directories. They need to + LV2 plugins are folders/directories. They need to be installed in either /usr/lib/lv2, /usr/local/lib/lv2 or a directory - mentioned in your LV2_PATH environment variable. + mentioned in the local 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 + /usr/local/lib/lxvst or a directory mentioned in the local LXVST_PATH environment variable.
- Unless you're a particularly technical computer user, building and + Except for the particularly technical computer user, building and installing plugins in the LV2 (or LADSPA) format is probably not something worth planning on.
- Most of the plugins you are likely to use on OS X will be in Apple's + Most of the plugins likely to be used on OS X will be in Apple's AudioUnit format. These have their own installation process that tends to just work.
-