Playback requirements for CMAF HEVC HHD10 ('chh1')

cta-wave / device-playback-task-force

9 stars 0 forks source link

Playback requirements for CMAF HEVC HHD10 ('chh1') #22

Open haudiobe opened 6 years ago

haudiobe commented 6 years ago

Where is the media profile defined?
What are Capability Discovery Options?
- <Define how the media profile capability signaling is donediscovery of the media profile may be done, including existing practices>
What are the Source Buffer Initialization Requirements?
- Codec
- max frame rate
- etc.
What are the Playback Requirements?
- via reference to the above playback requirements define what the media profile playback requirement is

haudiobe commented 5 years ago

10.2.3 Media Profile: CMAF HEVC HHD10 ('chh1') The details for this profile will be added to an updated version of the specification after a questionnaire to the media profile proponents.

haudiobe commented 2 years ago

I added the HEVC Test Content Options to an updated dpctf specification here

https://standards.cta.tech/apps/org/workgroup/dpctf/download.php/34886/dpctf-s00001-v032-WAVE-DPC-v1.12.docx

In order for better tracking, I also provided the content options for each of the profiles here:

https://github.com/cta-wave/Test-Content-Generation/blob/master/Instructions/chh1.md

jpiesing commented 2 years ago

I've tried to make the same style of sparse matrix for HEVC as for AVC following the list of content options. The results are somewhat different from the proposal at the end of the document from @haudiobe .

https://docs.google.com/spreadsheets/d/1wjj4U35uUboOM7sO06AqC3rsFtL_mffgSyPVJGYb7V0/edit?usp=sharing

The biggest difference from AVC is that the limited number of resolutions tested. For AVC, we did a good set of resolutions covering many (most) of those that might get used in a ladder. The original proposal here was just 4 combinations, 1280p50/60, 1280p25/30, 720p50/60 and 720p25/30. For avc, we had 15. I've only put 4 in this google doc.

haudiobe commented 2 years ago

DPCTF Call:

Agree to update based on the proposal from @jpiesing

nicholas-fr commented 2 years ago

I have 2 changes to propose, unless there is a particular reason these tests are relevant for AVC but not for HEVC. This relates to the discussion about consistency in test content across different codecs.

We should include 1 test stream with Picture timing SEI present (pic_struct=0). While this is optional and all content is progressive, the presence of this SEI should be tested as it is for AVC.
In order to test the presence of constant vui_time_scale and vui_num_units_in_tick, at least 1 test stream including VUI timing information should be created.

haudiobe commented 2 years ago

DPCTF Call on 2022/03/09:

agree on both, needs implementation

haudiobe commented 3 months ago

Implemented here in v2.08