http://bugs.winehq.org/show_bug.cgi?id=22880
--- Comment #15 from Raymond superquad.vortex2@gmail.com 2010-06-12 18:47:48 --- (In reply to comment #14)
I believe the actual sound HW (ens1371, AC'97 etc.) does not matter to Wine. These days, most Linux systems allow multiple opens and perform mixing (ALSA's dmix, OSS4 ...) when needed.
are you using dmix or pulseaudio ?
In OSS/Free ,
/dev/dsp is alsa 's hw:0,0 /dev/adsp is alsa 's hw:0,1
aplay -l **** List of PLAYBACK Hardware Devices **** card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: AudioPCI [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1] Subdevices: 1/1 Subdevice #0: subdevice #0
Note that there may be various reasons why music and sound do not mix, some external to Wine. On a Ubuntu system with PulseAudio, I've had situations where Timitidy grabbed the ALSA audio output (first come, first served), therefore no other app could produce sound any more, not /usr/bin/speaker-test, nor Wine's sound, nor any PulseAudio app.
It really depend on your sound card support hardware mixing or not
did you configured timitity to use dmix ?
dmix is hardcoded to use subdevice 0
even your hardware mixing sound card which has multiple subdevice , dmix can only use subdevice 0
if you did not specify subdevice (e.g. hw:0,0) , alsa-lib use default subdevice value -1 which mean any available subdevice ( hw:0,0,-1)
ens1371 has 2 playback devices , hw:0,0 and hw:0,1