Yep. Fortunately audio is relatively low-bandwidth compared to a typical LAN so you can pile on a lot of redundancy. If you want to go crazy you could transmit everything twice from the start.<p>AirTunes uses 352-frame packets. At 44100Hz, that&#x27;s about 8ms per packet. So you definitely do not want to do FEC over more than a fairly small number of packets, or else you&#x27;ll hit audible latency. (In my testing, if two sets of speakers are playing identical audio but with different delays, latency differences can be heard down to about 10ms with the right audio. Under 50ms is <i>usually</i> OK.)<p>Of course, if you&#x27;re doing your own protocol you could use whatever size you want for the packets, keeping in mind that overhead will start to dominate if you make them really tiny.<p>Another problematic question is, what causes the packet loss? If it&#x27;s just random, that&#x27;s one thing, but what if it&#x27;s outside interference? If some outside transmitter blasts your network for, say, 200ms and causes all data to be lost in that time, then a 2s buffer can recover, but a low-latency scheme is screwed no matter what. I don&#x27;t know what the answer is here.