Changes between Version 4 and Version 5 of Sound

Timestamp:

01/07/13 10:46:27 (8 years ago)

Author:

Antoine Martin

Comment:

--

Sound

@@ -16 +16 @@
 * a client with sound output of any kind (even virtual)
 * a server with pulseaudio (for going beyond the simple test step)
+* users must be "pulseaudio-enabled" - whatever that means in terms of permissions and user setup (distribution specific)
 
 == Test Sound Source Setup ==
@@ -53 +54 @@
 == Test Remote Setup ==
 Using a second client machine (or a second desktop session, virtual machine, etc), we can connect this new client to the server and get the sound from the desktop session forwarded to the client.
-The server can be running the test source or a the desktop session's pulseaudio server. In the case of an existing pulseaudio server, simply start any sound application.
+The server can be running the test source or a the desktop session's pulseaudio server. In the case of an existing pulseaudio server, simply start any sound application in the desktop session, the sound should come out in both this session's speakers (if any) and the client's speakers (if any / different!).
 {{{pavucontrol}}} on the server should show an Xpra entry in the {{{Recording}}} tab.
 The client should show an Xpra entry in the {{{Playback}}} tab (or whatever mixer/sound tool you have installed)
+
+== Full Setup ==
+Finally, we may want an xpra session to use a dedicated pulseaudio server.
+This is more difficult and at present, unless you really know what you are doing and are prepared to pickup the pieces, you should not attempt to do this as a user which already has an existing dbus session and pulseaudio server. Simply clearing the environment and trying to start a new pulseaudio instance will not work without some serious hacks to the environment variable that pulseaudio uses to find existing instances. [http://winswitch.org/about/ winswitch] will do this for you.
+[[BR]]
+Now, assuming that you have a dedicated user, '''without''' any form of dbus or pulseaudio server running. You should be able to setup a sound-capable environment by using a command line similar to this one:
+{{{
+dbus-launch xpra start :10 --no-pulseaudio \
+  --start-child="pulseaudio --start --daemonize=false --system=false \
+                --exit-idle-time=-1 -n --load=module-suspend-on-idle \
+                --load=module-null-sink --load=module-native-protocol-unix \
+                --log-level=4 --log-target=stderr"
+}}}
+Notes:
+ * the {{{--no-pulseaudio}}} flag is there to prevent old support code from firing - this may get removed in the future.
+ * you will need to use a tcp socket ({{{--bind-tcp=}}} or ssh forwarding to connect to this account - out of scope here.
+ * we may well introduce new xpra command line options to simplify this setup process
+
+You should then see these messages in the server log:
+{{{
+(..)
+D: [pulseaudio] main.c: Got org.PulseAudio1!
+D: [pulseaudio] main.c: Got org.pulseaudio.Server!
+I: [pulseaudio] main.c: Daemon startup complete.
+2013-01-07 17:42:55,732 xpra is ready.
+}}}
+And when connecting a sound capable client:
+{{{
+I: [pulseaudio] client.c: Created 0 "Native client (UNIX socket client)"
+(...)
+2013-01-07 17:44:32,205 will send sound using mp3 codec
+(...)
+2013-01-07 17:44:32,309 starting sound using null.monitor
+D: [pulseaudio] module-suspend-on-idle.c: Sink null becomes busy.
+}}}
+
+And yet more log messages as your start a sound application in this xpra session.