- From: Chris Needham <chris.needham@bbc.co.uk>
- Date: Thu, 4 Feb 2021 14:21:41 +0000
- To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
- Message-ID: <AM0PR01MB520198DAC6741BDFACA38A77A8B39@AM0PR01MB5201.eurprd01.prod.exchangelabs>
Dear all, The minutes and slides from Tuesday's Media & Entertainment IG call are available [1, 2]. Many thanks to James, James, and Michael from Grass Valley for joining us, and to all for the discussion. A number of needs were presented: - Capability detection in Web Codecs (which is planned) - Content protection (Please raise a GitHub issue at [3] for further discussion) - Local media editing (e.g., for news-gathering). Is Web Codecs the preferred way to do this, or is a higher level API needed [4] - Contribution codecs such as AVC-I, e.g., via a plugin architecture - Access to timecode, AFD, closed caption data. Are these carried in the encoded bitstream or in the media container, which would be parsed in JavaScript? - Wide colour gamut and high dynamic range video. Anyone interested this topic should join the Color on the Web CG [5], which is holding regular meetings. The next MEIG call will be on Tuesday 2nd March. I'd like to use this to have a follow-up discussion to hear more points of view, to see if there are other needs that we did not have time to cover in this call. In the meantime, please submit any use cases or requirements you have to our Media Production on the Web repo [6]. Many thanks, Chris (Co-chair, W3C Media & Entertainment Interest Group) [1] https://www.w3.org/2021/02/02-me-minutes.html [2] https://www.w3.org/2011/webtv/wiki/images/f/fe/Browser_Hosted_Video_Editing_v0.3.pdf [3] https://github.com/WICG/web-codecs [4] https://github.com/w3c/media-and-entertainment/issues/38 [5] https://www.w3.org/community/colorweb/ [6] https://github.com/w3c/me-media-production
Received on Thursday, 4 February 2021 14:23:27 UTC