... TCP or UDP doesn't matter. You can have higher level protocals of your own that use UDP just as robustly as TCP. UDP is just less overhead. But if a packet is lost a client can just ask for it again. As long as it stays ahead (keeps buffer from underruning) it's all fine and still jitterless. In small networks, in a home for example, UDP rarely fails...
Yes. That protocol is called TCP
No point reinventing the wheel.
As for small home networks, I think you would be surprised what people expect from their networks now a days, multiple AV streams, disc shadowing/backups etc all things used in a typical Sooloos network and some other networks . What do you think is happening exactly when the words 'buffering' appear on a device? You can build a really fast network that can continuously handle a high load requiring low latency, but we are talking about consumer devices here installed by consumers who may simply run the devices as wireless, peo or through the router supplied by their ISP. Meridian themselves recommend connecting Sooloos to its own router because they appreciate that Sooloos may be susceptible to network load. I can even remember one post on here talking about removing Sooloos from internet benefiting sound quality.
Google Search
|
Meridian Systems
|
Meridian Streaming
|
Restaurant
|
WiKi
|
Duncan's Meridian Info
|
Board Rules
|
Restaurant Rules
