From what you've reported above, a direct network client (e.g.
PULSE_SERVER=hostname mplayer /path/to/file ) should not have any more
latency than an on-device player.
And, using the zeroconf client makes that easy, since it's already on the server; Matt, if you load up that module on your workstation, it should see the sink on the pi and make it available to local sinks. (That's what I do at home).
_______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
