Run Windows VSTi's on Mac OSX EASILY with Low latency :-)

[Calum]

where did you copy the wineasio.dll.so file? I am not 100% sure where that path is for winebottler, I use his distro of wine generally, but not winebottler. Anyway, if that doesn't work, try to open cmd.exe and type the command in there, watch the results.

I copied the wineasio.dll.so file to /Applications/Wine.app/Contents/Resources/lib/wine and this directory contains a pile of other .dll.so files so I thought it was the right place. I found cmd.exe but could not get to open.

So my next question is, can I use the Winebottler distro with Wineskin because that appears to be the perfect solution? (Actually, wacvst would have been the perfect solution but, after days setting it up, I only got one plugin running for a few minutes before everything crashed). I agree with your comments about Wineskin. I love the convenience of being able to easily add stuff to a Wineskin app. When I was on Snow Leopard I created a Wineskin app based on Jamstixwine with a pile of VSTi's that I could share with 6 hosts (Mulab/EXT1/EXT2/SAVIHost/VSTHost/MiniHost Modular), all in the one package. Unfortunately I deleted the lot accidentally, in frustration, when i had to perform a clean install of Mavericks. So now I'm trying to create the same setup again in Mavericks with Wineskin, the new version of wineasio you mentioned and hopefully the Winebottler distro or similar without the need for X11.

While I have your attention, one more question. Is the sym links script fix that came with Jamstixwine still required with the new wineasio and JackOSX 0.89/0.90?

[Dewdman42]

where did you copy the wineasio.dll.so file? I am not 100% sure where that path is for winebottler, I use his distro of wine generally, but not winebottler. Anyway, if that doesn't work, try to open cmd.exe and type the command in there, watch the results.

I copied the wineasio.dll.so file to /Applications/Wine.app/Contents/Resources/lib/wine and this directory contains a pile of other .dll.so files so I thought it was the right place. I found cmd.exe but could not get to open.

So my next question is, can I use the Winebottler distro with Wineskin because that appears to be the perfect solution? (Actually, wacvst would have been the perfect solution but, after days setting it up, I only got one plugin running for a few minutes before everything crashed). I agree with your comments about Wineskin. I love the convenience of being able to easily add stuff to a Wineskin app. When I was on Snow Leopard I created a Wineskin app based on Jamstixwine with a pile of VSTi's that I could share with 6 hosts (Mulab/EXT1/EXT2/SAVIHost/VSTHost/MiniHost Modular), all in the one package. Unfortunately I deleted the lot accidentally, in frustration, when i had to perform a clean install of Mavericks. So now I'm trying to create the same setup again in Mavericks with Wineskin, the new version of wineasio you mentioned and hopefully the Winebottler distro or similar without the need for X11.

While I have your attention, one more question. Is the sym links script fix that came with Jamstixwine still required with the new wineasio and JackOSX 0.89/0.90?

I'm actually not sure if the symlink is still required, I can't remember the details of that actually. It will be some time before I can do any kind of experimentation to figure that out, sorry. Possibly not, but I can't recall the details at the moment. But you should be able to create that symlink without breaking anything, so if you don't get it working, try the symlink, never know.

Wineskin works without winebottler, they are two different approaches to the same thing. But inside Wineskin there is a config program you can launch and it has a command line button that will launch the command line (cmd.exe) and you can type the regsvr32 command in there. You have to dig a little deeper to find the location of all the *.dll.so files in wineskin.

I'm not super familiar with winebottler so unfortunately I can't break it down and it will be a few more weeks before I can spend any time to try to figure it out for you, unfortunately.

At this point I am just using the generic wine.app which is distributed by the guy that makes winebottler. That way I can have lots of programs installed and from any OSX command line I can just type "wine <exe path> to launch a windows program. Works pretty well. There are a lot of different approaches with wine, but unfortunately with each one you kind of have to figure out how to launch programs with it, like how to launch cmd.exe or how to launch regsvr32.exe in order to register the wineasio.dll

[Dewdman42]

So, downloaded Wineasio from the link

Do I need to makefile anything to get the "wineasio.dll" created, what I see is a file called "wineasio.dll.spec"?

see, not too easy for a newb!!!

Don't download the source. Click on the green button to download the pre compiled wineasio.dll.so file.

[carrieres]

nice tips, thanks you

[Calum]

where did you copy the wineasio.dll.so file? I am not 100% sure where that path is for winebottler, I use his distro of wine generally, but not winebottler. Anyway, if that doesn't work, try to open cmd.exe and type the command in there, watch the results.

I copied the wineasio.dll.so file to /Applications/Wine.app/Contents/Resources/lib/wine and this directory contains a pile of other .dll.so files so I thought it was the right place. I found cmd.exe but could not get to open.

So my next question is, can I use the Winebottler distro with Wineskin because that appears to be the perfect solution? (Actually, wacvst would have been the perfect solution but, after days setting it up, I only got one plugin running for a few minutes before everything crashed). I agree with your comments about Wineskin. I love the convenience of being able to easily add stuff to a Wineskin app. When I was on Snow Leopard I created a Wineskin app based on Jamstixwine with a pile of VSTi's that I could share with 6 hosts (Mulab/EXT1/EXT2/SAVIHost/VSTHost/MiniHost Modular), all in the one package. Unfortunately I deleted the lot accidentally, in frustration, when i had to perform a clean install of Mavericks. So now I'm trying to create the same setup again in Mavericks with Wineskin, the new version of wineasio you mentioned and hopefully the Winebottler distro or similar without the need for X11.

