[Wine]Wine and ALSA

Mark Knecht markknecht at gmail.com
Sat Apr 23 09:33:17 CDT 2005

   OK, if the dmix option isn't doing it and I believe switching to
Alsa will only make it worse since Alsa blocks Alsa, then one last
thing to try would be switching to Jack. this will absolutely do what
you want but it will only do it for Jack applications. I run only Jack
apps here so it works for me but I havn't tried the Wine Jack driver
in quite a while and haven't much info to give you there.

   Maybe I should install a game or two and see how things go... ;-)
(No time unfortunately!)


On 4/23/05, Joachim von Thadden <thadden at web.de> wrote:
> Am Fr, Apr 22, 2005 at 11:59:28 +0200 schrieb Sylvain Petreolle:
> > Just configure Wine for ALSA use :
> > in $HOME/.wine/config
> > [WinMM]
> > "Drivers" = "winealsa.drv"
> > [ALSA]
> > "PlaybackDevice" = "hw"
> >
> > and load the needed oss emulation modules :
> > snd_pcm_oss
> > snd_seq_oss
> > snd_mixer_oss
> No, you are miying things up: If you are using the winealsa driver you
> don't need oss emulation (assumed that you hano other programs needing
> oss emulation). But my problem is, that I don't want to use the
> winealsa driver as it is not as far implemented as the wineoss driver.
> But *if* I use the wineoss driver and my Wine app is accessing the
> device it is locked for all other programs. That' not really a problem.
> But if another ALSA program is already accessing the device it is
> locked for the WIne program. Only different ALSA programs can access
> the device together via dmix.
> Regards
>         Joachim von Thadden
> --
> "Never touch a running system! Never run a touching system?
>           Never run a touchy system!!!"
> _______________________________________________
> wine-users mailing list
> wine-users at winehq.org
> http://www.winehq.org/mailman/listinfo/wine-users

More information about the wine-users mailing list