On 10/16/05, Dave Phillips <dlphillips@xxxxxxxxxx> wrote: > Mark Knecht wrote: > > >>I'd like to see every Linux Audio user interested in this subject > >>start pressing the Wine folks to support this themselves. Let's pay > >>attention to the Windows apps that can host VSTs and VSTi's. Acid Pro > >>is a commercial one that comes to mind. Fruity Loops, etc. There's got > >>to be free VST loaders out there for Windows. Older versions of Acid > >>install and run fine under Wine but do not handle VSTs very well. The > >>new versions don't install or run. > >> > >>Putting together yet another hack outside of Wine that will run for 1 > >>year and then die when gcc5 comes out would be disappointing. Let's > >>get the Wine folks to support this. > >> > >>Please enter apps in the Wine AppDB and enter test results in Wine's > >>Bugzilla. If there are enough of us entering 100's of apps then > >>they'll pay attention. Maybe not fast, but I believe they will. > >> > >> > Hear the man. This issue is really as much a matter for the WINE folk as > it is for us. VSTs are Windows applications, WINE intends to run Windows > applications. Thanks Dave. I haven't heard a consensus yet, but there seems to be interst in the savihost.exe application for a simple host that can hold both VSTs and VSTi's. I tried installing savihost.exe but it failed for a missing DLL. I've rectified that and am learning to run Savihost. It's a bit strange to be renaming the thng all the time, but so be it. We'll see. I haven't tried to get sound yet from it. (Other competing priorities...) > > Torben Hohn wrote: > > >i still believe, that the current xfst approach is a clean solution. > >it does no more use the libwinelib hack. > >its a wine app which uses jack natively. > > > > > An interesting approach. > > I downloaded the 0.3 package and built it under Planet CCRMA's RH9, WINE > 20050725. What I had to do: > > 1) Fixed aeffectx.h by commenting out lines 918 through 932 and > added "struct" to the beginning of line 949 to read "struct VstFileType". > 2) Linked /lib/libuuid.so.1 to /lib/libuuid.so. > > It built without problems. There is no 'make install', so I ran xfst > from its own directory. > > The first time I ran it my X server crashed, probaby due to memory and > CPU shortcomings of my PII 366 laptop. I restarted X and ran './xfst > ../vstplugins/Crystal.dll'. The plugin GUI appears and its various > controls seem to work all right. I connected a virtual keyboard to it, > played a note, and JACK zombifies the plugin. > > I've only tried running the Crystal plugin, so this test doesn't mean > much. I'll try upgrading WINE to see if that matters. I tried this route back in February but didn't get very far with it. My email notes don't say what version I was using at that time. Possibly this is newer? Not sure as I've heard nothing from Torben since that time until this week's emails on the subject. Before I'd go to far down that path I'd like to understand if anyone would support it over the long term. (That's just a personal view of mine...) Cheers, Mark
