Page 1 of 1

Wine issues (e.g. affecting VSL Performance Tool)

Posted: Sun Mar 29, 2009 12:34 am
by dahnielson
Just a heads up, I had to downgrade from Wine 1.1.12 to version 1.1.11 to be able to run any audio application.

Re: Wine issues (e.g. affecting VSL Performance Tool)

Posted: Sun Mar 29, 2009 8:44 am
by ccherrett
I am running the performance tool with: wine-1.1.13

Re: Wine issues (e.g. affecting VSL Performance Tool)

Posted: Mon Mar 30, 2009 3:59 am
by ccherrett
If that was not clear the newest version of wine works and allows you to see the actual name of the ports in the program running in wine. So update :)

Re: Wine issues (e.g. affecting VSL Performance Tool)

Posted: Mon Mar 30, 2009 3:47 pm
by dahnielson
ccherrett wrote:If that was not clear the newest version of wine works and allows you to see the actual name of the ports in the program running in wine. So update :)
Yep, I'm seeing them too in the version I'm running. Appears that .12 is a bad apple on my machine.

Re: Wine issues (e.g. affecting VSL Performance Tool)

Posted: Mon Mar 30, 2009 4:55 pm
by ccherrett
dahnielson wrote:
ccherrett wrote:If that was not clear the newest version of wine works and allows you to see the actual name of the ports in the program running in wine. So update :)
Yep, I'm seeing them too in the version I'm running. Appears that .12 is a bad apple on my machine.
So did .13 work for you?

What VSL libraries are you running and did you midi map them out?

Re: Wine issues (e.g. affecting VSL Performance Tool)

Posted: Mon Mar 30, 2009 7:22 pm
by dahnielson
ccherrett wrote:
dahnielson wrote:
ccherrett wrote:If that was not clear the newest version of wine works and allows you to see the actual name of the ports in the program running in wine. So update :)
Yep, I'm seeing them too in the version I'm running. Appears that .12 is a bad apple on my machine.
So did .13 work for you?
I haven't tried it yet. Just masked .12 and waiting for >.12 to be deemed stable. Everything works now so I'm not sweating it to upgrade (looks like .17 is the latest ebuild in portage).

BTW, my issue affected all audio applications I tried to run. Noticed it first when Reaper refused to launch, and noticed the port names in Kontakt -- no more guessing. :D
ccherrett wrote:What VSL libraries are you running and did you midi map them out?
Opus 1 and no I haven't bothered to do that again.