Volume meter

[palinek]

fixes #75

[tsujan]

I don't think the animation saves a tangible amount of CPU time. Moreover, it seems much better to me when the value shown by the progressbar is that of the moment -- quick ups and downs are informative (although the animation is only for ups downs).

[palinek]

Moreover, it seems much better to me when the value shown by the progressbar is that of the moment

It is not so even in current master implementation:

    if (lastPeak >= DECAY_STEP)
        if (v < lastPeak - DECAY_STEP)
            v = lastPeak - DECAY_STEP;

[tsujan]

It is not so even in current master implementation:

The current master is better. I first compiled, then saw that a piano concerto "looked" like a violin concerto (contrary to my installed pavucontrol-qt), and only then, saw the diff.

[RJVB]

I don't think the animation saves a tangible amount of CPU time.

AFAICT the pulseaudio daemon itself burns at least as much CPU as pavucontrol-qt when showing the VU meters.

This is the main reason why I rarely leave the application open, while I'd actually prefer that when changing audio devices ("sinks").

It would be useful to have the Show volume meters checkbox in a new frame under the tabbox widget, so it is accessible from all tabs.