Summary: | media-sound/pulseaudio volume adjustments cause hissing / glitching | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Xepher <anarchy> |
Component: | Current packages | Assignee: | Gentoo Sound Team <sound> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chewi, ford_prefect |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Xepher
2010-08-08 06:16:46 UTC
You're not alone. I'm seeing this with Realtek-based hda-intel onboard sound. How many channels do you guys have in your setup? There were some fixes in PA recently for software volume scaling with a non-standard number of channels. 6, as it 5.1. But I've stopped seeing this issue since getting a different card. (In reply to comment #2) > How many channels do you guys have in your setup? There were some fixes in PA > recently for software volume scaling with a non-standard number of channels. > 5.1 here as well. As the sucker is part of my motherboard, I'd rather not replace it. :-) I'm not sure that software scaling has anything to do with it though, since (as I mentioned above) changing the hardware (alsa PCM) level fixes it. Of course, on modern systems, I'm never quite sure what's really "hardware" vs. "software" anymore. I suspect that this patch from stable-queue should fix your problems: http://git.0pointer.de/?p=pulseaudio.git;a=commit;h=a8d76e99ff0b13f424b44433fb169df6735a5842 There should be a new release containing this patch soon. In the mean time, an easy way to check if this fixes the problem is to set the environment variable PULSE_NO_SIMD=1 before (re)starting PulseAudio. PULSE_NO_SIMD=1 does seem to fix it. Woot! I can deal with that as a workaround for now. Hopefully the next release doesn't take another year. :-) (In reply to comment #6) > PULSE_NO_SIMD=1 does seem to fix it. Woot! I can deal with that as a workaround > for now. Hopefully the next release doesn't take another year. :-) Should be a lot sooner than that :) Should be fixed with 0.9.22 which is now in CVS. |