[LAU] Fwd: [PlanetCCRMA] VST

[Joseph Dell'Orfano]

I forwarded my post from the ccrma list. I am looking for help getting  
windows vst support on a 64 bit system. The typical solutions (fst,  
dssi-vst) don't compile, nor does wineasio.

Any help would be appreciated!

Joe


Begin forwarded message:

> From: "Joseph Dell'Orfano" <fullgo at dellorfano.net>
> Date: November 5, 2008 11:25:02 PM EST
> To: "Preston C." <gprestonc at gmail.com>, planetccrma at ccrma.Stanford.EDU
> Cc: linux-audio-user-bounces at lists.linuxaudio.org
> Subject: Re: [PlanetCCRMA] VST
>

> Thank you so much for your reply. I have explored all of these  
> options and actually just got my Amplitube plugin working on my old  
> 32-bit machine. This is using CCRMA with FC6.  This works for me  
> because I have this connected via S/PDIF to my main DAW (a 64-bit  
> machine running CCRMA and FC8), so essentially my old 32-bit machine  
> is functioning as a digital effects processor.
>
> Here is the summary of my experience with VST so far. I have cross  
> posted this on LAU as well.
>
> 1. I cannot run a (windows) VST on my 64-bit machine. I cannot  
> compile dssi-vst, fst, or wine-asio. It appears that they do not  
> want to compile against my 64-bit jack libraries. Perhaps I am  
> missing something obvious (probably) but I just can't compile these.
>
> 2. Reaper does not work in Wine on my 64-bit machine. I installed  
> wine from the CCRMA repo (it is 32-bit I believe).
>
> 3. Energy-XT runs but I cannot compile the libamm with jack support.  
> Again, 64-bit problems. I have not tried to run the windows version  
> of energy-XT but I suspect I will have wine problems as I did with  
> reaper.
>
> 4. dssi-vst appears to be broken on the 32-bit machine. Again, I  
> downloaded this from CCRMA repo. vsthost scans all of my plugins  
> properly and starts them up but quickly fails with a report that it  
> "lost communication" with the plugin.
>
> 5. fst compiles on my 32-bit machine very easily and runs my windows  
> plugins properly (Yay!)
>
> I hope this is helpful. Any comments about getting VST support up  
> and running on my 64-bit machine would be greatly appreciated.
>
> -Joe
>
> Preston C. wrote:
>>
>> On Mon, Nov 3, 2008 at 12:43 AM, Joseph Dell'Orfano
>> <fullgo at dellorfano.net> wrote:
>>
>>> Hi everybody,
>>>
>>> I am trying to find a solution to vst support on a ccrma fedora 8
>>> system. Oh, did I mention I'm running 64-bit? That seems to be a  
>>> major
>>> wall preventing dssi-vst and others from compiling. I can compile  
>>> wine-
>>> asio-x and jackbridge seems work fine. I cannot get Reaper to run,  
>>> nor
>>> can I get extreme-xt to run with jack support (cannot compile  
>>> libamm).
>>> I am using the stock wine packages from ccrma which do not appear to
>>> be 64-bit so this may prevent programs such as reaper from working.
>>>
>>> So, any suggestions would be appreciated. There do not seem to be a
>>> lot of success stories out there.
>>>
>>> Thanks!
>>>
>>> Joe Dell'Orfano
>>>
>>> _______________________________________________
>>> PlanetCCRMA mailing list
>>> PlanetCCRMA at ccrma.stanford.edu
>>> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>>>
>>>
>> I asked the same question on this list, and got a great reply from a
>> guy named Ray Rashif. Here it is:
>>
>> OK, the deal about VST "support" on GNU/Linux is that you can read  
>> all
>> about it scattered all around the WWW. It'd take some time to really
>> get things right if you don't come across the correct sources sooner
>> than expected. The SDK is freely available, but not free is in our
>> understanding; the license forbids redistribution. So, say you were  
>> to
>> use the SDK to program a host, you're not allowed to let the binary  
>> be
>> up for download. Each individual must agree to the licensing terms  
>> and
>> then download the SDK to compile the software himself. This is what
>> limits the so-called support for VSTs on Linux, or any free platform.
>>
>> In view of the situation, there are currently a few ways to use
>> VST(i)s on our favourite distros:
>>
>> (1) Proprietary DAW software with Linux offerings. Examples are
>> Renoise, energyXT..and I think that's about it.
>>
>> (2) Wine-friendly Windows software. Examples are..example is Reaper.
>>
>> (3) SDK-compiled Linux software that support it. Examples are Ardour,
>> Rosegarden, and I can't really remember the rest. Here you need to
>> download the SDK and configure the build to compile against the SDK.
>>
>> (4) Linux software with unique support for VSTs built in, with the
>> help of Wine. Note: No SDK required. This is my personal favourite
>> route to take. Examples are LMMS and Qtractor (via dssi-vst).
>> ---- Extra note: Qtractor is different because it relies on a  
>> separate
>> wrapper, which in turn has that unique Wine-based support built in:
>> dssi-vst
>> ---- Previously dssi-vst required the SDK, but not anymore. Yay.
>>
>> (5) Native VST host. Native here means Linux-only. These VSTs are
>> those that are compiled for the Linux system. There is only 1 such
>> host to my knowledge - Jost. The collection of plug-ins (ported or
>> otherwise) isn't all that great, but it feels really good being able
>> to run VST instruments natively without any overhead or performance
>> loss. The author's few plug-ins are of high quality; a talented
>> programmer AND musician he is.
>>
>
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20081105/4d9028f4/attachment.htm