Hello,
After upgrading wine from 1.3.27 -> 1.3.28 I found I got no sound when a different application (which uses the sound) is running in the background.
Workaround for me is to kill all sound, load up the wine application and alt+tab back to start a non wine application.
It's not optimal but a workaround.
But I would like to understand why this is happening. Why wine could somehow not make a connection to the audio server. And visa versa it works.
For relevance, I use opensuse tumbleweed with pulseaudio enabled.
wine 1.3.28 sound issues
wine 1.3.28 sound issues
On Sun, Sep 11, 2011 at 8:57 AM, mrmarcus <[email protected]> wrote:
anymore or something. It's strange. If I run winecfg, and click test
sound, it used to create a alsa-plugin in pulse, it doesn't anymore. Now
when I run a game it does create a wine-preloader plugin, but not
alsa-plugin[wine-preloader], not sure how it works tbh.
My fix from the 70 posts of testing still seems to work for me. It seems
that pulse 0.9.23 somehow has new API's, bug fixes, that allows it and alsa
to work better together. The problem is 0.9.23 for Ubuntu won't be
backported to 11.04, since the new API's don't work nice I guess or
something (if you read the bug report they say why)(and I have no clue what
version is in OpenSuse tbh). I'd use 0.9.23 except the Gnome Sound Applet
doesn't work with it, so I can't control sound volume easily, so I start
0.9.23, get sound from a pulse app running, kill 0.9.23 and start up the
built in sound, then the sound applet works, but it seems to use 0.9.23 so
now wine/pulse/alsa all play nice.
Or as wine recommends just get rid of Pulse all together, and use alsa sound
applets to control sound. I just personally like Pulse for everythign but
wine.
--
Sincerely,
MacNean C. Tyrrell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... hment.html>
Yes for some reason wine with alsa isn't creating a alsa-plugin in pulseHello,
After upgrading wine from 1.3.27 -> 1.3.28 I found I got no sound when a
different application (which uses the sound) is running in the background.
Workaround for me is to kill all sound, load up the wine application and
alt+tab back to start a non wine application.
It's not optimal but a workaround.
But I would like to understand why this is happening. Why wine could
somehow not make a connection to the audio server. And visa versa it works.
For relevance, I use opensuse tumbleweed with pulseaudio enabled.
anymore or something. It's strange. If I run winecfg, and click test
sound, it used to create a alsa-plugin in pulse, it doesn't anymore. Now
when I run a game it does create a wine-preloader plugin, but not
alsa-plugin[wine-preloader], not sure how it works tbh.
My fix from the 70 posts of testing still seems to work for me. It seems
that pulse 0.9.23 somehow has new API's, bug fixes, that allows it and alsa
to work better together. The problem is 0.9.23 for Ubuntu won't be
backported to 11.04, since the new API's don't work nice I guess or
something (if you read the bug report they say why)(and I have no clue what
version is in OpenSuse tbh). I'd use 0.9.23 except the Gnome Sound Applet
doesn't work with it, so I can't control sound volume easily, so I start
0.9.23, get sound from a pulse app running, kill 0.9.23 and start up the
built in sound, then the sound applet works, but it seems to use 0.9.23 so
now wine/pulse/alsa all play nice.
Or as wine recommends just get rid of Pulse all together, and use alsa sound
applets to control sound. I just personally like Pulse for everythign but
wine.
--
Sincerely,
MacNean C. Tyrrell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... hment.html>
thank you for the reply Dardack,
It seems logic and odd together.
Although my knowledge of linux isn't that great I do understand that there is an issue going on with the alsa-plugin for pulse which is somehow not loaded correctly when a different application (which uses the sound system) is already actived.
I use the pulseudio version 0.9.23 in openSUSE.
And till this issue is fixed (or noticed by the devs) I will use the workaround by starting the wine app first then whatever i need.
Regards,
It seems logic and odd together.
Although my knowledge of linux isn't that great I do understand that there is an issue going on with the alsa-plugin for pulse which is somehow not loaded correctly when a different application (which uses the sound system) is already actived.
I use the pulseudio version 0.9.23 in openSUSE.
And till this issue is fixed (or noticed by the devs) I will use the workaround by starting the wine app first then whatever i need.
Regards,
wine 1.3.28 sound issues
Well with 0.9.23 i believe you can do my solution, which is create a
.asoundrc that creates a dmix/dsnoop device, duplexes them, then edit
/etc/pulse/default.pa to have pulse use that duplex device, then have wine
use that duplex device directly. This way alsa things (wine/chrome flash)
use alsa directly, and pulse goes through alsa, so everything is happy.
On Mon, Sep 12, 2011 at 3:22 AM, mrmarcus <[email protected]> wrote:
Sincerely,
MacNean C. Tyrrell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... hment.html>
.asoundrc that creates a dmix/dsnoop device, duplexes them, then edit
/etc/pulse/default.pa to have pulse use that duplex device, then have wine
use that duplex device directly. This way alsa things (wine/chrome flash)
use alsa directly, and pulse goes through alsa, so everything is happy.
On Mon, Sep 12, 2011 at 3:22 AM, mrmarcus <[email protected]> wrote:
--thank you for the reply Dardack,
It seems logic and odd together.
Although my knowledge of linux isn't that great I do understand that there
is an issue going on with the alsa-plugin for pulse which is somehow not
loaded correctly when a different application (which uses the sound system)
is already actived.
I use the pulseudio version 0.9.23 in openSUSE.
And till this issue is fixed (or noticed by the devs) I will use the
workaround by starting the wine app first then whatever i need.
Regards,
Sincerely,
MacNean C. Tyrrell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... hment.html>
