Contents
What is PulseAudio sink?
A sink is an output device. The typical sink represents an output sound device, e.g. headphones connected to a sound card line output or on a Bluetooth headset. PulseAudio automatically creates a sink for every detected output device. Sink input. A sink input is a playback stream.
What are PulseAudio monitors?
The de facto Linux sound system, PulseAudio, allows any sound output (or “sink” in PulseAudio’s nonclementure) to be monitored. In PulseAudio land, each sink has a corresponding “source” called the monitor source which can be read just like any other other PulseAudio input such as a microphone.
What do I need to set up a PulseAudio sink?
For that, on fedora, you need the mpg123-plugins-pulseaudio package. For flash stuff in the browser (eg, youtude) you need alsa-plugins-pulseaudio (these are what actually connect to the remote server). Other distros should have similiar packages. If you’ve been using pulseaudio before (I was not), you may have them installed already.
How to set up a PulseAudio sink on a Raspberry Pi?
My pi’s LAN address with the default pulseaudio port. But here’s something that then had me confused for a while — with a server specified, pulseaudio would not even start: > pulseaudio –start N: [pulseaudio] main.c: User-configured server at tcp:192.168.2.13:4713, refusing to start/autospawn.
Is there a tool to read out PulseAudio volume?
They’ve opted to use a tool similar to pactl called pacmd that also comes with PulseAudio. If you take a look at man pacmd you’ll find that it can be “used to introspect or reconfigure a running PulseAudio sound server during runtime” ( pacmd man page ).
Do you have to run PulseAudio on the desktop?
However, as it turns out, you don’t have to run it at all on the desktop (sending) side, something which is not spelled out in the pulseaudio docs. Using lsof -i -P it appears that lower level plugins for various media players do the work.