KVR Audio

arakula · Post by **arakula** » Tue Jul 28, 2009 9:48 am

koalaboy wrote:Is the main reason that Wine is required, due to the GUIs ? I'm assuming (probably very stupidly) that the audio API should be pretty much cross-platform ?

The problem starts at a much deeper level... the executable file format used by Windows differs from the one used by Mac OSX (and Linux). Wine is necessary to load the Windows DLLs; and these as sure as hell contain quite a lot of references to other Windows DLLs, which are provided by Wine. Even without any graphics operations.

SWAN808 · Post by **SWAN808** » Tue Jul 28, 2009 10:15 am

I have a Crossover installation - would anybody mind advising me on how the wacvst installation differes from the previous page when using Crossover over Wine?

Bryan J · Post by **Bryan J** » Tue Jul 28, 2009 4:21 pm

SWAN808 wrote:I have a Crossover installation - would anybody mind advising me on how the wacvst installation differs from the previous page when using Crossover over Wine?

In this case, you would probably just need to know the path to Wine used by Crossover for wacvst when you're editing the config.plist file.

Bryan J · Post by **Bryan J** » Tue Jul 28, 2009 4:38 pm

mustgroove wrote:Also, Bryan J - is there any particular reason why downloading Xcode from ADC is required, or will the copy that comes on the OS X install disc suffice?

There are several versions out there of Wine, XQuartz, and Xcode. I made an effort to document a procedure that would get people up and running with what I know was working on my system in order to avoid questioning to many variables afterward. With that said, versions from other sources may or may not work just fine. If so, let us know. It would certainly be ideal to shorten the install procedure as much as possible.

goonzy · Post by **goonzy** » Tue Jul 28, 2009 5:20 pm

One of teh best news of this month for me.. GREAT JOB...

I'll have a try with the VSTi I want to use on my mac (which is not fully standard as it's a controller for a hardware synth. Bought it as the dev promised an OSX version and itnever occured...

I'll try it tonight when I'm home :p

retroware · Post by **retroware** » Tue Jul 28, 2009 10:41 pm

Bryan J wrote:
SWAN808 wrote:I have a Crossover installation - would anybody mind advising me on how the wacvst installation differs from the previous page when using Crossover over Wine?
In this case, you would probably just need to know the path to Wine used by Crossover for wacvst when you're editing the config.plist file.

I've been playing with this a bit and unfortunately, its not going to be quite that easy. Crossover uses a bunch of environment variables to get all of their components to communicate with each other, several of which change somewhat dynamically with each launch of crossover. Getting this to work with the current wacvst architecture might be a bit tricky.

djsubject · Post by **djsubject** » Wed Jul 29, 2009 9:56 am

interesting thread!!!

sin night · Post by **sin night** » Mon Aug 03, 2009 9:06 am

I just tried it and it seems to work, now I have to test it carefully with some plugins I'm missing from my windows days to find out how much stable is the current release, however this is a great piece of software! Praise to the dev!

mustgroove · Post by **mustgroove** » Tue Aug 04, 2009 12:46 pm

Just tried this procedure out and it's all worked out so far, except that wacvst.vst appears as a folder in Finder, so there's no "Show Package Contents" option in the right-click menu... Live doesn't seem to be recognising wacvst.vst as a plugin either.

Any tips on this situation?

djanthonyw · Post by **djanthonyw** » Tue Aug 04, 2009 12:54 pm

I had the same problem when trying it twice with it not showing up as a plugin.

mustgroove · Post by **mustgroove** » Tue Aug 04, 2009 12:56 pm

Not sure how, but it works perfectly now, even with the wacvst.vst appearing as a folder rather than a package.

Wow it works spectacularly well for simple stand-alone plugins... The Voxengo plugins which haven't been ported yet (like Marquis) run in demo mode, and considering that their registration scheme is registry-based (from what I can gather) I'm not entirely sure how to get them to run properly using this system... anyone have any clues?

But overall I'm very impressed and it seems entirely possible that this could be turned into a commercial product - Crossover Studio or something similar. I'd buy it for sure, I'd even invest in it's development.

djanthonyw · Post by **djanthonyw** » Tue Aug 04, 2009 1:03 pm

djanthonyw wrote:I had the same problem when trying it twice with it not showing up as a plugin.

Gamma-UT · Post by **Gamma-UT** » Tue Aug 04, 2009 1:09 pm

mustgroove wrote:Just tried this procedure out and it's all worked out so far, except that wacvst.vst appears as a folder in Finder, so there's no "Show Package Contents" option in the right-click menu... Live doesn't seem to be recognising wacvst.vst as a plugin either.

Any tips on this situation?

You need to set the 'bundle bit'. This is easy in Pathfinder, just choose Show Info and find the bit where it says 'Set bundle bit'. I don't think there's an easy way to do that from the Finder.

mustgroove · Post by **mustgroove** » Tue Aug 04, 2009 1:15 pm

Electri-Q works as well but looks like it would face a copy protection issue too - $20 says that if I sent the challenge code off to Aixcoustic, the response generated wouldn't be "valid" to actually register the plugin

mustgroove · Post by **mustgroove** » Tue Aug 04, 2009 1:33 pm

There's also the issue of whether it's possible to have PC-to-Mac compatibility of projects containing wacvst instances of plugins... having wacvst just load the plugins is great, but if it's possible to have compatibility for PCs to open wacvst-containing projects (and vice versa) that would tip this over the edge into super-awesome land

Win-to-OSX VST wrapper/adapter