[pulseaudio-discuss] Make discoverable PA network sound devices available locally results in huge network traffic

Maarten Bosmans mkbosmans at gmail.com
Thu Jan 20 13:27:08 PST 2011

2011/1/20 Brian J. Murrell <brian at interlinx.bc.ca>:
> Maarten Bosmans <mkbosmans <at> gmail.com> writes:
>> Well, that's the static configuration script loaded at the start of
>> the daemon. As noted in the comment just above that line, ticking the
>> box in paprefs can also load this module.
> Oh, well, there you go then.  :-)
>> If you are able to stream audio over the network, obviously some
>> modules facilitating that are loaded somehow.
> Indeed.
>> Can you provide the
>> output of "pactl list" on both machines (clearly indicating which is
>> which)?
> laptop (source of audio):
>  http://brian.interlinx.bc.ca/brian-laptop-pactl_list.txt
> workstation (destination of audio):
>  http://brian.interlinx.bc.ca/pc-pactl_list.txt

It looks like both are from your PC. You probably SSH'ed into your
laptop with the -X option. The pactl command then finds the clients
pulse server over the network via the DISPLAY variable. You can
circumvent this by saying:
PULSE_SERVER=localhost pactl list

>> Most helpful would be the output when there is no music playing, but
>> you are seeing high network utilisation.
> That is the case in those two lists.
>> with pactl list, look for a loaded rtp module.
> They both appear to have module-rtp-recv loaded.
>> That most certainly looks like raw audio bitrate.
> Indeed, but what?
> b.
> _______________________________________________
> pulseaudio-discuss mailing list
> pulseaudio-discuss at mail.0pointer.de
> https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss

More information about the pulseaudio-discuss mailing list