Home » Forums » Applications

wineasio 0.7.4 invisible to wine/wineapps?

Is anyone else having a problem with wine applications seeing wineasio as a driver option? I have compiled 0.7.4 to use with wine 0.9.58 from the winehq repos. compile and install appear successful, and regsvr32 wineasio.dll reports success.

however, when i start Pianoteq standalone (vs VST plugin) for some reason it is not seeing wineasio as a configuration option. unfortunately, i do not have another wine app to test it with.

I had it working in Ubuntu before, so I know it is not impossible...but i also do not know where the problem lies: with wineasio, wine, or Pianoteq.

does anyone have any tips on troubleshooting/collecting helpful information about this mystery?

i am using checkinstall 1.6 during the compile/install process in order to keep everything clean and manageable. i have also used it for dss-vst which is working perfectly, so i don't believe it is a problem. in fact, perhaps it is something 64studio could include in the repos or even a default install...it is very helpful.

ok,
thanks

‹ Jack broken pipe error nautilus side panel ›

operator error??

I am hoping this was a simple error.

Someone suggested "regsvr32 /path/to/actual/wineasio.dll.so" instead of "regsvr32 wineasio.dll"

so i will try that and report back

if anyone else has any suggestions as to common mistakes that i could have made...much appreciated :)

  • By ethanay at 05/26/2008 - 23:22
  • Login or register to post comments

problem solved

I clobbered the wineasio problem: completely uninstalled pianoteq, wineasio, wine, removed the .wine folder

uninstalled jackdmp, libjackmp and reinstalled jackd for good measure

reinstalled wine
reinstalled wineasio
"regsvr32 /usr/lib/wine/wineasio.dll.so"
ran winecfg to detect alsa audio
reinstalled Pianoteq

and was able to select wineasio! the splash screen now does not work but I don't care much about that! also, I have to start pianoteq before jack otherwise pianoteq won't start at all (freezes). so I now have pianoteq vst and pianoteq standalone working well for maximum flexibility. this is very good. there seem to be less xruns with jackd even though it uses more processor (~1.5x's as much as jackdmp).

not sure what the problem was: either 1) a jackdmp error or 2) a problem with typing "regsvr32 wineasio.dll." If that is the wrong command, then it shouldn't give a message, "driver successfully registered" when it doesn't actually register a driver!!

  • By ethanay at 05/28/2008 - 05:43
  • Login or register to post comments

Same problem

I have the same problem, and tried this, but it doesen´t work.
But when I use regsvr32wineasio.dll I get the following:

64studio:/home/thomas# regsvr32 wineasio.dll
fixme:mixer:ALSA_MixerInit No master control found on Keystation Pro 88, disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on MPU-401 UART, disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on M Audio Audiophile 24/96, disabling mixer
Successfully registered DLL wineasio.dll

Maybe the master control has something to do with the problem?????

Who can help?

  • By thomasK at 08/16/2008 - 11:55
  • Login or register to post comments

By the way

I didn´t use Pianoteq, I have the problem with Reaper and VSThost

  • By thomasK at 08/16/2008 - 12:01
  • Login or register to post comments

i've gotten those messages before

they've appeared when i had things plugged in and running, i think

when i registered successfully, i didn't have anything plugged in and running (midi controllers, external soundcards, jackd, etc)

also, i typed exactly:
regsvr32 /usr/lib/wine/wineasio.dll.so

which is the exact location of the file for regsvr32 to deal with

are you using jackdmp or jackd?

also, did you follow the exact order of events that i described above? i know you're not dealing specifically with pianoteq -- but substitute the programs that you are using in that place

  • By ethanay at 08/18/2008 - 08:36
  • Login or register to post comments