Topics for discussion at the CTA Spring Forum CMAF-IF Workshop 2021

[ablasgen]

The CMAF Industry Forum will hold a virtual meeting on Tuesday, May 4th from: PDT: 7:00-9:00am EDT: 10:00am-12:00pm CEST: 4:00-6:00pm

Use this issue tracker to contribute discussion items. These will be collated by the CMAF-IF Chair before the meeting and converted in to a presentation deck to drive the agenda for the day. For each item, please suggest a title, and provide some background text as well as the decision to made or call-to-action.

[haudiobe]

A few topics:

• 8K Video Profiles initially based on HEVC
• Common Media Profiles for VVC across DVB, MPEG, SCTE, 3GPP and others
• Support of ISO/ITU-T codecs in web browsers

[johnsim]

**From: https://hulu-my.sharepoint.com/:w:/p/zachary_cava/EQ9rtUd0QLJOnCFuyULr-LUBprPLujzF5ojl7riLDE7E_A

Clause 2.4 Known Issues**

[DASH] MPD Patching and [HLS] Partial Updates [DASH] Remote Resolution and [HLS] Interstitials [DASH] Multiple Base URLs and [HLS] Content Steering Usage of priority mechanisms for HTTP2/3 connections in [DASH] and [HLS] Low-Latency operation modes

[johnsim]

Proposed questionnaire for Smart TV providers regarding HTML5 playback of CMAF content.

From its inception the CTA WAVE project has promoted interoperable media playback by standardized encoding and playback, based on the ISO/IEC Common Media Application Format (CMAF) and W3C HTML5 Media Source Extensions (MSE) and Encrypted Media Extensions (EME).

In a recent Bitmovin report, nearly a third of OTT devices targeted by developers were Smart TVs. Yet it has been reported that some smart TVs must throttle MSE at 1080p and that there are limitations in UI responsiveness, especially with limited memory. Yet the IPTV Forum Hybridcast application is reportedly straight HTML with MSE/EME.

[johnsim]

Problem statement to W3C ME IG regarding CMAF playback in HTML5

The W3C Mission Statement is to lead the World Wide Web to its full potential. With 80+% of Internet consumption being media playback, unless HTML5 becomes a better platform for media playback, the role of W3C can only diminish with time.

We suggest considering: 1) consider embedded browsers in addition to desktop browsers while developing web media standards; 2) require interop between embedded and desktop browsers be a requirement for approving a recommendation; 3) update TAG requirements to allow for specialized web media Miniapps clients; 4) have the TAG define a class of web media clients which would not prevent capability reporting based on fingerprinting concerns; 5) allow incubations of web media app Miniapps clients separate from incubation of desktop browsers, perhaps managed by W3C MEIG; 6) provide a standard way for device manufacturers to surface broadly adopted, standards-based codecs supported by their hardware.

[johnsim]

Next steps on the CMAF Survey 1) open questions from the CMAF Survey 2) producing a public facing report of the survey

[johnsim]

Common Media Profiles for all WAVE media profiles across DVB, MPEG, SCTE, 3GPP and others. (I agree with Thomas' proposed topic, but would like to extend it to all or WAVE media profiles.)

[cta-source]

Next steps on the CMAF Survey

1. open questions from the CMAF Survey
2. producing a public facing report of the survey

I'd like to address this, with help from John and Krasimir who have been very involved in creating this survey. I would like to host a discussion about what kinds of 2nd-order information is interesting.

Examples:

• Breaking down responses by region
• Chains of responses; e.g., if you answered question M with response X, how likely is it that you answered question N with response Y?
• What can we learn or say about someone how supports multiple technologies (CMAF with both DASH & HLS; or Widevine/Playready/etc.),?

I'll have the PPT from the March CMAF-IF meeting as a base but will add some stuff to it.