> > > p.s. I'm having problems with the module-tunnel-sink as is but can't > provide > > any useful information except for saying there is a problem :) more > > specifically, has anyone had success in transfering a client from a > local > > (alsa) sink to a tunnel sink and back again? I fail at the "and back > again" > > :( The application creating the sound is mplayer, and it just gets stuck > at > > that point (I'm using padsp mplayer, not the mplayer pulse patch - so > maybe > > the problem is in padsp?) > > Hmm? Please elaborate! well, I'll try, but I don't have much more to add, maybe if I give the steps that end with mplayer getting stuck someone can try to reproduce it. You need two machines, both running pulseaudio server, I tried both linux+windows and linux+linux. The second is more fresh in my memory so here are the steps: 1. load both servers with module-protocol-native-tcp acl-ip=.. (or whatever you need for appropriate permissions) 2. in B, pacmd: load-module module-tunnel-sink server=A (A stands for the ip of A) 3. in B start mplayer using padsp: padsp mplayer some_url_here (I was streaming, but it shouldn't matter if it is a local file I guess). Music starts playing locally on B. 4. in B change the sink for the mplayer client to the sink number of the tunnel module. you hear music coming from A. the exact command is something like "move-sink-input <index for mplayer> <index for tunnel sink>" 5. in B change back the sink of mplayer to the local sink, the exact command is something like "move-sink-input <index of mplayer> <index of local sink>". Music stops completely. Looking at the mplayer terminal output you see it is stuck. Hope this helps, Alon -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20060903/4f3188b3/attachment.htm>