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...