howdy, about plugin hosts for vst to load them in your patches...
what are the challenges, issues and is there a reason why anyone hasn't done this for all OS yet?
cheers
btw, audiounits are only for mac os, but vst is for linux, windows and mac, right?
2016-06-12 23:48 GMT-03:00 Alexandre Torres Porres porres@gmail.com:
On Mon, Jun 13, 2016 at 6:02 PM, patrice colet colet.patrice@free.fr wrote:
vst is certainly not for linux, never ever
not sure if you're making a political point or not, but:
On Mon, 2016-06-13 at 11:02 +0200, patrice colet wrote:
vst is certainly not for linux, never ever
???
http://linux-sound.org/linux-vst-plugins.html
Roman
On 13/06/2016 12:28, patrice colet wrote:
I guess this paragraph from the Wikipedia article sums it up quite well:
"VST plugin standard" - https://en.wikipedia.org/wiki/Virtual_Studio_Technology#VST_plugin_standard
Also. On Linux, because of Jack, having a plug-in client (whichever format) directly in Pd maybe is a bit less relevant? (Although there could be interesting use cases, e.g. if the plug-in parameters were exposed and directly inter-actable from within the patch...)
Lorenzo.
Hi, it's not a principal problem, just a matter of implementing it. Here's my stone-old approach to it which is certainly far from being up-to-date. It has worked for a considerable time though. https://svn.grrrr.org/ext/trunk/vst/
The Mac part is not fully implemented. In the meantime, this part may have become more difficult because the APIs might be objective C only. I guess the linux part is pretty much depending on wine.
best, Thomas
-- Thomas Grill http://grrrr.org
2016-06-13 19:11 GMT-03:00 Simon Iten itensimon@gmail.com:
i think the point would be to have native linux vst support, right? (not saying that you should do that)
well, this is why i was asking, i need more info as I'm not a linux user. How "native" is vst for linux? Seems like it is "full native" to me... mostly because of this link http://linux-sound.org/linux-vst-plugins.html
and how it says compiled for native Linux. No WINE required
the situation is as follows:
linux vst is native on linux of course, but that does not mean that windows or osx vst’s will run on linux. you have to compile them for linux. there are some commercial plugins popping up for linux, and they are often linuxvst. opensource plugins are still mostly lv2 or still ladspa.
so, someone was telling me about an alleged issue, as follows:
"with a GUI that depends in GUI libraries as Qt, GTK or JUCE, there's no garanties I'll have these libraries so it may be impossible for PD to open such libraries (...) QTractor, for instance, runs well plugins based in Qt but is terrible with plugins whose GUI is based in GTK."
anyway, according to this, it'd be impossible, but I dont think so, although i have no idea what hes talking about, how about you people?
cheers
2016-06-14 6:59 GMT-03:00 Simon Iten itensimon@gmail.com:
2016-06-13 18:27 GMT-03:00 Thomas Grill gr@grrrr.org:
Hi, it's not a principal problem, just a matter of implementing it.
so relevant specific issues, besides actually doing it, huh? Cool, that was my main question...
Here's my stone-old approach to it which is certainly far from being
up-to-date. It has worked for a considerable time though. https://svn.grrrr.org/ext/trunk/vst/
interesting, never knew about this.
this looks interesting by the way...
https://github.com/falkTX/Carla
wondering how crazy would be to drink from this source and make pd externals...
cheers
2016-06-14 0:40 GMT-03:00 Alexandre Torres Porres porres@gmail.com:
I meant: *so NO relevant specific issues*