Atlantic wrote: > On transactions requiring multiple, sequential DNS lookups, the delays > caused by DNS alone can be a couple of seconds and we find this is > usually sufficient to knock over any real-time services. We try to make > sure that time-sensitive equipments and applications only transact over > our terrestrial uplink, including (of course) any DNS queries they make. >
The following is an explanation why I think DNS should not be the main source of your issue even with your satellite links. First a general comment about SB player - When and SB player (e.g. Touch) plays any stream (http/MP3, http/AAC, HLS or DASH) using a local LMS - the DNS lookup will be done by LMS - the Touch will be told to play a stream from a numeric IP address. The BBCiplayer does all the data comms with BBC - the SB player willbe told to play a stream (i.e. again a numeric IP address) and the source will be the LMS server. When BBCiPlayer is playing HLS streams - a DNS lookup will happen for each 6 sec chunk. Whereas with DASH in 1.5.x using HTTP 1.2 (persistent TCP) - only one DNS lookup should happen for each live stream. With yoru DNS setup I would expect more problem with HLS rather than DASH in 1.5.* unless replies to DASH request tale a long time. This is why message in log file are important. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=106409 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
