[pulseaudio-discuss] PulseAudio and Network Audio Devices

Colin Guthrie gmane at colin.guthr.ie
Mon Dec 17 14:12:17 PST 2007

Lennart Poettering wrote:
> On Sun, 16.12.07 21:53, Richi Plana (richip at richip.dhs.org) wrote:
>>>> I've two Fedora 8 machines on the network where PA seems to run fine on
>>>> each desktop. At least audio comes out through PA as shown by
>>>> pavucontrol. I can't, however, see each other (as was demoed by Lennart
>>>> in one of his videos). Other than pavucontrol, I don't even know how
>>>> else to interact with the PA daemon.
>>> Take a look at paprefs, specifically the Network Access tab.
>> Thanks for the tip. After installing paprefs, I enabled "network access
>> to local sound devices" but the "Allow other machines on LAN to browse
>> for local sound devices" remained grey'd out. Suffice it to say, I'm
>> not
> If this checkbox is greyed out, then you are missing the zeroconf
> plugins for PA. Consider installing the pulseaudio-module-zeroconf package.
>> seeing the local device of the other computer on both computers. I'm
>> using pulseaudio-0.9.7 on Fedora 8 on both. Is it too old?
> Yes, in some way. See my previous mail.
>> I'm also noticing an oddity on the two devices. When I enabled
>> Multicast/RTP sender on one machine, a virtual sink appeared on the
>> Output tab. When I enabled "Simultaenouse output", the simul output
>> virtual device appeared. When I did both on the other machine, neither
>> virtual output device appeared. Not my main concern right now (getting
>> audio to appear on a remote machine is), but I thought I'd mention the
>> oddity anyway.
> paprefs require pulseaudio-module-paprefs installed and
> activated. Which should be the default. 

If your packaging hasn't changed since last time I poached from it, I
think you mean pulseaudio-module-gconf...


More information about the pulseaudio-discuss mailing list