I'm in the process of setting up PulseAudio over TCP. I already got my server running and I want to playback sound from a headless VM.
I can play sound through my server if I simply do:
export $PULSE_SERVER=<server ip> play xyz.wav
So it seems that pulseaudio is actually not needed on the client at all?
In the Arch Linux documentation this is regarded as a quick fix and not a suitable permanent setup (https://wiki.archlinux.org/index.php/PulseAudio/Examples#When_everything_else_seems_to_fail)
What's the "proper" way of setting up my client? I guess I should use the cookie, but security is a nonissue at the moment.
Keep in mind that I don't have access to
pavucontrol on the client because no X11 server is running.
I could probabl use
pacmd, but then I have to run pulseaudio on the client. When I do that via
W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Thanks in adance.