Bug 96922

Summary: "Simultaneous output" is too low
Product: PulseAudio Reporter: Gabriel Corona <gabriel.corona>
Component: coreAssignee: pulseaudio-bugs
Status: RESOLVED MOVED QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: lennart
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: pactl list

Description Gabriel Corona 2016-07-13 20:54:26 UTC
Created attachment 125060 [details]
pactl list

Hi,

I've updated Pulseaudio from 8.0-2+b2 to 9.0-1.1 (Debian packages) and with the new version the sound is way too low when using when using the "Simultaneous output". I have to put all the sliders at 150% as well as my speaker at near max to get some sound (and then I get a lot of noise).

It used to work fine before the update. Switching to "Builtin Audio Analog Stereo" gives me a much louder/normal audio output.

I attached the output of "pactl list".

Cheers.
Comment 1 Gabriel Corona 2016-07-13 21:29:42 UTC
It turns out I have "Virtual Streams" in pavucontrol. The volume of those was too low. Moving them back to 100% fixes the problem. I don't know why (and if) the pulseaudio update changed something about this.
Comment 2 Tanu Kaskinen 2016-07-13 21:56:09 UTC
module-stream-restore.id for the virtual streams is "sink-input-by-media-role:filter", which probably means that if you set the volume for any virtual stream, it will be later restored for all virtual streams. I don't know how relevant this is to your problem, but I think this doesn't make sense in general, so there's at least something to fix.
Comment 3 GitLab Migration User 2018-07-30 10:22:35 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/384.

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.