Re: how does EME/DRM effect captioning

On Wed, Apr 3, 2013 at 1:32 PM, Glenn Adams <glenn@skynav.com> wrote:
> On Wed, Apr 3, 2013 at 4:18 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
>> On Tue, Apr 2, 2013 at 7:24 PM, Glenn Adams <glenn@skynav.com> wrote:
>> > On Tue, Apr 2, 2013 at 2:45 AM, Henri Sivonen <hsivonen@iki.fi> wrote:
>> >> On Thu, Mar 28, 2013 at 7:01 PM, Glenn Adams <glenn@skynav.com> wrote:

>> Which browsers currently implement MPEG-2 without DRM in HTML5 video?
>
> Hmm, let's see, there are Samsung Smart TVs, LG TVs, Sony TVs, .... I'm not
> sure where the list stops.

Thanks. Do you happen to know how recently these TV makers added HTML5
video support to the embedded browsers? Do they also support H.264?

>> Which content providers currently serve MPEG-2 in an HTML5-based
>> player?
>
> Every commercial video service provider I am familiar with.

Which ones are you familiar with? Does Netflix stream MPEG-2 to
devices that can do H.264? (Seems unlikely.)

(I'm aware of a cloud PVR that streams the original MPEG-2 data
captured from DVB-T, but they also offer H.264 recompressions. So if
they chose to migrate from using out-of-browser viewer apps to HTML5,
they could. But that service is irrelevant to EME, since they don't
add any DRM to the data captured from DRMless DVB-T broadcasts.)

> A better question would be whether and when they intend to use something
> other than MPEG-2?
...
> There is something called legacy systems.

Do you expect the services you are talking about to target Chrome or
IE using HTML5/EME? Or just Samsung/LG/Sony TVs?

--
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/

Received on Wednesday, 3 April 2013 11:05:50 UTC