We have collected the most relevant information on Xpra Pulseaudio. Open the URLs, which are collected below, and you will find all the info you are interested in.
Sound – Xpra
https://www.xpra.org/trac/wiki/Sound
XPRA_PULSEAUDIO_DEVICE_NAME to use a specific device if there is more than one device to choose from (can happen when using an existing pulseaudio server with more than one output device attached) XPRA_SOUND_CODEC_ENABLE_xxxx (replace xxxx with a codec name): can be used to force enable a specific codec (not recommended)
FAQ – Xpra
https://www.xpra.org/trac/wiki/FAQ
"Warning: pulseaudio has terminated. Either fix the pulseaudio command line or use --no-pulseaudio to avoid this warning." This usually occurs when an xpra session is started from a running X11 session which already has its own pulseaudio server running. Pulseaudio does not support multiple servers per user.
xpra/Audio.md at master · Xpra-org/xpra · GitHub
https://github.com/Xpra-org/xpra/blob/master/docs/Features/Audio.md
A Linux client's pavucontrol showing the Xpra application connected to the local pulseaudio server: pavucontrol running within the xpra session ("on the server"), showing xpra recording the session's audio: Options Main options. The main controls can be specified in the configuration file or on the command line, and they are documented in the ...
Xpra + VirtualGL · Issue #320 · Xpra-org/xpra · GitHub
https://github.com/Xpra-org/xpra/issues/320
Half those warnings already tell you what to do: use -no-notifications or start xpra with dbus-launch (see FAQ); use --no-pulseaudio or launch as a different user to get sound; The GFlags warnings are GTK things and beyond our control, I believe you can just ignore those.. Apart from that I don't see any new errors - just the odd RANDR one, but please post:. the whole …
Now you know Xpra Pulseaudio
Now that you know Xpra Pulseaudio, we suggest that you familiarize yourself with information on similar questions.
