Bug 89796

Summary: Popping sound on Volume change when more than one stream is active
Product: PulseAudio Reporter: andros
Component: coreAssignee: pulseaudio-bugs
Status: RESOLVED MOVED QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: lennart
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description andros 2015-03-27 20:26:59 UTC 
There is an popping/clicking sound on volume changing, every time when there is more than one application active.

Example:
Runing KDE 
- You got Audacious playing music
- System Notifications Sounds are on

Result:
Every time you change the volume of one of: Notification Sound, or Audacious, there is is a popping noise.

Workaround:
Mute System Notifications Sound, there is no noise when chaining volume of Audacious.

Example2:
- You got Audacious playing music
- You have mumble running (no speaking just running idle)

Result:
There is always a noise changing volume of Mumble or Audacious!

Workaround:
Have only one app running at a time!

Because Mumble streams even if it is idle, it counts as second stream here. So there will be this noise every single time you have more then one stream.

Searching on Google about this got me thousands of site who say, just have one stream always and everything is fine. 
But this is no solution!
Comment 1 Tanu Kaskinen 2015-03-31 08:17:36 UTC 
Does setting "flat-volumes = no" in ~/.config/pulse/daemon.conf help?
Comment 2 andros 2015-03-31 11:32:53 UTC 
Yes, you could say it is gone. 
By the way, this is Gentoo Kernel 3.19.2 with pulseaudio 5.0-r4
Comment 3 GitLab Migration User 2018-07-30 10:34:08 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/508.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.