While I have your attention, one more question. Is the sym links script fix that came with Jamstixwine still required with the new wineasio and JackOSX 0.89/0.90?

I'm actually not sure if the symlink is still required, I can't remember the details of that actually. It will be some time before I can do any kind of experimentation to figure that out, sorry. Possibly not, but I can't recall the details at the moment. But you should be able to create that symlink without breaking anything, so if you don't get it working, try the symlink, never know.

Wineskin works without winebottler, they are two different approaches to the same thing. But inside Wineskin there is a config program you can launch and it has a command line button that will launch the command line (cmd.exe) and you can type the regsvr32 command in there. You have to dig a little deeper to find the location of all the *.dll.so files in wineskin.

I'm not super familiar with winebottler so unfortunately I can't break it down and it will be a few more weeks before I can spend any time to try to figure it out for you, unfortunately.

At this point I am just using the generic wine.app which is distributed by the guy that makes winebottler. That way I can have lots of programs installed and from any OSX command line I can just type "wine <exe path> to launch a windows program. Works pretty well. There are a lot of different approaches with wine, but unfortunately with each one you kind of have to figure out how to launch programs with it, like how to launch cmd.exe or how to launch regsvr32.exe in order to register the wineasio.dll

No need to look into this any further for me. I downloaded the latest wineskin/wineasio/jackOSX and had it all up and running in no time and I think i have answered all of my own questions. The biggest surprise is that the latest version of wine that wineskin download's may not be the same build as Winebottler distributes but it is the same version and the windowing environment works in exactly the same way (so no need for me to use the Winebottler distro). JackOSX 0.90 and the new wineasio are behaving well in Mavericks and the extra channels will come in very useful. I'm also fairly sure the sym links script is no longer required as everything worked "out of the box" without the need to use the jamstixwine installer to run the script.

Hope I haven't wasted too much of your time but at least your feedback gave me the confidence to have another go at this (Mavericks is very flakey on my Mac and I'm trying to avoid another reinstall). Also gave me the chance to finally say thank you for jamstixwine without which I would have probably given up on trying to use PC VSTs on a MAC.

[Dewdman42]

glad to hear its been helpful!

[Dewdman42]

The biggest surprise is that the latest version of wine that wineskin download's may not be the same build as Winebottler distributes but it is the same version and the windowing environment works in exactly the same way .

Yea it can get a little confusing. Basically its all fine and they all are based off the same wine source. The wine source is updated pretty much weekly. Anyone at any time can download the very latest source and build it yourself, which can be a pain on OSX, easy on linux. The guy who makes wine bottler distributes two things of interest, he distributes Winebottler.app and Wine.app. Wine.app is just pretty much an OSX build of the latest wine source. He might be a week behind schedule or something but he keeps it pretty up to date. I am using his Wine.app now for my wine environment. I used to use Wineskin for everything before that.

Wineskin is same concept as winebottler, but instead of rebuilding the whole wineskin binary every week, his wineskin binary will download the latest builds of wine which he updates from time to time, in my experience, not quite as frequently as winebottler, but after while I get sick and tired of trying to stay up to date on wine anyway, it is constantly being updated. Might as well just use a build that works and leave it at that. If it ain't broke don't mess with it.

Wineskin has a much nicer configuration environment then Winebottler in my view, but they are both cool in their own ways, but I find wineskin config tool rather nice to work with. The author of Winebottler did respond to my request to change his build of wine in general so that it uses better font handling, not sure if wineskin is doing that right yet or not. Basically either one will be very close to the same version of wine and most things will work in one or the other just fine.

I choose to just use Wine.app and I don't use any kind of wrapper now, because I use a number of different apps under wine and this way its a bit easier to just use the Wine.app to launch them. I even was able to setup a handler on osx that when I double click on any .exe file in OSX, it automatically launches wine.app and runs the program and most of the time it works pretty well too. I can't remember the details of that now, I think I had to create an Applescript to launch Wine.App or something like that, google around, I found something someone else had already did. Winebottler and wineskin are more self contained and there is beauty in that, but then you end up with copying a couple hundred mb's or more of wine junk into each wineskin bundle you make. So once I got more comfortable with how wine works, I just am inclined to use the Wine.app directly. From the command line I can always launch just about any exe by typing "wine myprogram.exe" and it will launch and/or I can use the applescript thing I mentioned that lets me just double click on an EXE and launch Wine.app, etc.

Its all good, different strokes for different folks.

[basslinemaster]

hehe bootcamp is a lot more hassle then that, I have been down that road. Honestly I've tried all the solutions over several years, wineasio under free wine is the best way to go. You can still record your projects in Logic or DP or PT or whatever OSX DAW you want and just use wine for hosting the actual VST that way. You can even use a much simpler host then MuLab, like VstHost (free), which works just fine under wine.

It's "more... than", not "more... then"...

[Anantich]

Thanks for all your help, folks! I'm successfully setup Jack, wine (with wineasio.dll). I'm able to route audio from Reaper on mac to Reaper on Wine (with win VST's) and back. Jack-Insert plugin is still 32bit only, so it works only for 32bit Reaper. Latency is much better then with NetVST