Bug 102462 - pavucontrol - volume levels always zero
Summary: pavucontrol - volume levels always zero
Status: RESOLVED NOTABUG
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: pavucontrol (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-28 20:40 UTC by quantumphoton007
Modified: 2017-08-29 09:45 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
The sound level bar that always stays zero (8.48 KB, image/png)
2017-08-28 20:40 UTC, quantumphoton007
Details

Description quantumphoton007 2017-08-28 20:40:54 UTC
Created attachment 133854 [details]
The sound level bar that always stays zero

pavucontrol's volume levels are always zero, no matter how loud my audio playback is. It is zero in both playback and output-devices tabs.

In an attempt to debug, I cloned the latest version from git, printed the values to see where the issue is.

> v = ((const float*)data)[length / sizeof(float) - 1];
> fprintf(stderr, "%lf\n", v);

in mainwindow.cc

The output always stays zero. The only exception is the input devices tab, where the sound levels work as expected for my microphone. When I print the values from input devices section, the value is some non-zero float.
Comment 1 quantumphoton007 2017-08-28 20:50:05 UTC
I looked for all values returned by `pa_stream_set_read_callback` that are non zero (inside MainWindow::createMonitorStreamForSource).

Every value that is in the array turns out to be 0.

Could this be a bug on pulseaudio's implementation of `pa_stream_set_read_callback`? 

I do remember the sound level working, not long ago.
Comment 2 quantumphoton007 2017-08-29 09:45:12 UTC
My bad. The monitor of built-in analog stereo was muted in pavucontrol. Unmuting it fixed it.

Sorry for the trouble.


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.