Jim Duda wrote: > The documentation for tunnel sink says: > > Tunnel a remote sink/source to a local "ghost" sink/source. Requires a running PulseAudio daemon on the remote server > with module-native-protocol-tcp loaded. It's probably a better idea to connect to the remote sink/source directly since > some buffer control is lost through this tunneling. > > Can anyone expand on "It's probably a better idea to connect to the remote sink/source directly"? What specifically > does this mean to connect directly. Is this referring to using the alsa-pulse plugin and attaching to some remote sink > using the "server", "device", and "sink" parameters in the .asoundrc file? You can do e.g.: PULSE_SERVER=otherhost paplay /path/to/sound.wav Same applied for all pulse clients (alsa routing included). e.g. PULSE_SERVER=otherhost amarok works too. HTHs Col
