Bug 209902 - Add VU meters to mixer dialog
Summary: Add VU meters to mixer dialog
Status: RESOLVED INTENTIONAL
Alias: None
Product: kmix
Classification: Applications
Component: Backend: Pulseaudio (show other bugs)
Version: unspecified
Platform: Gentoo Packages Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Colin Guthrie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-08 20:01 UTC by BRULE Herman
Modified: 2013-07-21 10:00 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description BRULE Herman 2009-10-08 20:01:05 UTC
Version:            (using KDE 4.3.1)
Installed from:    Gentoo Packages

Please add little bar for the the current value of the input and/or output, like:
http://2.bp.blogspot.com/_fq9xRZFHXcc/Sd8MfNj4kaI/AAAAAAAAD3U/olbeK8pNwLI/s400/base+de+gerance+multi+mixer+windows+seven+max.PNG
http://windowsvj.com/wpblog/wp-content/uploads/2009/09/volume-mixer-win7.jpg
For show the activities of the input/output channel.
Comment 1 Christian Esken 2010-08-01 00:50:58 UTC
My understanding is that this is not possible in general.
But it should be possible with Pulseaudio, and I think it should only be done for Pulseaudio.

Thus I'll assign this request to the Pulseaudio component.
Comment 2 Alexey Shildyakov 2010-08-31 10:33:46 UTC
Now (with KDE 4.5.0) when KMix support Pulseaudio it have been done.
But I want to change it: show levels for all activities when press on tray icon with scrollbar if it needed. Not only main, but for all activities.
Comment 3 yo 2013-02-16 19:46:34 UTC
(In reply to comment #2)
> Now (with KDE 4.5.0) when KMix support Pulseaudio it have been done.
> But I want to change it: show levels for all activities when press on tray
> icon with scrollbar if it needed. Not only main, but for all activities.

One step at a time, no? :)
Comment 4 Christian Esken 2013-02-22 22:49:01 UTC
I think it is not possible what BRULE Herman has asked for in the screenshot, or Alexey asks for ("levels for all activities"). It is not supported by any Linux based sound system known to me. PulseAudio has some kind of overall meter for input, but not for individual channels. Even doing this has many obstacles (there is not even a Slider available to display the meter value), and there are simply no capacities for doing it.
Well, should some volunteer find out a solution, please let me know and I will aid in integrating it.  For now I will close the bug report as I cannot do it.
Comment 5 yo 2013-07-20 12:33:32 UTC
(In reply to comment #4)
> I think it is not possible what BRULE Herman has asked for in the
> screenshot, or Alexey asks for ("levels for all activities"). It is not
> supported by any Linux based sound system known to me. PulseAudio has some
> kind of overall meter for input, but not for individual channels. Even doing
> this has many obstacles (there is not even a Slider available to display the
> meter value), and there are simply no capacities for doing it.
> Well, should some volunteer find out a solution, please let me know and I
> will aid in integrating it.  For now I will close the bug report as I cannot
> do it.

The only way I can think of at the top of my head would be to determine the percentage of the current dB output as opposed to the maximum possible dB output for a specific channel. The logic would vary across sound stacks and probably would require something to be done upstream (if such doesn't exist already).

Again, one solution that came to mind.
Comment 6 Colin Guthrie 2013-07-21 10:00:15 UTC
(In reply to comment #4)
> I think it is not possible what BRULE Herman has asked for in the
> screenshot, or Alexey asks for ("levels for all activities"). It is not
> supported by any Linux based sound system known to me. PulseAudio has some
> kind of overall meter for input, but not for individual channels. 

Not actually true. With PA you can get a VU meter for the overall sink or source or for any individual stream. You can also get VU values for each channel too. Ultimately the VU meters are generated by connecting to the sources (or the monitor sources for sinks) and checking the levels. In pavucontrol it uses a PEAKs resampler (via the PA_STREAM_PEAK_DETECT flag) which is not great for fidelity but fine for showing levels. We also restrict it to just one channel to save resources, but there is no reason not to do it multi-channel.

So from the "information needed" perspective, it's all there. Your other points about how it would be difficult to factor in remain true of course :)