W3C home > Mailing lists > Public > public-web-and-tv@w3.org > December 2017

Media Capabilities: supplying the init segment (was: Re: [me] minutes - 7 December 2017)

From: François Daoust <fd@w3.org>
Date: Thu, 28 Dec 2017 09:04:53 +0100
To: Chris Needham <chris.needham@bbc.co.uk>, Kazuyuki Ashimura <ashimura@w3.org>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <e531e4d4-21c5-3e62-d128-daebfa48c778@w3.org>
Le 11/12/2017 à 09:27, Chris Needham a écrit :
> Thanks Kaz,
> For those not able to join the call yesterday, here's a short summary of the outcomes:
> - Mounir and Francois from Google talked through the Media Capabilities API [1]. The explainer [2] gives a good introduction, which I encourage you to read.
> - A next step is to extend the API to cover HDR displays. Input from IG members on this is welcome.
> - Another gap is the ability to query the UA's ability to seamlessly playback streams that switch between different encodings. At TPAC, Mark Vickers presented a document from CTA WAVE with requirements for Media Source Extensions [3].
> - Will raised a couple of specific points regarding MPEG CMAF (which Cyril mentioned during the IG meeting at TPAC [4]):
> -- Can the video and audio configurations have an optional definition mode in which the corresponding init segment of the media is supplied as a binary object? This will help address deficiencies in codec strings which are insufficient in describing the dynamic range and color volume combinations which may occur in media. These attributes are not captured by the current defined fields of width, height, bitrate and framerate.

A quick note that Will raised this particular point on the Media 
Capabilities issue tracker:

Received on Thursday, 28 December 2017 08:05:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:37 UTC