On 11/16/06, Dmitry Baikov <dsbaikov(a)gmail.com> wrote: So you're going to purchase a license? I bought a license for a Linux music app once, the Ultramasters RS-101 (I think that was the name). It was an awesome program, but it disappeared off the face of the earth, and I couldn't get it to run on anything newer than the Red Hat 7.2 system I initially installed it on. Apparently energyXT will only use native Linux VSTs. Nobody writes native Linux VSTs (although the energyXT author says he has compiiled some). I'm not trying to be negative here, but I don't really see the point in a native energyXT.

On Thu Nov 16, 2006 at 11:42:22AM +0300, Dmitry Baikov wrote: does it really offer much beyond seq24/dino/hydrogen/gneutronica in this department? can it do stuff like recursively trigger patterns from other patterns in realtime? if it can, is it flexible in the representation? ive downloaded the windows version before , and all i could figure out was it was sort of an om-synth that used VST instead of LADSPA, plus a piano roll.. in other words, if im paying $45, id like the source with it thanks :)

On Thu, Nov 16, 2006 at 05:27:54PM -0500, Ivica Ico Bukvic wrote: What does that mean, a VST compiled for Linux ? Will it work without a Windoze emulator ? -- FA Lascia la spina, cogli la rosa.

Erm, I meant "his interview," not "his e-mail"... Whoever invented "multitasking" should be beaten up with an ATX case... Ico

On Fri, 2006-11-17 at 08:48 +0100, rj(a)spamatica.se wrote: what are you talking about? almost every VST plugin has a GUI written using a GUI toolkit that is not available for linux. so sure, "no inherent problem" but that actually means "no inherent problem but in practice its so much work that nobody does it".

On Fri, Nov 17, 2006 at 08:19:58AM -0500, Paul Davis wrote: Are you talking about the Windows native GUI toolkit? I beleive it's possible to use the WineLib part of Wine to recompile Windows apps (and presumably dlls like VSTs) to run natively on Linux using the WineLib API calls instead of the Windows calls. This is not the same as emulating a Windows program under Linux using Wine. The final product is a Linux binary that only runs under Linux. Hopefully if people did this they would open source their VSTs to keep with the spirit of GNU/Linux. Best, Chris. ------------------- chris(a)mccormick.cx http://mccormick.cx

On Sat, 2006-11-18 at 11:55 +0800, Chris McCormick wrote: there is no WineLib API. anybody who says otherwise is lying. how do i know this? because when torben and i took kjetil's initial work on running VSTs on linux and tried to do the in-process system we went down this route (using wine as a library) we even wrote some patches for the wine people, in collaboration with the Mono project. we were rebuffed, 100% and completely, because the benevolent dictator of Wine was adamant that Wine is not and will never be a library despite the recurrence of "WineLib" as a term. they have no interest (at this time) in defining an interface to Wine support via a library. no its not. if you check what actually happens under the hood when you do this, you will find that you actually get 2 products: a shared object representing the original windows program and a shell script that uses Wine to execute the shared object. how do i know all this? because we use this in ardour2 (and the current version of FST) to provide the most robust VST support that we can. how does it work? we compile the code that normally makes up the executable for ardour as a shared library, with an special entry point called ardour_main(). then we compile a tiny win32 app that does nothing but start up and call ardour_main(). this is compiled using winegcc. the result is a shell script and a small win32 shared object/.exe file. you run the shell script, it starts wine, which runs the tiny win32 app, which is linked against libardourgtk and calls ardour_main(), and voila ... ardour running inside wine with the best VST support that wine can offer. note that you can substitute cedega for wine and it works slightly better ;) baroque? yep. but this how it actually works ... --p

On Sat, 2006-11-18 at 11:35 -0500, Ivica Ico Bukvic wrote: as i have mentioned, VSTGUI does come with a Motif backend but i very very much doubt that it has been kept current as VSTGUI has evolved. VSTGUI is LGPL'ed and on sourceforge. that is, of course, very very different from "having functional support on a large number of platforms including Linux or X Window" nothing more is needed than programmers with time and motivation. but this is also missing a deeper issue. a lot of plugins do not use VSTGUI, a lot of plugins make calls to win32 function that are not necessarily GUI related. thus, even if you had VSTGUI support for X Window, it wouldn't necessarily be trivial to port a given plugin to linux. --p