linuxaudio.org

--e89a8f22bc2905da3704d5214e6c

Content-Type: text/plain; charset=ISO-8859-1
On Thu, Feb 7, 2013 at 1:54 AM, Louis Gorenfeld

wrote:
> If I understand it correctly, you can compile free VSTs for Linux, you

quoted text
> just can't give away their SDK source code without going through the

> form on Steinberg's website (just like with the Mac and Windows

> versions). VSTSDK, the (fairly separate) component I had a problem

> with, is legitimately open-sourced and Linux-centric improvements can

> be made. I'm not seeing a problem here, unless there's something I'm

> overlooking (always very possible with me :))

>

true, except that
  * linux-centric improvements require someone to do the work. you may have

noticed that such people are

          in short supply.

  * there is a perception that many (even a majority?) of plugin developers

use synthedit or juce, making

          VSTGUI appear less and less relevant

  * VSTGUI's original X Window implementation was based on Motif which was

nobody ever really used

          on Linux. A later version (I think) switched to be directly based

on X Window itself, which is not

          a bad choice, but doesn't make life particularly easy for host

developers

  * plugin developers still have a tendency to want to do things in

windows-y ways, even though both VST

          and VSTGUI attempt to convince them not to (GUI threading rules

are one example).
--e89a8f22bc2905da3704d5214e6c

Content-Type: text/html; charset=ISO-8859-1

Content-Transfer-Encoding: quoted-printable
On Thu, Feb 7, 2013 at 1:54 AM, Louis Gorenfeld &=

lt;louis.gor=

enfeld@gmail.com> wrote:

If I understand it correctly, you can compil=

e free VSTs for Linux, you

just can't give away their SDK source code without going through the

form on Steinberg's website (just like with the Mac and Windows

versions). VSTSDK, the (fairly separate) component I had a problem

with, is legitimately open-sourced and Linux-centric improvements can

be made. I'm not seeing a problem here, unless there's something I&=

#39;m

overlooking (always very possible with me :))

true, except=

 that =A0 * linux-centric improvements require someone to do the wo=

rk. you may have noticed that such people are=A0=A0=A0=A0=A0=

=A0=A0=A0=A0 in short supply.

=A0 * there is a perception that many (even a majority?) of plug=

in developers use synthedit or juce, making=A0=A0=A0=A0=A0=

=A0=A0=A0=A0 VSTGUI appear less and less relevant=A0 * VSTGU=

I's original X Window implementation was based on Motif which was nobod=

y ever really used

=A0=A0=A0=A0=A0=A0=A0=A0=A0 on Linux. A later version (I think) =

switched to be directly based on X Window itself, which is not=A0=A0=A0=A0=A0=A0=A0=A0=A0 a bad choice, but doesn't make life parti=

cularly easy for host developers

=A0 * plugin developers still have a tendency to want to do thin=

gs in windows-y ways, even though both VST=A0=A0=A0=A0=A0=A0=

=A0=A0=A0 and VSTGUI attempt to convince them not to (GUI threading rules a=

re one example). 
--e89a8f22bc2905da3704d5214e6c--