© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
I'm hearing some very conflicting reports here, to tell the truth... It's good to be hearing from a set of people for whom the winepulse patchset hasn't fixed the problem. It's odd, though, that we're seeing such different results. I'm starting to wonder if there might be multiple underlying issues here.
As I've reported, I'm currently running Lucid x86-64, and was previously running Karmic x86-64. I was previously able to duplicate sound-stuttering issues in various games, when running Wine through the ALSA interface of PulseAudio under Karmic, using Hardware Acceleration: Full at all times. Running Lucid essentially out of the box, using the default wine1.2 package (1.1.38-0ubuntu1) and an unchanged PulseAudio, I see no such problems, and cannot duplicate problems in any of the games that previously showed them, or in foobar2k. I haven't yet had the chance to test Ventrilo as previously requested.
Ernst, I'm confused that you say that you haven't tested with Wine 1.1.38 yet, since it's currently the main Wine package in the Lucid repositories, and has been for at least a week... Have you upgraded to Lucid, or no? I was seeing persistent problems under Karmic, and no longer see any under Lucid, including in foobar2k - absent further data, I've been assuming that the new version of PulseAudio in Lucid has fixed the issue for me.
Scott, thanks very much for responding to this - I appreciate it. This is a stupid question - but when you tested the winepulse packages, you did remember to switch the option in winecfg to select the PulseAudio driver, rather than the ALSA driver? I only ask because the behavior you're talking about sounds awfully like my own testing results while running through the ALSA driver in a winepulse-updated Wine - and winepulse adds a new driver, and doesn't fix the old one at all. I'm certain you do realize this, but everyone slips up occasionally, so I have to ask.
I do agree that PulseAudio appears to have played the major role in this bug, particularly since it should have been the only relevant component updated when I moved to Lucid... besides, I've found many records of PulseAudio behaving in slightly odd ways through the ALSA input, causing persistent problems.