blob: 8bff5a2b27845efc9ddaf7ad18189eb95dba3456 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
<?xml version="1.0" standalone="no"?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<section id="sn-vst-plugins">
<title>Using VST Plugins</title>
<section id="vst-why-so-hard">
<title>Why is this harder than it should be?</title>
<para>
The owners of VST (Steinberg Technologies, now owned by Yamaha) give VST
away to developers for free. Sounds great, but they do not those same
developers the ability to pass what they get from Steinberg on to other
developers.
</para>
<para>
This conflicts with the terms of the license for Ardour and several
software libraries used by Ardour. Steinberg have said quite often that
they are not opposed in principle to changing their license to allow
redistribution, but as of mid-summer 2006, it has not happened yet.
</para>
<para>
All of this means that it is <emphasis>illegal</emphasis> for anyone to
distribute a binary (ready-to-run) version of Ardour with support for VST
plugins built in. If you want to use Ardour with VST plugins, you must
<emphasis>compile it yourself</emphasis>.
</para>
<para>
This is not a trivial undertaking; see our
<emphasis>build page</emphasis>
for a full explanation even without VST support. This page documents some
more required steps for the build if you want to include VST support.
</para>
</section>
<section id="building-ardour-with-vst-support">
<title>Getting a version of Ardour with VST support</title>
<para>
... to be completed.
</para>
</section>
<!--
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="Some_Subsection.xml" />
-->
</section>
|
