Originally Posted by Athlon646464
I was responding to the idea that it is the media player's manufacturer issue that it does not have the current API. Very often it is Netflix and their high licensing requirements instead. It certainly ain't free!!
I can believe that, though I should think that Netflix would want to keep the price low, so as not to discourage anyone from adding Netflix players to their products. Of course, at this point it's kind of de rigueur to include Netflix in your media player if you want it to be competitive, which no doubt gives Netflix a lot of leeway in pricing.
I can understand how initial
licensing might reasonably cause some delays in getting Netflix on your product in the first place, but I'd expect access to new features for current licensees to be immediate for all, barring exclusivity agreements, like the one that Microsoft seemed to have for embedded console implementations for a year or so (and I suspect that Sony has now on use of the 1080p encodings). Anything else would seem like potential unfair restraint of trade. If you allow one licensed manufacturer to offer support for 5.1 soundtracks in their product while making me wait some months before I can offer it, in the meantime my product is a at a competitive disadvantage and it's your fault. I'm not a lawyer, but it seems legally actionable to me.
I've worked on numerous embedded software systems in hardware products which used a lot of off-the-shelf components--Java VMs, audio and video codecs, etc. AFAIK, every licensee of those component was informed of improvements and given access to the improved versions simultaneously. I can see that Netflix might want to review and sign off on your updated implementation before release, but they'd need to keep turnaround on that process pretty rapid. (If they do such reviews they're not very effective, given the glaring and immediately obvious bugs I've run across in some WI players).
BTW - thank you for your list!