<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head>
<body>
<p> </p>
<div style="margin: 5px 0px;">
> >
<br/>
> > I'd like to use PulseAudio to stream high-quality, low-latency
<br/>
> > (50-100ms) audio from a PC to an Android device over a managed
<br/>
> > wireless network.  I have the server running on the PC, but am having
<br/>
> > trouble on the Android side.  I'm not an Android developer so I don't
<br/>
> > have the ability or knowledge to re-build the kernel, make custom
<br/>
> > configurations or anything like that.  Is there any other way that I
<br/>
> > can get PulseAudio on a device for testing and experimentation with
<br/>
> > the rest of my system?
<br/>
>
<br/>
> What device is your Android system running on? If you care only about
<br/>
> playback (and don't mind other stuff being completely broken), and are
<br/>
> using a Galaxy Nexus (both *big* ifs, of course), I could provide an
<br/>
> image for you to try.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Right now I have a Motorola Droid 3, but I'm willing to purchase new hardware for my testing.  For right now all I care about is playback and the lowest latency possible and maintaining audio quality.  Other Android features will not be needed.</p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">I also have easy access to some TI-based reference designs using the OMAP3630 if you think that would be a viable option. </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px;">
>
<br/>
> > Related to this project, has anyone measured or estimated what the
<br/>
> > lowest end-to-end latency of this system could be, assuming all parts
<br/>
> > are optimized at both end of the signal chain?
<br/>
>
<br/>
> Assuming decent ALSA drivers on your target device, the main variable
<br/>
> here is the wireless network. In the ideal world, our RTP modules would
<br/>
> receive more love and work better, making things more robust. I know
<br/>
> there are periodic glitches over the TCP tunnel, and haven't had time to
<br/>
> try to pin them down, but your mileage may vary.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">I'll have complete control over a managed WiFi network, so once I'm streaming I can start playing around with the network config.</p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Incidentally, can I stream from one source to multiple client devices, or is the connection strictly 1-to-1?</p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Thanks.</p>
<p style="margin: 0px;"> - Dave </p>
</body>
</html>