Thanks Sean and Marten, this has answered my question, very much appreciated. I had hoped to send my local machine's microphone (for voice) over the Internet to the remote machine, but through all the various configuration I've done the delay/latency problem persists. Ah well, I had fun trying! Many thanks again, Cheers, Nick -----Original Message----- From: pulseaudio-discuss-bounces@xxxxxxxxxxxxxxxx [mailto:pulseaudio-discuss-bounces at mail.0pointer.de] On Behalf Of Maarten Bosmans Sent: Sunday, April 17, 2011 9:24 PM To: General PulseAudio Discussion Subject: Re: Pulseaudio recording device re-direct from local machine over cable broadband to remote server / "latency" problem 2011/4/17 Sean McNamara <smcnam at gmail.com>: > I don't know if pulseaudio supports any kind of protocol compression > these days, but traditionally it does not. And due to that, it is > generally unsuitable for use over the public internet. Lossy > compression such as mp3, and protocols such as RTP and Icecast, exist > for this purpose. Even if both nodes are dedicated servers with > symmetric 100mbps, your transport latency over the internet is too high for most uses of PA. Indeed, it is still the case that only raw PCM audio streaming is supported. For CD quality audio this means a 44100Hz x 16bit x 2ch = 1.4 Mbit/s bandwidth requirement. > I've heard about lots of interest in extending the PA protocol to > support lossy, non-PCM formats, but I don't *think* that has been added quite yet. The CELT codec would be the best candidate for that, as it is specifically designed for low-latency requirements. Maarten _______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss at mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
