My internet is 100/100 Fiber FWIW.Ĭlick to expand. Anyway, the actual HD stream from the Satellite which is received by the Sling hardware probably isn't what is "slung" to the client (Firestick in this case), so the bitrates are going to be different, and, to do it in near real-time in a consumer device means it probably isn't going to be as efficient as the high-end transcoders Dish uses in their uplink centers, so it could easily end up using more bandwidth than the original signal. Sling/DA probably just uses TLS over http for the transport encryption of the "slung" content. Also, the encryption on the satellite signal needs to be removed as I doubt the DA clients are doing that. That is going to require some transcoding unless there is something I am missing. The secret sauce is the adaptive bit-rate stuff, which isn't so secret anymore, but it allows the throughput to change dynamically based on the network conditions between the source and destination.
In theory, it is going to take the video output from the satellite feed, and transcode it to a format that is readable by the client (Firestick/Android app, browser, iOS App, etc.). Well, I don't know the specifics of Sling's transcoding algorithm, but I would suspect that, to make it fast, it might output more data than is input.
0 kommentar(er)
