Re: VSTPlugin on Linux

[email protected] Thu, 1 Apr 2021 02:45:09 +0200
Newsgroups gmane.comp.audio.supercollider.user
Message-ID <[email protected]>
> So, it is indeed possible to have (maybe not all) native Win VST3
> working on Linux in SC with VSTPlugin host with yabridge
Cool!

In the meantime, I've been experimenting a bit with Wine and the next
VSTPlugin version will probably have native Wine support, meaning you
will be able to run Windows VSTs on Linux without any third-party tools :-)

> (now aeffectx.h is called audioeffectx.h or smthg). I might have
> downloaded the wrong SDK for VST2 ...
'audioeffectx.h' is in the 'public.sdk' folder. You need the header
files in 'pluginterfaces' folder. The folder structure shoudl look like
this:

VST2_SDK -> pluginterfaces -> vst2.x -> "aeffect.h", "aeffectx.h"

Christof

On 31.03.2021 21:47, [email protected] wrote:
> Hi Christof,
>
> Thanks for your help and I wanted to let you know that I finally got
> it working.
> So, it is indeed possible to have (maybe not all) native Win VST3
> working on Linux in SC with VSTPlugin host with yabridge as the bridge
> between Wine and the VSTs (phew).
> I even got it working in non-RT (thanks to another of your post here:
> https://git.iem.at/pd/vstplugin/-/issues/20
> <https://git.iem.at/pd/vstplugin/-/issues/20>) on an EC2 instance
> inside a docker, just to spice it up a bit.
> I am so glad it works and wanted to warmly thank you.
>
> One bit that is still missing is the VST2 support. I compiled it with
> the VST2 option OFF, since it was causing a discrepancy with the
> Steinberg VST_SDK include files
> (now aeffectx.h is called audioeffectx.h or smthg). I might have
> downloaded the wrong SDK for VST2 ...
>
> Cheers,
>
> @.
>
>
> Le lun. 29 mars 2021 à 10:33, <[email protected]
> <mailto:[email protected]>> a écrit :
>
>     > Using this approach you do not have to run the vst plugins
>     inside sc.
>     @eric: But you lose all the benefits ;-)
>
>     > I thus wonder if there is a way to use yabridge + vstplugin with
>     SC ...
>     @artheist: I don't see why it shouldn't. From looking at the GitHub
>     page, I understand that it just creates wrapper .so files and
>     VSTPlugin
>     should be able to load them. For VST2 plugins you'd have to pass the
>     correct directory to VSTPlugin.search (see the 'dir' argument).
>     The VST3
>     plugins should be in a standard location, so a plain VSTPlugin.search
>     should do. I think it's all explained here:
>     https://github.com/robbert-vdh/yabridge
>     <https://github.com/robbert-vdh/yabridge>
>
>     Christof
>
>     On 29.03.2021 16:20, [email protected]
>     <mailto:[email protected]> wrote:
>     > Hi,
>     >
>     > If you are on a linux platform, don't forget that you can use jack :
>     > why not running an independent vst hosting application and route
>     input from
>     > and to sc via jack ?
>     >
>     > You just have to adapt the numOutputBusChannels variable or the sc
>     > server to have any number out output busses routable with jack,
>     and the
>     > same applies for numInputBusChannels.
>     >
>     > Using this approach you do not have to run the vst plugins
>     inside sc.
>     >
>     > Regards.
>     >
>     > Eric
>     > Le lun. 29 mars 2021 à 16:08, [email protected]
>     <mailto:[email protected]> a écrit :
>     >
>     >> Hi Christof,
>     >>
>     >> Thanks for the quick response, that is what I indeed feared.
>     >> I have been able to run VSTs on Linux with yabridge, which in
>     my understanding is performing better than LinSVT.
>     >>
>     >> I thus wonder if there is a way to use yabridge + vstplugin
>     with SC ...
>     >> Will keep you posted if I achieve to get something working this
>     way.
>     >>
>     >> Best,
>     >>
>     >> @.
>     >>
>     >> Le lun. 29 mars 2021 à 09:50, <[email protected]
>     <mailto:[email protected]>> a écrit :
>     >>
>     >>   Hi,
>     >>
>     >>   VSTPlugin itself can only open plugins compiled for the same
>     platform.
>     >>   Since you've mentioned Wine, I assume you're trying to run
>     Windows DLLs?
>     >>   If yes, you can use LinVst (https://github.com/osxmidi/LinVst
>     <https://github.com/osxmidi/LinVst>) which
>     >>   allows to run Windows VST plugins in a Linux host.
>     >>
>     >>   ---
>     >>
>     >>   Actually, VSTPlugin already supports bit bridging (= running
>     a 32-bit
>     >>   plugin in a 64-bit host and vice versa). This is done by
>     running the
>     >>   plugins in a dedicated process which communicates with the
>     host via a
>     >>   shared memory interface. I guess the same technique could be
>     used to run
>     >>   Windows VST plugins on Linux Pd/Supercollider. I'll put this
>     on my list.
>     >>
>     >>   Christof
>     >>
>     >>   On 29.03.2021 15:06, [email protected]
>     <mailto:[email protected]> wrote:
>     >>   > Hi,
>     >>   >
>     >>   > I have been fiddling a bit with VSTPlugin which is a great
>     addition to SC.
>     >>   > So far, I have been able to use it correctly on Mac OSX,
>     but I have
>     >>   > trouble getting it to work on Linux.I guess the issue is mostly
>     >>   > related to Wine, or there is something I did not quite
>     understand.
>     >>   >
>     >>   > I have been able to install vstplugin~ correctly either
>     with the
>     >>   > supercollider-vstplugin AUR package as well as compiled
>     from the
>     >>   > github latest version.
>     >>   >
>     >>   > Compile class library works fine and I am able to
>     instantiate both
>     >>   > VSTPlugin SynthDef and VSTPluginController.
>     >>   >
>     >>   > However, when I am trying to open from the vst path for a vst
>     >>   > installed through wine, it results in an empty vst ...
>     >>   >
>     >>   > I am sure there is something obvious or sutpid on my part, any
>     >>   > pointers would be appreciated.
>     >>   >
>     >>   > Best,
>     >>   >
>     >>   > @.
>     >>
>     >>   _______________________________________________
>     >>   sc-users mailing list
>     >>
>     >>   info (subscription, etc.):
>     http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>     <http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx>
>     >>   archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
>     <http://www.listarc.bham.ac.uk/marchives/sc-users/>
>     >>   search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>     <http://www.listarc.bham.ac.uk/lists/sc-users/search/>
>     >
>
>     _______________________________________________
>     sc-users mailing list
>
>     info (subscription, etc.):
>     http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>     <http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx>
>     archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
>     <http://www.listarc.bham.ac.uk/marchives/sc-users/>
>     search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>     <http://www.listarc.bham.ac.uk/lists/sc-users/search/>
>