a real path.
</p>
<p>
- An example of a configuration path in Window (from XP) would be:
- <code>C:\Documents and Settings\<User>\Application Data\Local Settings\Ardour5\</code>
+ An example of a configuration path in Window 10 would be:
+ <code>C:\<User>\AppData\Local\Ardour5\</code>
The user in the path would be the user's account name.
</p>
<p class="note">
The above is only an example and may not even be true for all installations
- of Windows XP.
+ of Windows 10.
</p>
<h2>Plugins</h2>
<h4>LV2</h4>
<p>
- LADSPA plugins should be found in <code>/usr/lib/lv2/</code>,
+ LV2 plugins should be found in <code>/usr/lib/lv2/</code>,
<code>/usr/local/lib/lv2/</code>
or in a directory mentioned in your LV2_PATH environment variable.
The most common mistake made by distro packagers, is to use a path
- like <code>/usr/lib/$ARCH/lv2/</code> and find that Ardour will not find that by
- default. The user can either add a link from this actual directory to
- the standard directory or add this path to LV2_PATH.
+ like <code>/usr/lib/$ARCH/lv2/</code>, <code>/usr/lib64/lv2</code>
+ or <code>/usr/local/lib64/lv2</code> and find that Ardour will not find
+ that by default. The user can either add a link from this actual directory
+ to the standard directory or add this path to LV2_PATH.
</p>
<h4>Linux VST or lxvst</h4>
<h4>LV2</h4>
<p>
The LV2 standard for Windows is <code>%APPDATA%/LV2/</code> or
- <code>%COMMONPROGRAMFILES%/LV2/</code>
+ <code>%COMMONPROGRAMFILES%/LV2/</code> (On Windows 10: <code>C:\<User>\AppData\Roaming\LV2\</code> or <code>C:\Program Files\Common Files\LV2\</code>).
</p>
<h2>Project Directory</h2>