[Bug 39744] No sound with winepulse.drv in multiple applications when using Debian Wine packages (PULSE_LATENCY_MSEC set to 60 in wine wrapper script)
wine-bugs at winehq.org
wine-bugs at winehq.org
Tue Dec 8 16:27:12 CST 2015
https://bugs.winehq.org/show_bug.cgi?id=39744
Sebastian Lackner <sebastian at fds-team.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Version|unspecified |1.7.55
Summary|No sound in Applications |No sound with winepulse.drv
|after Update from 1.7 pre |in multiple applications
|winepulse.drv to 1.7.55 or |when using Debian Wine
|1.8 after the pulse update |packages
| |(PULSE_LATENCY_MSEC set to
| |60 in wine wrapper script)
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #12 from Sebastian Lackner <sebastian at fds-team.de> ---
I was already aware that Debian applies invalid/unnecessary patches, provides
unnecessary and broken wrapper scripts, and so on ... - but the fact that they
also sets Pulseaudio specific environment variables is new to me.
(In reply to Andrew Eikum from comment #9)
> It's possible that winepulse should buffer locally, too, to account for
> setups like yours. On the other hand, maybe users are expected to let PA do
> its latency calculations itself, and so testing with that environment
> variable set is invalid. I don't know.
I would say, lets keep this bug report open as an enhancement, unless we have
evidence that it also occurs in a setup without environment variable overrides.
We probably should promote the WARN() to a winediag message though, to catch
such invalid user setups a bit easier. Do you agree?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list