Your browser is not supported. Please update it.

16 August 2005

Microsoft codec weakness tipped as basis for Unicast IPTV approach

We received an awful lot of fan mail at Faultline after our write up of the Microsoft IPTV platform in the last issue, as well as a number of interesting ideas from people in the IPTV market. One that has been dropped to us by a series of technicians in and around that IPTV business, suggests that Microsoft was ‘forced’ into its so called ‘fast channel change’ strategy by deficiencies in its own codec.

We have explained in the past how Microsoft uses unicast servers which are used to initiate a channel change between different multicast channels. The server accelerates the delivery of I- frames to the client and to fill the buffer, and then switches to a multicast stream.

Now we are being told that the reason MSTV had to do this is because its own VC-1 codec would have performed appallingly due to the spacing of I-Frames.

Most codecs deliver I-Frames, the reference frame to which all shortcut references in other frames refer, every 10 to 15 frames, so about 2 or 3 each second.

The less I-Frames a system sends, the more processing work that is needed in the set top to rebuild the frames, but beneficially this leads to less data in total being sent, reducing the overall bandwidth needed. There is a point of diminishing returns when so many of the pixels cannot be predicted in the other frames, that it is better to send another I-frame, rather than vary this depending upon the amount of unpredictable pixels from frame to frame, video tends to be send at a uniform data rate. But the underlying I-frame delivery rate can be tuned at the head end.

Which is why we are not sure we 100% believe that Microsoft has an issue here. On the other hand it may be that VC-1 is architected in a significantly different way to MPEG 4 (H.264), its main rival (we have been led to believe that they are similar in the past) and that causes some of the problems, but while Microsoft refuses to explain to anyone how its ‘rapid channel change’ works, it will continue to be easy for outsiders to take pot shots at the company’s IPTV strategy.

Anyhow the story goes that the unicast servers are a workaround to this problem, not a system benefit and they have a huge impact on scalability.

Existing subscriber statistics on channel changes point to them being grouped around adverts and program starts and endings which is expected to overload these channel change servers and drive up channel change times in the Microsoft architecture, and also drive up the number of servers required on the network.