3 ms·
I'm not understanding your comment. A QAM tuner provides the modulating/decoding of the RF signal over coax. If they are moving away from this then fine but why
by bogomipz 10y ago
I'm not understanding your comment. A QAM tuner provides the modulating/decoding of the RF signal over coax. If they are moving away from this then fine but why does that design have "inherent assumptions" that "they own and control the network end-points that provide the video to the display device."? So they can continue to charge people $10 a month in perpetuity? That's about the only reason for that assumption. I certainly can't think of a technical one.
Its hard to read a comment like this and find it any way credible:
"Comcast argued that "running our network code directly on third-party devices without our application [is] not feasible."
Running our "network code"? What? What does even mean? Thats like saying the "system is down." It's the kind of crap that customer service reps say to people when they have no clue why something isn't functioning.
The cable companies have zero credibility at this point. This is about continuing to gouge people that it that have no other choice in getting bits delivered into their home in 2016.
- gumby 10y ago> A QAM tuner provides the modulating/decoding of the RF signal over coax. If they are moving away from this then fine but why does that design have "inherent assumptions" that "they own and control the network end-points that provide the video to the display device."? The old QAM systems broadcast metadata (i.e. channel info) on one channel -- if you wanted an update just have your hardware keep watching until it passes by. Comcast's network is, I believe, an IPv6 system with a bunch of terminals and a set of servers at the core like some big enterprise network. None of which justifies their refusal, which is well above layer 7
- forgottenpass 10y agoComcast's network is, I believe, an IPv6 system with a bunch of terminals and a set of servers at the core like some big enterprise network. If my cable tech was correct, the cable box is such a thin client that every button press on the remote is processed remotely rather than on the cable box. Considering a packet can circumnavigate the planet faster than their goddamn cableboxes will register a button press, I tend to believe it.
- korethr 10y agoThat there are assumptions that they own and control the network end points is betrayed by the comment that you don't find credible. I agree that the comment is poorly worded, but to me, it indicates that the set-top boxes they're renting out are more complex than just than something that naively decodes whatever video codec stream(s) is/are thrown at it. I think it's a reasonable assumption that the set-top boxes that Comcast provides are loaded with at least some proprietary Comcast code that takes care of the various functions the TV box provides (scheduling/channel guide, on-demand, authorization, DRM-handling etc). I think it's also a reasonable assumption that Comcast's video distribution network (and related systems, like billing) are also built with the assumption that the endpoints will have Comcast's code running on them. It could well be that the set-top boxes for their new system are naive MPEG decoders running completely stock OEM firmware, but until presented with evidence of such, I think the former is more likely.
- bogomipz 10y ago"I think it's a reasonable assumption that the set-top boxes that Comcast provides are loaded with at least some proprietary Comcast code that takes care of the various functions the TV box provides (scheduling/channel guide, on-demand, authorization, DRM-handling etc)" In other words a web app? Why does that require dedicated and proprietary hardware? What am I missing?
- korethr 10y agoMaybe a web app, maybe not a web app. Whether the code running on the Comcast set-top boxes is a web app or not doesn't matter. What does matter is that is is that the code running on the Comcast set-top boxes is likely built with the assumption that it would only ever talk to Comcast's back-end, and Comcast's back-end is likely built with the assumption that it will only ever talk to Comcast's set-top box code. In other words, they're going to be tightly coupled. Sufficiently so that decoupling them enough to provide an API compliant with the FCC's proposed ruling is going to be an expensive engineering task that Comcast would rather not have to spend money on.
- jwatte 10y ago