http://bugs.winehq.org/show_bug.cgi?id=28683
Bug #: 28683 Summary: Crysis: no sound with wine 1.3.30 Product: Wine Version: 1.3.29 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mmdevapi AssignedTo: wine-bugs@winehq.org ReportedBy: alessandro_pezzoni@lavabit.com CC: aeikum@codeweavers.com Classification: Unclassified Regression SHA1: e786998daff4ad49521a4c9c39c172ddcdcad82a
Created attachment 36861 --> http://bugs.winehq.org/attachment.cgi?id=36861 +mmdevapi log (wine compiled from rev e786998daff4ad49521a4c9c39c172ddcdcad82a)
Crysis doesn't play any sound with wine 1.3.30, but it works fine with wine 1.3.29. I don't seem to have any other sound issue with wine 1.3.30 (I tried the winecfg sound test, Assassin's Creed, and Guilty Gear XX).
I tracked the regression to this commit:
commit e786998daff4ad49521a4c9c39c172ddcdcad82a Author: Andrew Eikum aeikum@codeweavers.com Date: Tue Sep 27 08:51:07 2011 -0500
dsound: Reimplement rendering devices on mmdevapi.
:040000 040000 53407fdfd9131c99d768c90eeda5dadc66a63abb af37caec04c5e8abedfd395abcd88a16e71a3b85 M dlls
Test system: OS: Arch Linux (kernel 3.0.6) Sound: alsa-lib 1.0.24.1
I'm attaching a +mmdevapi log (wine compiled from the revision mentioned above).
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #1 from Andrew Eikum aeikum@codeweavers.com 2011-10-12 14:43:05 CDT --- Thanks for reporting. Can you attach a log with the channels requested at http://wiki.winehq.org/Sound? A log from the latest version of Wine that you can test is preferred (from latest Git is best, 1.3.30 is fine if you can't build from Git).
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #2 from Alessandro Pezzoni alessandro_pezzoni@lavabit.com 2011-10-12 16:24:32 CDT --- Created attachment 36868 --> http://bugs.winehq.org/attachment.cgi?id=36868 +tid,+mmdevapi,+winmm,+midi,+dsound,+dmusic,+oss,+alsa,+coreaudio wine-1.3.30-45-ga843ace log
Here is the log from the current git head, as you asked. I had to compress it to attach it.
http://bugs.winehq.org/show_bug.cgi?id=28683
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.29 |1.3.30 Summary|Crysis: no sound with wine |Crysis: no sound |1.3.30 |
http://bugs.winehq.org/show_bug.cgi?id=28683
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #3 from Andrew Eikum aeikum@codeweavers.com 2012-01-25 11:41:57 CST --- Hi Alessandro, is this still a problem in Wine 1.3.37? Your log contains lots of underruns, and we've had some patches to the ALSA driver to address that specifically.
http://bugs.winehq.org/show_bug.cgi?id=28683
Alessandro Pezzoni alessandro_pezzoni@lavabit.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #36861|0 |1 is obsolete| | Attachment #36868|0 |1 is obsolete| |
--- Comment #4 from Alessandro Pezzoni alessandro_pezzoni@lavabit.com 2012-01-25 14:00:38 CST --- Created attachment 38553 --> http://bugs.winehq.org/attachment.cgi?id=38553 +tid,+mmdevapi,+winmm,+midi,+dsound,+dmusic,+oss,+alsa,+coreaudio wine 1.3.37 log
Hello Andrew, sadly this issue is still present in wine 1.3.37. I'm attaching a new log.
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #5 from Andrew Eikum aeikum@codeweavers.com 2012-01-25 14:14:18 CST --- Thanks for the new log.
It looks to me like audio is working well in that log.
It's possible we've got the wrong device. Dsound is opening "plughw:0,1" which is named "HDA Intel PCH - ALC892 Digital". This usually maps to some optical connector (perhaps even HDMI? not sure). It's not clear why Crysis is selecting that device. Perhaps it's leftover from a previous version of Wine? Have you tried this in a fresh wineprefix?
You can test if that's the correct device with this command: $ aplay -D "plughw:0,1" some_wav_file.wav
Some information about what device you /expect/ to be using would be the next step.
http://bugs.winehq.org/show_bug.cgi?id=28683
Alessandro Pezzoni alessandro_pezzoni@lavabit.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #38553|0 |1 is obsolete| |
--- Comment #6 from Alessandro Pezzoni alessandro_pezzoni@lavabit.com 2012-01-25 16:42:48 CST --- Created attachment 38555 --> http://bugs.winehq.org/attachment.cgi?id=38555 +tid,+mmdevapi,+winmm,+midi,+dsound,+dmusic,+oss,+alsa,+coreaudio wine 1.3.37 log, plughw:0,0 not in useplughw:0,0plughw:0,0
The device I am expecting is "plughw:0,0", which is named "HDA Intel PCH - ALC892 Analog". It seems that the device was in use by another program (namely firefox), even if other programs could play sound just fine (I couldn't access the device directly with "aplay -D 'plughw:0,0' file.wav", though). I'm attaching a new log where the device can be accessed (or at least there are no 'The device "plughw:0,0" failed to open' messages), but I still don't get any sound from Crysis.
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #7 from Andrew Eikum aeikum@codeweavers.com 2012-01-26 08:34:20 CST --- Okay, so this is definitely a wrong device problem.
Looking at your new log, Crysis calls DirectSoundEnumerate which returns all of the devices:
0009:trace:dsound:enumerate_mmdevices Calling back with NULL (L"Primary Sound Driver") 0009:trace:dsound:send_device Calling back with {2febaa6a-8001-4792-9d8b-6af340cf0087} (L"HDA Intel PCH - ALC892 Digital") 0009:trace:dsound:send_device Calling back with {465fa93a-66ce-4cd2-b97c-c5dfe0179538} (L"default") 0009:trace:dsound:send_device Calling back with {a214ce73-cc51-4308-80fa-912ddca7ecfb} (L"HDA NVidia - HDMI 0") 0009:trace:dsound:send_device Calling back with {d23e4ba2-ba3f-4890-bf6a-a5c66caded76} (L"HDA Intel PCH - ALC892 Analog")
It's not clear whether Crysis stores the device ID, or if it just chooses the first non-NULL device from the Enumerate callback. Either way, Crysis chooses Digital (notice the same GUID):
0009:trace:dsound:DirectSoundCreate8 ({2febaa6a-8001-4792-9d8b-6af340cf0087},0x3e4ec48,(nil)) 0009:trace:alsa:AUDDRV_GetAudioEndpoint "plughw:0,1" 0x69b1970 0 0x69b22a4
The order of enumeration is significant. Dsound always sends the NULL device first. That is followed immediately by the default device, which appears to be the Digital device in your case. Using the ALSA driver, "default" is _always_ the default device unless you have explicitly overridden it in winecfg or regedit. What does the Default Output Device entry in the winecfg Audio tab say for you? If it's set to something other than System Default, try using System Default and see how Crysis behaves.
If that doesn't work, it's possible Crysis is storing the Digital device ID and requesting that explicitly. Try installing into a clean WINEPREFIX and see what happens. E.g.:
$ WINEPREFIX=$HOME/tmp_pfx wine winecfg $ WINEPREFIX=$HOME/tmp_pfx wine CrysisInstaller.exe etc...
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #8 from Alessandro Pezzoni alessandro_pezzoni@lavabit.com 2012-01-26 10:49:45 CST --- Yes, now it is working. Sorry for the inconvenience.
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #9 from Andrew Eikum aeikum@codeweavers.com 2012-01-26 10:59:36 CST --- I'm glad to hear it! So I can give this the right Closed status, can you tell me whether choosing the right device in winecfg fixed it, or did you have to reinstall in a clean prefix?
http://bugs.winehq.org/show_bug.cgi?id=28683
--- Comment #10 from Alessandro Pezzoni alessandro_pezzoni@lavabit.com 2012-01-27 00:45:11 CST --- Choosing the right device fixed it.
http://bugs.winehq.org/show_bug.cgi?id=28683
Andrew Eikum aeikum@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #11 from Andrew Eikum aeikum@codeweavers.com 2012-01-27 08:55:40 CST --- Great, thanks for the info!
User config problem, closing Invalid.
http://bugs.winehq.org/show_bug.cgi?id=28683
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Austin English austinenglish@gmail.com 2012-01-28 14:04:16 CST --- Closing.