On Sat, 2017-08-26 at 11:34 +0000, Mark Raynsford wrote: > On 2017-08-26T12:15:20 +0300 > Tanu Kaskinen <tanuk at iki.fi> wrote: > > > > > > I would guess that you're loading module-tunnel-sink without the "sink" > > parameter, so it will connect to the default sink of the remote server, > > in this case the alsa sink. Pass "sink=NAME" to module-tunnel-sink when > > you load it. Replace NAME with the name of the jack sink. > > Hello! > > Yes, this makes sense. I can't seem to get Pulse to accept the > sink names I'm passing in, however. On the server, I see: > > properties: > device.api = "jack" > device.description = "Jack sink (PulseAudio JACK Sink)" > jack.client_name = "PulseAudio JACK Sink" > device.icon_name = "audio-card" > > So on the client, I've tried: > > load-module module-tunnel-sink server=10.2.17.1 sink="Jack sink" > load-module module-tunnel-sink server=10.2.17.1 sink="Jack sink (PulseAudio JACK Sink)" > load-module module-tunnel-sink server=10.2.17.1 sink="PulseAudio JACK Sink" > > In each case, restarting Pulse on the client doesn't result in any > new outputs appearing (I only get the default local sound card). Some > investigation with Wireshark does show that the client opens a TCP > connection to the server, but it closes it very quickly. > > Is there anything else I can do to try to track down the problem? Sorry, I should have given better instructions. You're not the first one who has trouble figuring out what "sink name" exactly means. "pactl list sinks | grep Name" will print the names of all sinks. -- Tanu https://www.patreon.com/tanuk
