8 Feb
2013
8 Feb
'13
4:15 a.m.
On Thu, 7 Feb 2013 08:58:12 -0500
jordan <triplesquarednine(a)gmail.com> wrote:
Hey,
AFAIK, Vestige only works for the host side. For building plugins
you still need the VST SDK. At least that's what I thought.
Has that changed?
It is not a technical point about only using free
software ... it is a very real copyright issue. VST is owned by Steinberg so unless you
are willing to ignore/reject Copyright and IP laws
(which would be really problematic regarding your other points about encouraging
commercial software on Linux) then you are very limited in how VST can be distributed in
Linux. To
change that you must convince Steinberg to change the license they offer. A freely
distributed program obviously cannot pay Steinberg for every downloaded copy .. so no
license .. so the
potential user must compile their own version of VST support.
Vestige provides a replacement for Stienberg's VSTSDK, it's been
widely used for some time now, by several projects (FST, FSTHost,
LMMS, Ardour, etc, etc)... I use both Windows and Linux VSTs all of
the time, I don't feel restricted by Steinberg. It's pretty simple, do
not rely on their header, use Vestige and their is no problem. The
last time i was required to get the VSTSDK from Steinberg was quite
some time ago, like 2007-8 and that was to compile/use one specific
application / corner case. The only time i (still) have actually need
some headers from Steinberg is for WineASIO support (asio.h), which i
barely use. You are only limited in how/what can be distributed if you
plan on using the VSTSDK - which would mean you are in the position of
WineASIO / ASIO SDK - the end-user must get the header (asio.h) and
compile WineASIO him/herself. (but even that doesn't bother me, since
it takes all of 3 minutes to do).