7 Jun
2003
7 Jun
'03
10 a.m.
Hello
A friend and I have made a VST plugin as a college project, and would
like to open source it, and possibly port it to other plugin APIs. We
are considering the GNU GPL for our licence, which has lead to this
question: Does VST count as a special exception of being "anything that
is normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies the
executable," or should we follow the suggestion about [1]controlled
interfaces in the GPL FAQ?
[1]
http://www.gnu.org/licenses/gpl-faq.html#TOCLinkingOverControlledInterface
--
Torgeir Strand Henriksen <torgshen(a)stud.iet.hist.no>
7 Jun
7 Jun
10:46 a.m.
What I do know about this, is that it is illegal from the VST SDK
license point of view to redistribute their headers with some GPL sources,
so the end user has to download the SDK with the headers included, to be able
to compile your plugin with VST support, if you license it GPL.
I don't think that is a showstopper, it is only a nuisance.
regards,
Vincent
PS: please consider creating a ladspa plugin from your sources:
http://www.ladspa.org/ , information about its API can be found
at http://www.linuxdj.com/audio/lad/resourcesapi.php3
There you can also find info about JACK, which is a great low latency
audio connection toolkit (that way you can test your plugin by linking
it to the audio stream of say a soft synth or some stuff you recorded).
On Sat, Jun 07, 2003 at 01:48:35PM +0200, Torgeir Strand Henriksen wrote:
Hello
A friend and I have made a VST plugin as a college project, and would
like to open source it, and possibly port it to other plugin APIs. We
are considering the GNU GPL for our licence, which has lead to this
question: Does VST count as a special exception of being "anything that
is normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies the
executable," or should we follow the suggestion about [1]controlled
interfaces in the GPL FAQ?
[1]
http://www.gnu.org/licenses/gpl-faq.html#TOCLinkingOverControlledInterface
--
Torgeir Strand Henriksen <torgshen(a)stud.iet.hist.no>
11:47 a.m.
lør, 07.06.2003 kl. 14.36 skrev Vincent Touquet:
What I do know about this, is that it is illegal from
the VST SDK
license point of view to redistribute their headers with some GPL sources,
Yes, we only intend to distribute our code, not the VST headers.
PS: please consider creating a ladspa plugin from your
sources:
http://www.ladspa.org/ , information about its API can be found
at http://www.linuxdj.com/audio/lad/resourcesapi.php3
Our plugin has a (still unfinished) GUI, and from the LADSPA page it
sounds like a standard GUI specification is something for the future.
The plugin is a complete virtual analog synthesizer with effects, and
has (in our opinion) too many parameters to be used without a custom
GUI. What is the status of such a specification?
There you can also find info about JACK, which is a
great low latency
audio connection toolkit (that way you can test your plugin by linking
it to the audio stream of say a soft synth or some stuff you recorded).
This could also be useful for making a standalone version, if that's
useful. I'll have a closer look at it.
--
Torgeir Strand Henriksen <torgshen(a)stud.iet.hist.no>
12:15 p.m.
On Sat, Jun 07, 2003 at 03:35:05 +0200, Torgeir Strand Henriksen wrote:
lør, 07.06.2003 kl. 14.36 skrev Vincent Touquet:
Theres nothing yet, I think a JACK appliation would be more relaisitic.
- Steve
What I do know about this, is that it is illegal
from the VST SDK
license point of view to redistribute their headers with some GPL sources,
Yes, we only intend to distribute our code, not the VST headers.
PS: please consider creating a ladspa plugin from
your sources:
http://www.ladspa.org/ , information about its API can be found
at http://www.linuxdj.com/audio/lad/resourcesapi.php3
Our plugin has a (still unfinished) GUI, and from the LADSPA page it
sounds like a standard GUI specification is something for the future.
The plugin is a complete virtual analog synthesizer with effects, and
has (in our opinion) too many parameters to be used without a custom
GUI. What is the status of such a specification? 
2:02 p.m.
Hallo,
Torgeir Strand Henriksen hat gesagt: // Torgeir Strand Henriksen wrote:
Our plugin has a (still unfinished) GUI, and from the
LADSPA page it
sounds like a standard GUI specification is something for the future.
The plugin is a complete virtual analog synthesizer with effects, and
has (in our opinion) too many parameters to be used without a custom
GUI.
I think, even so, LADSPA would make sense. I tend to build highly
customized GUI around LADSPA plugins in Pd, and with a LADSPA version,
I wouldn't be forced to use your GUI...
ciao
--
Frank Barknecht _ ______footils.org__
7778
days inactive
7778
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Frank Barknecht -
Steve Harris -
Torgeir Strand Henriksen -
Vincent Touquet