These instructions work, but it's not exactly what I wanted.<div><br></div><div>I have 2 machines, each logged in. Machine A has a sound card, machine B does not. I would like to be able to sit down at machine B and run applications, whose audio will go to the speakers hooked up to A. This means that an application would have to use one machine as its X server, and another seperate machine as its pulseaudio server.</div> <div><br></div><div>What I'd really like is for the pulseaudio server at B to show the sinks/sources from A, so I could just select A's sound device as the fallback (although since it's the only device, even that wouldn't be neccesary.) This takes place over avahi right now as I understand it, but I'd like it to expand beyond that. (It's a high-speed network, but different link-level networks).</div> <div><br><div class="gmail_quote">On Tue, Feb 2, 2010 at 02:38, Colin Guthrie <span dir="ltr"><<a href="mailto:gmane@colin.guthr.ie">gmane@colin.guthr.ie</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> So the easiest way is to:<br> <br> 1. On the machine where you want to hear things, run paprefs and enable<br> network access to local sound devices. To save trouble, it's easiest to<br> tick the box "do not require authentication" too but I'll assume you<br> have not ticked this box (if things break, this is step one to check!)<br> 2. Ensure start-pulseaudio-x11 has been run on this machine (xprop<br> -root| grep PULSE will tell you) and if not, run it.<br> 3. ssh -X -R 4713:localhost:4713 othermachine<br> 4. export PULSE_SERVER=localhost<br> 5. Run any pulseaudio client.<br> <br> That's it.<br> <br> <br> This should setup a reverse SSH tunnel from the destination machine back<br> to the source machine. PA uses TCP port 4713 by default for it's network<br> support and we override the PULSE_SERVER variable on the remote machine<br> to point at localhost which is, in turn, a tunnel over SSH back to our<br> source machine which connects to the PA servers network socket.<br> <br> Other information regarding authentication etc. should be passed across<br> in X11 properties (the -X flag to ssh ensures this although I believe it<br> is generally enabled by default anyway).<br> <br> Of course if SSH were aware of PA in the same way it's aware of X11,<br> then this wouldn't be needed and it would just work. Perhaps one day :)<br> <br> <br> Hope this helps.<br> <div><div></div><div class="h5"><br> Col<br> <br> --<br> <br> Colin Guthrie<br> gmane(at)<a href="http://colin.guthr.ie" target="_blank">colin.guthr.ie</a><br> <a href="http://colin.guthr.ie/" target="_blank">http://colin.guthr.ie/</a><br> <br> Day Job:<br> Tribalogic Limited [<a href="http://www.tribalogic.net/" target="_blank">http://www.tribalogic.net/</a>]<br> Open Source:<br> Mandriva Linux Contributor [<a href="http://www.mandriva.com/" target="_blank">http://www.mandriva.com/</a>]<br> PulseAudio Hacker [<a href="http://www.pulseaudio.org/" target="_blank">http://www.pulseaudio.org/</a>]<br> Trac Hacker [<a href="http://trac.edgewall.org/" target="_blank">http://trac.edgewall.org/</a>]<br> <br> _______________________________________________<br> pulseaudio-discuss mailing list<br> <a href="mailto:pulseaudio-discuss@mail.0pointer.de">pulseaudio-discuss@mail.0pointer.de</a><br> <a href="https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss" target="_blank">https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss</a><br> </div></div></blockquote></div><br><br clear="all"><br>-- <br>Jeremy Nickurak -= Email/XMPP: <a href="mailto:jeremy@nickurak.ca">jeremy@nickurak.ca</a> =-<br><br> </div>