http://bugs.winehq.org/show_bug.cgi?id=34183
Bug #: 34183 Summary: alsa driver ignores output device selection Product: Wine Version: 1.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winealsa.drv AssignedTo: wine-bugs@winehq.org ReportedBy: vallesroc@gmail.com Classification: Unclassified
Created attachment 45471 --> http://bugs.winehq.org/attachment.cgi?id=45471 My ~/.asoundrc setup
I own a soundcard (emu20k2) that alsa does hxmix with (no dmix involved). I don't run pulseaudio.
I use a 4.0 (Front l/r, back l/r) set of speakers and I like front input to be duplicated on the back, and to achieve that I use the attached .asoundrc, with a pcm.ch40dup device that does just this.
Now, with ogg123 I'd do: ogg123 -d alsa -o dev:ch40dup stereosong.ogg
And it'd play through the 4 speakers.
Now, I tried to get it to work with winealsa.drv:
1. It doesn't enumerate it, so I can't select it as output through the winecfg panel. Workaround: I can force winealsa.drv to be aware of it through the ALSAOutputDevices registry key (I put just "ch40dup" there) as described in http://wiki.winehq.org/UsefulRegistryKeys
2. I select it as output and voice output on winecfg. Click test. The test sound only plays through the front speakers, so it's failing to really use that output and failing back to "default"... silently, without any output indicating any problem on the terminal it was launched from.
3. Afterwards, I try foobar2000. Audio still outputs from front only. Conveniently, foobar2000 does support selecting an output device. ch40dup is listed. If I try to force playing through it, foobar2000 crashes. Stack trace of its own builtin crash report tool reports the crash happens inside dsound.
http://bugs.winehq.org/show_bug.cgi?id=34183
--- Comment #1 from Roc Vallès Domènech vallesroc@gmail.com 2013-07-31 21:27:21 CDT --- Correction for step 3:
If I leave ch40dup set as the default in winecfg, foobar2000 also crashes when letting it use the default output. Did just not save the selection in winecfg in my prior test.
http://bugs.winehq.org/show_bug.cgi?id=34183
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source Severity|major |normal
https://bugs.winehq.org/show_bug.cgi?id=34183
--- Comment #2 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=34183
--- Comment #3 from Roc Vallès Domènech vallesroc@gmail.com --- Don't have the hardware to test this currently. Feel free to close for now... it can be reopened eventually if someone needs it be.
https://bugs.winehq.org/show_bug.cgi?id=34183
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net, | |super_man@post.com
https://bugs.winehq.org/show_bug.cgi?id=34183
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #4 from Anastasius Focht focht@gmx.net --- Hello folks,
resolving 'ABANDONED' for now. Reopen when you can reproduce with original hardware setup and recent Wine version.
Regards
https://bugs.winehq.org/show_bug.cgi?id=34183
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Austin English austinenglish@gmail.com --- Closing.