[Bug 33100] New: ALSA Audio playback in WINE locks up ALSA capture by other applications

http://bugs.winehq.org/show_bug.cgi?id=33100

Bug #: 33100
           Summary: ALSA Audio playback in WINE locks up ALSA capture by
                    other applications
           Product: Wine
           Version: 1.5.25
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: winealsa.drv
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

Hi there,

when trying to record sound (e.g. using arecord) played by some 
application running on WINE (e.g. vlc.exe) via ALSA, and if the 
recording application is launched *before* the playback application, 
recording stops immediately when playback starts, and after a while ALSA 
reports an "Input/output error". This does not happen with native 
playback applications, e.g. the Linux version of vlc.

Funny enough, if recordings starts *after* playback has begun, 
everything works fine.

How to reproduce:

1. In a terminal, issue

sudo alsactl restore; arecord -D default -f dat -v -V stereo test.wav

2. In another terminal, launch vlc.exe by issuing something like

WINEPREFIX=/path/to/prefix wine /path/to/vlc.exe /path/to/some/audiofile

3. Wait for a few seconds... and see arecord complaining:

arecord: pcm_read:1801: read error: Input/output error

4. Re-launch arecrod:

sudo alsactl restore; arecord -D default -f dat -v -V stereo test.wav

5. Watch arecord recording happily ever after.

I initially suspected WINE to somehow force access to my soundcard's 
capture device (A SB Live, which seems not to be dsnoop'd by default), 
but after creating a dsnoop'd device (which did allow for multiple 
simultaneous recordings with arecord when playing back audio with 
Linux's vlc) and teaching WINE to actually use it, the problem 
unfortunately remained.

Best regards --

Torsten

P.S. If filed this bug with Debian's wine-unstable-alsa package some two months
ago already, but since there hasn't been a single reply up to now and since the
problem still remains with 1.5.25 (Debian is still at 1.5.6), I found it
appropriate to directly re-file this report at WINE's bug tracking system.