2 <h2>Configuration Directory</h2>
4 Ardour stores configuration files in two places. The system configuration
5 directory and the user configuration directory. The system configuration
6 directory is used for stock configuration files at install time.
7 The user configuration directory is used by Ardour to store
8 configuration changes made in the GUI as well as being a place the user
9 can add control surface device files, scripts etc.
13 Ardour tries to use standard places for these directories for the platform
18 The user configuration directory will be somewhere inside the user's
19 home directory. The home directory on a linux system is normally
20 <code>/home/$USER/</code>, but should also be returned by <code>$HOME</code>
22 A normal place to find this is <code>$HOME/.config/ardour*/</code> where
23 <code>*</code> is the major version. However this can be set by the system with the
24 <code>$XDG_CONFIG_HOME</code> environment variable to something else. If you cannot
25 find <code>$HOME/.config/</code> on your system try <code>echo ${XDG_CONFIG_HOME}</code>
26 to see if your distro is using something else. In any case Ardour
27 appends the <code>ardour*</code>
28 directory to the result where <code>*</code> is the major version number.
29 For example, <code>ardour5</code> where the Ardour version is 5.6.
32 In Linux, all path names are lower case and case matters.
38 The user configuration directory on macOS is
39 <code>$HOME/Library/Preferences/Ardour*/</code> where <code>*</code>
40 is the major version number.
41 For example, <code>Ardour5</code> where the Ardour version is 5.6.
45 Windows users are not expected to hand edit configuration files at all.
46 It is expected configuration options are changed with some sort of GUI
47 tool. For the most part all of Ardour's configuration is taken care of
48 by the GUI in preferences. However, there are devices that may need a
49 custom file and that would be in the users configuration directory.
52 Ardour asks the system for this directory and then appends
54 to the path where <code>*</code> is the major version number.
55 For example, <code>Ardour5</code> where the Ardour version is 5.6.
56 The official path would look like:
57 <code>%localappdata%\Ardour5\</code> Windows expands
58 <code>%localappdata%</code> to
62 An example of a configuration path in Window (from xp) would be:
63 <code>C:\Documents and Settings\<User>\Application Data\Local Settings\Ardour5\</code>
64 The user in the path would be the user's account name.
67 The above is only an example and may not even be true for all installations
73 Plugins will be installed in various places, some by standard and some
74 by developer whim. Some are installed incorrectly by distro policy.
79 In linux there are 3 kinds of plugins Ardour can use. LADSPA, LV2 (LADSPA version 2)
80 or lxvst (VSTs compiled as native linux binaries). While it is possible
81 with some strange magic to run <a href="/working-with-plugins/windows-vst-support/">Windows VSTs</a>
82 on linux, their whereabouts would follow the Windows info below.
87 LADSPA plugins should be found in <code>/usr/lib/ladspa/</code>,
88 <code>/usr/local/lib/ladspa/</code>
89 or in a directory mentioned in your LADSPA_PATH environment variable.
90 The most common mistake made by distro packagers, is to use a path
91 like <code>/usr/lib/$ARCH/ladspa/</code> and find that Ardour will not find that by
92 default. The user can either add a link from this actual directory to
93 the standard directory or add this path to LADSPA_PATH.
98 LADSPA plugins should be found in <code>/usr/lib/lv2/</code>,
99 <code>/usr/local/lib/lv2/</code>
100 or in a directory mentioned in your LV2_PATH environment variable.
101 The most common mistake made by distro packagers, is to use a path
102 like <code>/usr/lib/$ARCH/lv2/</code> and find that Ardour will not find that by
103 default. The user can either add a link from this actual directory to
104 the standard directory or add this path to LV2_PATH.
107 <h4>Linux VST or lxvst</h4>
109 They are typically installed in <code>/usr/lib/lxvst</code>,
110 <code>/usr/local/lib/lxvst</code> or
111 a directory mentioned in your LXVST_PATH environment variable. However,
112 this is not a standard and the VST plugin developer may install the plugin
113 just about anywhere. Therefore Ardour allows the user to set extra VST
114 paths in the preferences GUI under Plugins>VST.
119 On the Mac, plugins are expected to be installed correctly Ardour uses
120 the system tool to scan for AU style plugins and LV2s should be in the right
121 place. LV2 should be in <code>$HOME/Library/Audio/Plug-Ins/LV2/</code>
122 <code>/Library/Audio/Plug-Ins/LV2/</code>
123 <code>/usr/local/lib/lv2/</code>
124 <code>/usr/lib/lv2/</code>
125 If an AU or LV2 plugin does not show up on a Mac it is probably
126 a development fault with the plugin and the plugin will not work with anything.
127 Ardour in Ardour 5.6 has support for native VST plugins. That is VST
128 plugins built for OSX. I am not sure if these have a standard place to
129 be, but as with other VSTs the search path can be edited at Plugins>VST.
134 The most common plugins on Windows are VSTs. However, LADSPA and LV2
135 plugins are available for windows as well. In fact Ardours built in
136 plugins are LV2s. The biggest advanatage of LV2 plugins is that they are
137 the most likely to be cross platform and therefore allow the same Ardour
138 project to be worked on in Windows, OSX and Linux.
143 As with other platforms, VSTs on Windows do not have a standard place
144 to reside. Ardour Preferences>Plugins>VST allows setting the VST path
149 The LV2 standard for Windows is <code>%APPDATA%/LV2/</code> or
150 <code>%COMMONPROGRAMFILES%/LV2/</code>
153 <h2>Project Directory</h2>
155 Ardour places a project directory where the user tells it to. This
156 directory is chosen when creating a project. In most cases the user
157 does not need to know about the files inside of the project directory.
158 However there are a few subdirectories worth noting.
162 This is the subdirectory where exported files end up.
projects / ardour-manual / blob