4 ms·
> in sports bars, not all the screens have the same amount of buffering in the path Assuming we aren't talking about personal devices, could this be solved at
by culturestate 7y ago
> in sports bars, not all the screens have the same amount of buffering in the path
Assuming we aren't talking about personal devices, could this be solved at install time by ensuring same-length cable runs the same way you would for e.g. HFT tenants in a datacenter? Or is this a different kind of problem?
- thakoppno 7y agoIt is essentially the same problem. A sports bar may have some tvs hooked up via Comcast and some via DirectTV with noticeably different physical layer lengths. Additionally, the modern OTT services resemble personal devices and trade synchronicity for scalability.
- culturestate 7y agoThat makes sense. Assuming a bar probably maintains multiple subscriptions because they need access to both local and national broadcasts, I wonder if there's space to build a platform designed specifically to aggregate video content across providers and distribute it to commercial customers. I'm imagining an OTT service that specifically bids for (or sublicenses) public performance rights for e.g. sports and sells only to public venues, with hardware designed for this purpose. Thinking about it, this seems like the kind of thing that probably already exists in some specific niche.
- wtallis 7y agoIn this case, it's not about cable length, but the number of boxes the data has to travel through before hitting the screen. Cable length matters on the nanosecond scale. For human-noticeable latencies larger than 0.1 seconds, you can only blame buffers where data sits around not moving.