2010/7/22 Chris cpollock@embarqmail.com

On Thu, 2010-07-22 at 11:03 +0800, Raymond Yau wrote:

...

2010/7/22 Chris cpollock@embarqmail.com

    >
    > AFAIK, the most buggy PA client is pavucontrol because
    >
    > 1) it has those vumeters which need to get audio data from
    the
    > playback and capture devices of the sound card ,
    > 2) when you move the slider to left ( over 100%) and this
    force PA to
    > provide software gain
    >
    > You should notice that the new gnome-volume-control is
    actually a
    > simplified version of pavucontrol


    Hmm, I just pulled up PulseAudio Volume Control and see no
    vumeters, I
    can't figure out though why the drive thrashing at various
    times whether
    I have a stream playing or not.

Did you click the input device tab page of the gnome volume control ?

The vumeter is "Input level" above the volume control slider ?

You should noticed that the following message appear in the pulseaudio log

I: source-output.c : Created output 0 "Peak detect" on alsa_input

I.source-output:c application.id = "org.gnome.volume.control" I.source-output:c media.name = "Peak detect" I.source-output:c application.name = "GNOME Volume control dialog"

when you using mplayer to play music and open pavucontrol to

pavucontrol sometime abort suddenly when you aborte mplayer but this is not 100% reproducible

pavucontrol ** ( pavucontrol:3232) : DEBUG: failed to initialize device manager extension: No such extension ** (pavucontrol:3056) : DEBUG: Ignoring sink-input due to it being designated as an event and thuse handled by the event widget

The point is after the complete intergration of pulseaudio in to the system ( libcanberra, mixer-applet , ... )

I think "pulseaudio -k; pulseaudio -vvvv" is no longer the correct way to debug since there are lots of PA clients running at the desktop

You have to ask the mandriva maintainer how to increase the debug level of PA server and have to perform a logout/login to debug the PA server

Thanks Raymond, so I should contact Colin and go from there? I'm not sure what to even tell him though. I thank you for all your help.

Chris

There are over 15 PA clients running when you are using gnome desktop

running "pulseaudio -k " to shutdown PA server , this kill all the PA clients restart PA server by "pulseaudio -vvvv" , only one or two PA clients (e.g. consolekit, .. ) can connected back to PA server

This command "pulseaudio -k;pulseaudio -vvvv" cannot provide a normal environment to debug PA server since most of PA clients are killed