Win-to-OSX VST wrapper/adapter
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Excellent news!!! Much appreciated
-
- KVRist
- 40 posts since 22 Mar, 2007
Hmmm, the problem seems to be a bit more subtle than I originally thought. I am however working on it and hope to have a 10.6 compatible version out not to far in the future.
What is curious is that wacvst works fine using Live 7.0.10 under Snow Leopard but not 7.0.16. I'm still trying to figure out exactly why. I'm guessing that whatever the problem is, its the same problem that is causing Live 8/Snow Leopard to fail.
Are any other developer types playing with wacvst? Any help in figuring out what might be the problem would be greatly appreciated. I pretty much just work on wacvst in my spare time as an interesting "experiment".
What is curious is that wacvst works fine using Live 7.0.10 under Snow Leopard but not 7.0.16. I'm still trying to figure out exactly why. I'm guessing that whatever the problem is, its the same problem that is causing Live 8/Snow Leopard to fail.
Are any other developer types playing with wacvst? Any help in figuring out what might be the problem would be greatly appreciated. I pretty much just work on wacvst in my spare time as an interesting "experiment".
-
- KVRist
- 40 posts since 22 Mar, 2007
A new version of wacvst is available at:
https://sourceforge.net/projects/wacvst ... p/download
This new version:
Appears to work under 10.6
Allows for more than one wacvst instance
Tracks with a wacvst plugin can be deleted without crashing the host.
Source tarballs are no longer being distributed. The source is available through sourceforge svn.
https://sourceforge.net/projects/wacvst ... p/download
This new version:
Appears to work under 10.6
Allows for more than one wacvst instance
Tracks with a wacvst plugin can be deleted without crashing the host.
Source tarballs are no longer being distributed. The source is available through sourceforge svn.
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Much appreciated mate!!! Have only had a couple minutes to test it so far and I can't get to work as yet, Live [8.0.8] is scanning and recognising my wacvst-wrapped plugin, and X11 is opening while it does this, but when the Live GUI eventually pops up the plugin is missing from my plugin folder...
I'll retry your newer method for compiling Wine and give it a more thorough go later tonight, and post my results back here.
I'll retry your newer method for compiling Wine and give it a more thorough go later tonight, and post my results back here.
-
- KVRist
- 40 posts since 22 Mar, 2007
Also try this:mustgroove wrote:Much appreciated mate!!! Have only had a couple minutes to test it so far and I can't get to work as yet, Live [8.0.8] is scanning and recognising my wacvst-wrapped plugin, and X11 is opening while it does this, but when the Live GUI eventually pops up the plugin is missing from my plugin folder...
I'll retry your newer method for compiling Wine and give it a more thorough go later tonight, and post my results back here.
Remove wacvst from your plugin directory.
Start Live and then exit.
Put wacvst back into the plugin directory (to force a rescan)
Start X11 by just double clicking the X11 icon. - Do this before starting Live
Start Live.
When Live first scans, I've found that if a plugin doesn't fully initialize within a certain amount of time, then Live doesn't recognize it. If X isn't running, initialization can take a bit of time since X needs to get fired up. Prestarting X solves this problem. This is only an issue the first time one adds wacvst to the plugin folder. After that, Live will wait for X to get started.
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Yup I did the remove-to-rescan trick Just tried having X11 open when Live rescanned wacvst but didn't work unfortunately... am now retrying everything from scratch - recompiling Wine using your command line method is up first...
Will post back with my results
Just tried having X11 open when Live rescanned wacvst but didn't work unfortunately... am now retrying everything from scratch - recompiling Wine using your command line method is up first...Will post back with my results
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
OK so still no love unfortunately...
- I removed wacvst.vst from my VST folder & ran Live to clear the plugin from its cache...
- Then I ran X11 as you suggested, to hopefully ease the scanning process
- Then I copied wacvst.vst back to my VST folder and ran Live... it scanned wacvst.vst for a good 10 seconds or so, but when the Live is done booting up and the GUI finally shows up, the plugin is nowhere to be found in the plugins folder.
X11 isn't crashing, Live isn't crashing, Live isn't giving a "wacvst isn't compatible with Live" (which it used to do), it's just not showing up in the plugins list...
Are there any logs I can send which would help you pinpoint the problem? Or perhaps is my Wine no compiled properly? I used your commandline method but there's so much verbose feedback from the compiler, who knows if there's any error messages in there I may have missed...
- I removed wacvst.vst from my VST folder & ran Live to clear the plugin from its cache...
- Then I ran X11 as you suggested, to hopefully ease the scanning process
- Then I copied wacvst.vst back to my VST folder and ran Live... it scanned wacvst.vst for a good 10 seconds or so, but when the Live is done booting up and the GUI finally shows up, the plugin is nowhere to be found in the plugins folder.
X11 isn't crashing, Live isn't crashing, Live isn't giving a "wacvst isn't compatible with Live" (which it used to do), it's just not showing up in the plugins list...
Are there any logs I can send which would help you pinpoint the problem? Or perhaps is my Wine no compiled properly? I used your commandline method but there's so much verbose feedback from the compiler, who knows if there's any error messages in there I may have missed...
-
- KVRist
- 369 posts since 18 Sep, 2008
mustgroove - the following should help wacvst show up in scans.
Open terminal.
Close terminal.
As far as clearing the live plugin cache goes, here's an easier trick --
Go to /library/audio/plug-ins in finder, and make a new folder (e.g. WinVST).
In live's preferences, choose "use custom VST plugin folder", and select the folder you just made.
Every time you want to rescan wacvst, turn the "use custom VST plugin folder" off and on.
FYI, the snow leopard alpha of XQuartz works smoothly with SL / wine / wacvst.
My desktop is back on leopard (had massive issues with snow leopard not recognizing drives and freezing constantly...I think there might be something wrong with my mac that apple's retail stores can't seem to find) and I've found that wacvst 0.2 works a lot better than 0.3.
Here's my latest bug report --
- 0.3 breaks firebird+ (at least in demo mode, waiting for license transfer to use full version), mostly works in 0.2 (changing presets occasionally causes Live to crash, I haven't pinpointed the issue -- I believe it has something to do with any voices playing at all when it shifts, but even when it seems like they're all off, it'll crash after I've changed waveforms and then picking a different preset). Perhaps the process needs to be paused when a preset change is sent and then resumed after it enters the wrapped plugins' queue?
- Application focus with XQuartz/X11 causes sound to stop if I leave the mouse button down for too long while tweaking a knob or selecting from a drop-down box's list. Perhaps some sort of client/server accelerator or hook (I don't know the mac equivalents) would solve this?
- (Known) - you can only have one plugin wrapped with WacVST, regardless of what parameters you change in the .plist files (bundle identifier, etc) or ableton crashes on VST scan. Could this have something to do with DSSI and how it hooks into the wrapped audio drivers? If so, it looks like you may need to do a server/client setup with DSSI running in the background and connecting to plugins on demand.
Open terminal.
Code: Select all
Type "/library/audio/plug-ins/VST/"
Type "SetFile -a BI wacvst.vst"
As far as clearing the live plugin cache goes, here's an easier trick --
Go to /library/audio/plug-ins in finder, and make a new folder (e.g. WinVST).
In live's preferences, choose "use custom VST plugin folder", and select the folder you just made.
Every time you want to rescan wacvst, turn the "use custom VST plugin folder" off and on.
FYI, the snow leopard alpha of XQuartz works smoothly with SL / wine / wacvst.
My desktop is back on leopard (had massive issues with snow leopard not recognizing drives and freezing constantly...I think there might be something wrong with my mac that apple's retail stores can't seem to find) and I've found that wacvst 0.2 works a lot better than 0.3.
Here's my latest bug report --
- 0.3 breaks firebird+ (at least in demo mode, waiting for license transfer to use full version), mostly works in 0.2 (changing presets occasionally causes Live to crash, I haven't pinpointed the issue -- I believe it has something to do with any voices playing at all when it shifts, but even when it seems like they're all off, it'll crash after I've changed waveforms and then picking a different preset). Perhaps the process needs to be paused when a preset change is sent and then resumed after it enters the wrapped plugins' queue?
- Application focus with XQuartz/X11 causes sound to stop if I leave the mouse button down for too long while tweaking a knob or selecting from a drop-down box's list. Perhaps some sort of client/server accelerator or hook (I don't know the mac equivalents) would solve this?
- (Known) - you can only have one plugin wrapped with WacVST, regardless of what parameters you change in the .plist files (bundle identifier, etc) or ableton crashes on VST scan. Could this have something to do with DSSI and how it hooks into the wrapped audio drivers? If so, it looks like you may need to do a server/client setup with DSSI running in the background and connecting to plugins on demand.
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Fidelity & Ad0 - which method did you guys use to compile Wine? The commandline method posted by retroware, or the Macports/Porticus method?
-
- KVRist
- 185 posts since 22 May, 2003 from Norway
I used macports commandline.
port install wine-devel +universal
I am in SL so I had to do universal. Remember to install the latest X11 alpha in that case.
How does this thing behave in the AU wrapper from IE. FXpansion?
Is it stable when closing the window / reopening / hiding the plugin, bringing it out again (violent actions for a piece of code).
Is it possible to make an AU version as well? And how do I get debug output from it?
Thanks!
port install wine-devel +universal
I am in SL so I had to do universal. Remember to install the latest X11 alpha in that case.
How does this thing behave in the AU wrapper from IE. FXpansion?
Is it stable when closing the window / reopening / hiding the plugin, bringing it out again (violent actions for a piece of code).
Is it possible to make an AU version as well? And how do I get debug output from it?
Thanks!
A is A
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Hmmmm OK so I've compiled wine-devel from the commandline as you suggested, and it's worked OK (by the looks of it) but now X11 isn't working properly - I installed 2.4.1beta3 and now when X11 loads (either by itself, or when wacvst s being "scanned" by Live) it just bounces several times in the dock and then just sits there - it never loads properly at all...
If it's not one thing, it's another
It seems to be related to 2.4.1beta3, as X11 was working fine before I installed it... is there any way to uninstall X11?
If it's not one thing, it's another
It seems to be related to 2.4.1beta3, as X11 was working fine before I installed it... is there any way to uninstall X11?-
- KVRist
- 369 posts since 18 Sep, 2008
I used porticus so I could leave my account un-passworded. As for X11, use XQuartz -- works every time for me.mustgroove wrote:Fidelity & Ad0 - which method did you guys use to compile Wine? The commandline method posted by retroware, or the Macports/Porticus method?