Its looking more and more like the problem is that winelib programs are tied to the version of wine that they were compiled on. For instance, a winelib program compiled using wine 1.1.30 is not necessarily going to run under wine 1.1.31.
The current binary version of wacvst was compiled using wine 1.1.30. I built my wine directly from source. For those who have managed to get wacvst working I'd be curious as to what version of wine you were running.
Win-to-OSX VST wrapper/adapter
-
virtualinsanity virtualinsanity https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=102898
- KVRist
- 333 posts since 27 Mar, 2006 from Hamburg, Germany
Hey, great thread. But. Hmmpff. I've got some trouble installing Wine:
Computer says Noooo.
Error: You cannot install wine-devel for the architecture(s) i386
Error: because /opt/local/lib/libSM.dylib only contains the architecture(s) x86_64.
Error: Try reinstalling the port that provides /opt/local/lib/libSM.dylib with the +universal variant.
Error: Target org.macports.extract returned: incompatible architectures in dependencies
Error: Status 1 encountered during processing.
I seem to have found a solution here:
http://trac.macports.org/ticket/21865
but that means I have to reinstall a whole lot of ports. First of all that's not funny at all and second, I don't get xorg-libsm reinstalled properly with the +universal argument.
Any ideas what might be wrong? My system (MacOs 10.6.1) was pretty clean before.
XCode and MacPorts are installed, of course.
Thanks
Cheers
Sören
Computer says Noooo.
Error: You cannot install wine-devel for the architecture(s) i386
Error: because /opt/local/lib/libSM.dylib only contains the architecture(s) x86_64.
Error: Try reinstalling the port that provides /opt/local/lib/libSM.dylib with the +universal variant.
Error: Target org.macports.extract returned: incompatible architectures in dependencies
Error: Status 1 encountered during processing.
I seem to have found a solution here:
http://trac.macports.org/ticket/21865
but that means I have to reinstall a whole lot of ports. First of all that's not funny at all and second, I don't get xorg-libsm reinstalled properly with the +universal argument.
Any ideas what might be wrong? My system (MacOs 10.6.1) was pretty clean before.
XCode and MacPorts are installed, of course.
Thanks
Cheers
Sören
und doch, doch, und doooooch!
-
- KVRist
- 40 posts since 22 Mar, 2007
You might want to try building directly from source. See my instructions in page 6 of this thread. Building from source is pretty straightforward. Download the tarball, configure and make. No other packages or ports are needed. If you go this route, download version 1.1.30 as opposed to the newest version 1.1.33 given that the wacvst binary was compiled with 1.1.30.
-
virtualinsanity virtualinsanity https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=102898
- KVRist
- 333 posts since 27 Mar, 2006 from Hamburg, Germany
Hmm.
I finally managed to compile Wine. With the first plugin (B8Organ, just to test), X11 crashed and the second one (my own, still unreleased) simply didn't show up.
But, well, I feel a bit stupid. I said I had installed XCode and the installation guide on page 3 says you need it to install Wine. I should see the XCode IDE when having installed xcode, shouldn't I? Maybe I didn't? At least I remember that I INTENDED to install XCode
I'm pretty sure Wine is, at least, installed. Don't know if it works, though.
Another problem: What's the difference between X11 and XQuartz? Every XQuartz installer I download says, this build was exclusively made for Leopard (Me using Snow Leopard).
But I'm gonna try your version later anyway. Thanks.
Cheers
Sören
I finally managed to compile Wine. With the first plugin (B8Organ, just to test), X11 crashed and the second one (my own, still unreleased) simply didn't show up.
But, well, I feel a bit stupid. I said I had installed XCode and the installation guide on page 3 says you need it to install Wine. I should see the XCode IDE when having installed xcode, shouldn't I? Maybe I didn't? At least I remember that I INTENDED to install XCode
I'm pretty sure Wine is, at least, installed. Don't know if it works, though.Another problem: What's the difference between X11 and XQuartz? Every XQuartz installer I download says, this build was exclusively made for Leopard (Me using Snow Leopard).
But I'm gonna try your version later anyway. Thanks.
Cheers
Sören
und doch, doch, und doooooch!
-
- KVRer
- 13 posts since 5 Dec, 2006
Hey retroware,
I've now built wine from source (version wine-1.1.30) and I no longer get the "Bad EXE format for"-message!
Which is good (I suppose : ) however, the plug-in (dblue_Glitch_v1_3) doesn't show up in Live. Here's the log:
Returning file identifiers: nTDiUjY6PaAFpBR1q0pHR3bjKyvYPaxh72UYCXoreh
RemoteVSTClient: executing /Library/Audio/Plug-Ins/WinVST/wacvst.vst/Contents/Resources/dssi-vst-server.exe.so
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Building font metrics. This may take some time...
Font metrics: 0.0% done
[and on and on about fonts forever and ever...]
As you can see wine cannot find FreeType (might be related to this bughttp://bugs.winehq.org/show_bug.cgi?id=17674 that is said to be fixed in 1.1.31), but I don't think this has anything to do with the plug-in not showing up in Live (I'm using the 8.0.9 demo version).
Regards,
- Jonas
I've now built wine from source (version wine-1.1.30) and I no longer get the "Bad EXE format for"-message!
Which is good (I suppose : ) however, the plug-in (dblue_Glitch_v1_3) doesn't show up in Live. Here's the log:
Returning file identifiers: nTDiUjY6PaAFpBR1q0pHR3bjKyvYPaxh72UYCXoreh
RemoteVSTClient: executing /Library/Audio/Plug-Ins/WinVST/wacvst.vst/Contents/Resources/dssi-vst-server.exe.so
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Building font metrics. This may take some time...
Font metrics: 0.0% done
[and on and on about fonts forever and ever...]
As you can see wine cannot find FreeType (might be related to this bughttp://bugs.winehq.org/show_bug.cgi?id=17674 that is said to be fixed in 1.1.31), but I don't think this has anything to do with the plug-in not showing up in Live (I'm using the 8.0.9 demo version).
Regards,
- Jonas
-
- KVRist
- 185 posts since 22 May, 2003 from Norway
Install wine using the macports commandline with +universal.JOnas666 wrote: As you can see wine cannot find FreeType (might be related to this bughttp://bugs.winehq.org/show_bug.cgi?id=17674 that is said to be fixed in 1.1.31), but I don't think this has anything to do with the plug-in not showing up in Live (I'm using the 8.0.9 demo version).
Regards,
- Jonas
This will install all the dependencies. I guess if you compile wine by hand, you can exclude stuff like freetype etc.
Porticus is nice to view the deps.
I followed this tutorial in this thread:
http://www.kvraudio.com/forum/viewtopic ... 57#3685457
Just remember +universal. That will make 32bit wine.
A is A
-
- KVRist
- 40 posts since 22 Mar, 2007
Actually, this is expected behavior. The first time you start wine, it builds a font cache to make things quicker on subsequent loads. But, because it takes so long the first time, Live thinks the plugin has failed and doesn't make it available. The freetype warning can be safely ignored.JOnas666 wrote:Hey retroware,
I've now built wine from source (version wine-1.1.30) and I no longer get the "Bad EXE format for"-message!
Which is good (I suppose : ) however, the plug-in (dblue_Glitch_v1_3) doesn't show up in Live. Here's the log:
Returning file identifiers: nTDiUjY6PaAFpBR1q0pHR3bjKyvYPaxh72UYCXoreh
RemoteVSTClient: executing /Library/Audio/Plug-Ins/WinVST/wacvst.vst/Contents/Resources/dssi-vst-server.exe.so
Wine cannot find the FreeType font library. To enable Wine to
use TrueType fonts please install a version of FreeType greater than
or equal to 2.0.5.
http://www.freetype.org
Building font metrics. This may take some time...
Font metrics: 0.0% done
[and on and on about fonts forever and ever...]
As you can see wine cannot find FreeType (might be related to this bughttp://bugs.winehq.org/show_bug.cgi?id=17674 that is said to be fixed in 1.1.31), but I don't think this has anything to do with the plug-in not showing up in Live (I'm using the 8.0.9 demo version).
Try this,
Start up live and wait for the building fonts thing to finish (it typically takes a minute or two). Quit live. Move wacvst out of the Plugin folder and restart live. Quit live again and place wacvst back into the plugin folder. Or alternatively follow the rescan trick posted earlier in this thread.
Restart live. This time, you should NOT get the building font metrics thing. Please report if you do. Hopefully, wacvst will now be available for use by Live.
-
- KVRer
- 13 posts since 5 Dec, 2006
Thanks again for your quick replies! Unfortunatley I get the building font metrics thing everytime I use (this installation of) Wine (regardless of which windows program I throw at it - first the font metrics thing and then the program starts). So my best guess is that there's something wrong with my wine installation.retroware wrote:Actually, this is expected behavior. The first time you start wine, it builds a font cache to make things quicker on subsequent loads. But, because it takes so long the first time, Live thinks the plugin has failed and doesn't make it available. The freetype warning can be safely ignored.
Try this,
Start up live and wait for the building fonts thing to finish (it typically takes a minute or two). Quit live. Move wacvst out of the Plugin folder and restart live. Quit live again and place wacvst back into the plugin folder. Or alternatively follow the rescan trick posted earlier in this thread.
Restart live. This time, you should NOT get the building font metrics thing. Please report if you do. Hopefully, wacvst will now be available for use by Live.
The time it takes to do the font thing might be the reason that Live doesn't make the plug-in avaliable, but when I force a rescan Live waits until the whole font etc process is done and then I can close the preferences. So I kind of get the feeling that it might not be the time it takes to do the fonts thing that is the problem but I might be wrong here. (I've tried it in Reaper as well - my main DAW - with the exact same results, it waits until the fonts etc is done and then moves on to other plugs, but when done wacvst isn't in the list.)
I'll have to try that - until yesterday I had a Wine installed via macports but it gave the Bad EXE... message when I tried wacvst. However, that wasn't wine-devel (just "wine") so I'll give the devel version a spin. Thanks for helping out!Ad0 wrote:Install wine using the macports commandline with +universal.
This will install all the dependencies. I guess if you compile wine by hand, you can exclude stuff like freetype etc.
Porticus is nice to view the deps.
I followed this tutorial in this thread:
http://www.kvraudio.com/forum/viewtopic ... 57#3685457
Just remember +universal. That will make 32bit wine.
Regards,
- Jonas
-
- KVRer
- 13 posts since 5 Dec, 2006
Hey all,
Here's the result from using wine-devel installed via macports and the +universal switch (wine-1.1.33).
No Bad EXE..., no font metrics-thing which is good. But now I get this:
Returning file identifiers: qgJWtVxweAxvLLDej0Q23EkNyQdb3RgK9jKsVyVJBJ
RemoteVSTClient: executing /Library/Audio/Plug-Ins/WinVST/wacvst.vst/Contents/Resources/dssi-vst-server.exe.so
/opt/local/lib/../bin/wine: line 5: 41225 Bus error DYLD_FALLBACK_LIBRARY_PATH="/opt/local/lib" "/opt/local/libexec/wine/wine" "$@"
... and the plug-in doesn't show up in Live or Reaper (x11 starts up, though). Wish I had some idea but a quick Google search didn't give me much - I'll continue searching but if anyone has any ideas I'd love to hear them : )
I've tried a few Windows apps (notepad, pathsync...) on this wine install and they seem to work just fine.
Regards,
- Jonas
Here's the result from using wine-devel installed via macports and the +universal switch (wine-1.1.33).
No Bad EXE..., no font metrics-thing which is good. But now I get this:
Returning file identifiers: qgJWtVxweAxvLLDej0Q23EkNyQdb3RgK9jKsVyVJBJ
RemoteVSTClient: executing /Library/Audio/Plug-Ins/WinVST/wacvst.vst/Contents/Resources/dssi-vst-server.exe.so
/opt/local/lib/../bin/wine: line 5: 41225 Bus error DYLD_FALLBACK_LIBRARY_PATH="/opt/local/lib" "/opt/local/libexec/wine/wine" "$@"
... and the plug-in doesn't show up in Live or Reaper (x11 starts up, though). Wish I had some idea but a quick Google search didn't give me much - I'll continue searching but if anyone has any ideas I'd love to hear them : )
I've tried a few Windows apps (notepad, pathsync...) on this wine install and they seem to work just fine.
Regards,
- Jonas
-
- KVRist
- 369 posts since 18 Sep, 2008
Personally I just reverted to 10.5 and everything works fine. Using WusikVM as an intermediary between WacVST and your target VST fixes the issues with preset loading (with plugins that don't have a preset menu, e.g. firebird+), and is quite handy for browsing through them in comparison.
Does anyone know any freebie/super cheap windows VST-format VSTi plugin chainers? Could be a good temporary solution for those of us trying to use a few instances
I now know for a fact that kore *will not* work within wine :/
Does anyone know any freebie/super cheap windows VST-format VSTi plugin chainers? Could be a good temporary solution for those of us trying to use a few instances
I now know for a fact that kore *will not* work within wine :/-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Any further updates on this retroware? I noticed an update to Xcode (version 3.2.1) appear in Software Update the other day... haven't installed it as yet, but I wonder whether it might make any difference...
Quite tempted to just roll back, seeing as wacvst works pretty well under 10.5.8, but it's gonna be such a monumental effort I'd prefer just to wait for a 10.6-compatible wacvst...
Quite tempted to just roll back, seeing as wacvst works pretty well under 10.5.8, but it's gonna be such a monumental effort I'd prefer just to wait for a 10.6-compatible wacvst...
-
- KVRist
- 40 posts since 22 Mar, 2007
I'll be posting a minor update in the very near future.
I'm still a bit puzzled as to what is causing the 10.6 issues on different machines. I've managed to get wacvst 0.3 working on two different 10.6.2 machines. I've even gotten it to work with Live 8. The updated version I'm going to put out has a couple of small changes that might make a difference but I fear that I still haven't gotten to the bottom of the problem.
The one thing that is maybe "special" about my machine is that I've never installed either wine or X11 from macports. I always build wine from the winehq.org source and use Apple's X11. One thing to try is to temporarily disable macports by moving the /opt directory to one with a different name, say /opt-tmp. Also, move the ~/.wine directory to ~/.wine-tmp. Then build and install wine and give wacvst another shot.
The other difference is that I have /usr/local/bin in my path. I don't think this should make a difference but who knows.
The other thing to try is to load wacvst under the terminal based misswatson host (www.teragon.org).
Give it the flags -editor -plugin=wacvst
This will generate lots of debugging output to the terminal which if you send to me will maybe help debug the problem. Plus, this gets rid of any issues introduced by a more complex host such as Live.
I'm still a bit puzzled as to what is causing the 10.6 issues on different machines. I've managed to get wacvst 0.3 working on two different 10.6.2 machines. I've even gotten it to work with Live 8. The updated version I'm going to put out has a couple of small changes that might make a difference but I fear that I still haven't gotten to the bottom of the problem.
The one thing that is maybe "special" about my machine is that I've never installed either wine or X11 from macports. I always build wine from the winehq.org source and use Apple's X11. One thing to try is to temporarily disable macports by moving the /opt directory to one with a different name, say /opt-tmp. Also, move the ~/.wine directory to ~/.wine-tmp. Then build and install wine and give wacvst another shot.
The other difference is that I have /usr/local/bin in my path. I don't think this should make a difference but who knows.
The other thing to try is to load wacvst under the terminal based misswatson host (www.teragon.org).
Give it the flags -editor -plugin=wacvst
This will generate lots of debugging output to the terminal which if you send to me will maybe help debug the problem. Plus, this gets rid of any issues introduced by a more complex host such as Live.
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Any chance you might be able to post some instructions on how to build wine using this method? The closer we can get to replicating your method, the greater the chance we might also be able to get it workingretroware wrote:I always build wine from the winehq.org source and use Apple's X11.
-
- KVRist
- 40 posts since 22 Mar, 2007
The newest version can be downloaded from:
http://sourceforge.net/projects/wacvst/ ... p/download
The included README has instructions on how I built wine together with some troubleshooting tips.
One thing that is still missing from the README is the need to set the bundle bit using the following command:
SetFile -a Bi [path to the wacvst.vst folder]
If I get some time over the weekend I'm going to try and build a distributable wine that will eliminate the need to compile it.
http://sourceforge.net/projects/wacvst/ ... p/download
The included README has instructions on how I built wine together with some troubleshooting tips.
One thing that is still missing from the README is the need to set the bundle bit using the following command:
SetFile -a Bi [path to the wacvst.vst folder]
If I get some time over the weekend I'm going to try and build a distributable wine that will eliminate the need to compile it.
-
- KVRer
- 4 posts since 5 Dec, 2009
first off, thank you so much! i cant wait to give wine a spin, but i'm definitely a neophyte, and i'm having trouble installing it. I've followed the instructions in the README and on page 6 to the t, however i can't get Wine to end up in /usr/local/bin...
i'm guessing that Wine creates some windows-esque directory, but i dont see it anywhere.
lastly, when i type 'winecfg' i get the following error: "wine: '/Users/Hal' is not owned by you, refusing to create a configuration directory there". what's up with this? how do i fix it?
by the way, i'm running Snow Leopard 10.6.2
downloaded wine-1.1.33 (per the README)
thanks guys so much!!!
i'm guessing that Wine creates some windows-esque directory, but i dont see it anywhere.
lastly, when i type 'winecfg' i get the following error: "wine: '/Users/Hal' is not owned by you, refusing to create a configuration directory there". what's up with this? how do i fix it?
by the way, i'm running Snow Leopard 10.6.2
downloaded wine-1.1.33 (per the README)
thanks guys so much!!!