Topics for discussion at the CTA Fall Forum Workshop 2021

[ablasgen]

WAVE is holding a workshop on Monday, September 20 from 07:00-11:00 am PT to cover some of the decision points which require a deeper discussion than the regular TF/group meetings.

Use this issue tracker to contribute discussion items. These will be collated by the TWG 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. Also state which TF or group you feel the work falls under.

[technogeek00]

Topics from DASH-HLS Interop group:

• External evangelism of WAVE specifications, common routes vs specification specific. Do we want to establish some general operating procedures to ensure we are making our specs well known in the industry and getting feedback for subsequent editions?
• How do we identify and track industry groups / areas that align with a particular specification?
• Revisit discussion of direct PDF links to specifications on CTA WAVE site instead of requiring CTA store front access.

[wilaw]

CMSD Overview - I'd like to brief members on the scope & status of the spec, along with some key questions for debate that I will specify at that time.

[johnsim]

• the use of 4CC codes to identify media profiles has fallen out of favor. How should this be reflected in the content specification?
• would it be worthwhile to discuss the status of collaboration with 3GPP, DVB, ATSC on defining media profiles and test vectors?

[technogeek00]

From DASH-HLS Interop group call today:

• How do we prioritize work items for specifications? DASH-HLS looking at litmus test to help establish whether to consider a topic and the prioritization of it.

[jpiesing]

What are the testing priorities for 2022?

• Pushing forwards with more media profiles, HEVC, AV1, (VVC), HDR, more audio codecs
• Filling the gaps in observations for the existing tests. The first iteration of the observation framework is limited to observations that can be made with QR codes. The second iteration covers the additional observations needed for the 2nd iteration of tests but doesn't back-fill the gaps in the first iteration. Specifically;
  1. Video fills the area of the screen expected
  2. For video the following is expected to be observed: • No visible shifts of objects in the video. • No visible spatial offset of pixels in the video.
• A/V sync
  1. The presentation starts with the earliest video sample and the audio sample that corresponds to the same presentation time.
  2. While continuing playback, the media samples of different tracks with the same presentation times are presented jointly.
• Automation / integration between the test runner & the observation framework that was left out of first iteration.
  1. Starting and stopping camera from UI on PC that runs tests.
  2. Streaming camera output to PC that runs tests and analysing it without a manual download process
• More tests - even further down the priorities and/or additional ones we have not yet considered

[jpiesing]

We touched on this before but I don't remember if we reached a conclusion or indeed any actions. Could / should we be doing more about content protected by commercial DRM? Creating (arranging the creation of) content protected by multiple commercial DRMs and somehow facilitating the provision of license servers for that content?

[jpiesing]

Could or should we be doing more about subtitles/captions? If so, what?

[cta-source]

DPCTF Test Suite Release Plan:

How will we launch the first “good” version of the test suite to industry? This goes to 1) completeness of materials, both technical and marketing; 2) quality assurance pre-launch; and 3) plans for promotion of the test suite.

Some things we might consider: • What feature set is “version 1” for industry release? • What qualification testing and criteria do we need to go through? • What’s our bug report process for outside WAVE? • What promotional activities, e.g., website, press releases, conference presentations? • Etc.

This topic should not be discussed to completion at this meeting. A reasonable expected result of this discussion might be, 1) Main activities to be planned (qualification plan, documentation plan, communications (promotion) plan, etc. 2) Assigned responsibilities (task forces, TWG, CMAF-IF, Steering Committee, others?) 3) Plan to plan -- make a plan for a next meeting for the leaders of activities in number 2 above, with an eye for setting a work-back plan.

[JohnRiv]

For HATF, we have a number of open issues around ATSC potentially leveraging the WMAS test suite:

• https://github.com/cta-wave/technical-working-group/issues/16
• https://github.com/cta-wave/WMAS/issues/63
• https://github.com/cta-wave/WMAS/issues/64

Specifically for the Fall Forum, my hope is there will be enough participants that are also involved in ATSC that we could at least address the first issue above and come up with:

• Which WMAS tests are most useful/applicable for ATSC
• How to maintain that list of tests
• The most effective way for ATSC to incorporate those WMAS tests into their testing

The other 2 issues around the test runner are more informative, although if we could have ATSC members confirm/deny if launching the test suite using DIAL without needing modulator is useful, that would be helpful.