Changes between Version 5 and Version 6 of Sound/Debugging

Timestamp:

01/31/18 04:25:21 (10 months ago)

Author:

Antoine Martin

Comment:

https

Sound/Debugging

@@ -1 +1 @@
 {{{#!div class="box"
-[[Image(http://xpra.org/icons/sound.png)]]
+[[Image(https://xpra.org/icons/sound.png)]]
 = Sound Debugging =
 
@@ -105 +105 @@
 == 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 pulseaudio server running. Simply clearing the environment and trying to start a new pulseaudio instance will not work without some serious hacks to the environment variables that pulseaudio uses to find existing instances. If this is what you really want, [http://winswitch.org/about/ winswitch] will do this for you.
+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 pulseaudio server running. Simply clearing the environment and trying to start a new pulseaudio instance will not work without some serious hacks to the environment variables that pulseaudio uses to find existing instances. If this is what you really want, [https://winswitch.org/about/ winswitch] will do this for you.
 [[BR]]
 Now, assuming that you have a dedicated user, '''without''' any pulseaudio server running, and that the {{{pulseaudio}}} option is enabled (ie: no {{{--no-pulseaudio}}} command line option and no {{{pulseaudio = no}}} in the {{{xpra.conf}}} file). You should be able to setup a sound-capable environment by using simply: