We have collected the most relevant information on Pulseaudio Avahi. Open the URLs, which are collected below, and you will find all the info you are interested in.
How-to set up network audio server based on PulseAudio …
https://blogs.gnome.org/ignatenko/2015/07/31/how-to-set-up-network-audio-server-based-on-pulseaudio-and-auto-discovered-via-avahi/
# dnf install pulseaudio pulseaudio-module-zeroconf avahi Nothing needs to be set up in avahi, so just start and enable daemon: # systemctl start avahi-daemon # systemctl enable avahi-daemon module-native-protocol-tcp will use 4317/tcp port to handle connections, need to open port. 1 2 # firewall-cmd --add-port=4317/tcp
[OpenWrt Wiki] package: pulseaudio-daemon-avahi
https://openwrt.org/packages/pkgdata/pulseaudio-daemon-avahi
PulseAudio (formerly Polypaudio) is a cross-platform, networked sound server.\\ This package enables avahi,bluez and is compiled against dbus, sbc, and avahi.\\ Installed size :
networking - RPi3 PulseAudio & Avahi problem - Raspberry ...
https://raspberrypi.stackexchange.com/questions/67424/rpi3-pulseaudio-avahi-problem
To get the RPi3 seeing my servers Pulse Audio services I can do one of two things; either restart the avahi-daemon on the server systemctl restart avahi-daemon or I manually unload then reload the zeroconf module in PulseAudio pacmd unload-module module-zeroconf-publish then directly aftwards pacmd load-module module-zeroconf-publish.
PulseAudio - LinuxReviews
https://linuxreviews.org/PulseAudio
Avahi and systemds resolved are the most commonly used zeroconf-service for automatic discovery. It is, alternatively, possible to have a line in /etc/pulse/default.pa which specifies a remote PulseAudio server to use by IP: load-module module-tunnel-sink server=xxx.xxx.xxx.xxx (replace xxx.xxx.xxx.xxx with an IP like 192.168.0.2)
networking - How can I force the rediscovery of …
https://askubuntu.com/questions/151216/how-can-i-force-the-rediscovery-of-pulseaudio-virtual-sound-devices
Edit: Unloading and reloading the module-zeroconf-discover with pacmd does not help either and it doesn't appear to be an avahi problem per se since avahi-browse -t --all | grep PulseAudio shows lots of right-looking stuff, even when the devices aren't listed in pavucontrol or pacmd list-sinks.
Running PulseAudio as system service – /dev/blog
https://possiblelossofprecision.net/?p=1956
There are use cases however, where PulseAudio’s system mode is a great tool, e.g. for building a PulseAudio streaming target to stream audio from multiple clients to speakers. First, install PulseAudio, avahi (a free implementation of zeroconf) to publish the service throughout the network and the corresponding PulseAudio module: ? 1
PulseAudio - Ubuntu Wiki
https://wiki.ubuntu.com/PulseAudio
Firestarter & Avahi Programs Using OpenSound/OSS output PulseAudio is a sound server for POSIX and Win32 systems. A sound server is basically a proxy for your sound applications. It allows you to do advanced operations on your sound data as it passes between your application and your hardware.
PulseAudio: Sound over the network - manurevah
https://manurevah.com/blah/en/p/PulseAudio-Sound-over-the-network
Run paprefs and under the "Network Access" tab there should be an option called "Make discoverable PulseAudio network sound device available locally", activate that. Then all is left is to restart PulseAudio on the client. The easiest way …
Now you know Pulseaudio Avahi
Now that you know Pulseaudio Avahi, we suggest that you familiarize yourself with information on similar questions.
