Re: Re: [Lmuse-developer] VST and dssi support

[<cco...@ch...>]

> 
> From: Robert Jonsson <rj...@sp...>
> Date: 2005/02/01 Tue PM 09:16:50 GMT
> To: lmu...@li...
> CC: cco...@ch...
> Subject: Re: [Lmuse-developer] VST and dssi support
> 
> 
...
> Though, as I understood it, the dssi-vst plug had a specific license, please 
> make sure that all requirements are met.
> 
> Regards,
> Robert
> 
> 
> 
> 
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
> 
> -- 
> http://spamatica.se/music/
> 
> 


Here is what it says in the dssi-vst README:

"You may distribute and/or modify dssi-vst under the terms of version 2
of the GNU General Public License as published by the Free Software
Foundation, except that you are hereby permitted to omit the source
code to the two VST SDK header files AEffect.h and aeffectx.h (the
source code of which would otherwise be required by section 3 of the
GPL) when redistributing dssi-vst.  The full terms of the GPL continue
to apply to all of the remaining source code for dssi-vst.

So basically my plugin couldn't be included with muse because section 3 says you need to include all the code necessary to build the program and the steinberg VST SDK headers cannot be. 

It seems to me it must be workable, otherwise muse is violating the GPL also since it uses fst.h
in muse/driver/jack.cpp and muse/vst.cpp

fst.h contains

#include <vst/AEffect.h> 

which is not GPLed

An idea:

Distribute my plugin so that it builds in a manner that does not use dssi-vst by default. And provide additional licensing terms in its subdirectory that must be agreed to before building with VST support. The dssi-vst source would not be included with muse and could only be used unless the user agrees with the additional terms.. It would also be noted in those terms that building in this manner conflicts with Muse's licensing as noted above.

Hopefully there is a solution, otherwise I may be the only one who benefits.