{"action":"created","issue":{"url":"https://api.github.com/repos/Dash-Industry-Forum/DASH-IF-IOP/issues/115","repository_url":"https://api.github.com/repos/Dash-Industry-Forum/DASH-IF-IOP","labels_url":"https://api.github.com/repos/Dash-Industry-Forum/DASH-IF-IOP/issues/115/labels{/name}","comments_url":"https://api.github.com/repos/Dash-Industry-Forum/DASH-IF-IOP/issues/115/comments","events_url":"https://api.github.com/repos/Dash-Industry-Forum/DASH-IF-IOP/issues/115/events","html_url":"https://github.com/Dash-Industry-Forum/DASH-IF-IOP/issues/115","id":188547482,"number":115,"title":"comments on HDR for DASH-IF-IOP-v3.95-clean.docx ","user":{"login":"emauena","id":23383932,"avatar_url":"https://avatars.githubusercontent.com/u/23383932?v=3","gravatar_id":"","url":"https://api.github.com/users/emauena","html_url":"https://github.com/emauena","followers_url":"https://api.github.com/users/emauena/followers","following_url":"https://api.github.com/users/emauena/following{/other_user}","gists_url":"https://api.github.com/users/emauena/gists{/gist_id}","starred_url":"https://api.github.com/users/emauena/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emauena/subscriptions","organizations_url":"https://api.github.com/users/emauena/orgs","repos_url":"https://api.github.com/users/emauena/repos","events_url":"https://api.github.com/users/emauena/events{/privacy}","received_events_url":"https://api.github.com/users/emauena/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-11-10T16:03:13Z","updated_at":"2016-11-28T05:25:07Z","closed_at":"2016-11-28T05:25:07Z","body":"The current version of the document only specifies interoperability points that are essential for delivering HDR content, that is, it does not consider to test any metadata scheme. Ericsson believes that readers may find confusing to mention and refer the generic way to carry metadata information through HEVC, especially if the verification of the test vectors excludes them.\r\n\r\nSEI (and CRI) messages is a mechanism in HEVC to carry (or map) metadata, this means that it would be relevant to mention or specified them, only if, DASH-IF decides to consider the inclusion of specific metadata schemes for HDR. Further, it may be proper to define how to carry the specific metadata information at HEVC bitstream level only if DASH-IF decides to evaluate the performance of these schemes with test vectors. At the moment, the latest version of this document let the SEI messages undefined and this may cause unnecesary confusion.\r\n\r\nNote that specifiying metadata presence at higher layer in the DASH protocol is another issue.\r\n\r\nEricsson suggest to have the following text in the document:\r\n\r\nNote that optional metadata may be present in the form of SEI messages as defined in ITU-T H.265 /ISO/IEC 23008-2:2015 [19].\r\n\r\n1.1.1.1.\tBitstream Requirements and Recommendations\r\nA bitstream conforming to the HEVC HDR PQ10 media profile shall comply with the Main Tier Main10 Profile Level 5.1 restrictions, as specified in Recommendation ITU-T H.265 / ISO/IEC 23008-2 [19].\r\nIn addition the requirements in section 10.2.2.2 apply, except that this profile requires the use of Recommendation ITU-R BT.2020 [74] non-constant luminance colorimetry and SMPTE ST 2084 [71].\r\nSMPTE ST 2084 [71] usage shall be signaled by setting colour_primaries to the value 9, transfer_characteristics to the value 16 and matrix_coeffs to the value 9.\r\n\r\n1.1.1.2.\tReceiver Requirements\r\nReceivers conforming to the HEVC HDR PQ10 media profile shall support decoding and displaying HEVC HDR PQ10 bitstreams as defined in section 10.3.2.2.\r\nNo additional processing requirements are defined, for example processing of SEI messages is out of scope.\r\n\r\n/Mauricio"},"comment":{"url":"https://api.github.com/repos/Dash-Industry-Forum/DASH-IF-IOP/issues/comments/263186167","html_url":"https://github.com/Dash-Industry-Forum/DASH-IF-IOP/issues/115#issuecomment-263186167","issue_url":"https://api.github.com/repos/Dash-Industry-Forum/DASH-IF-IOP/issues/115","id":263186167,"user":{"login":"haudiobe","id":2828689,"avatar_url":"https://avatars.githubusercontent.com/u/2828689?v=3","gravatar_id":"","url":"https://api.github.com/users/haudiobe","html_url":"https://github.com/haudiobe","followers_url":"https://api.github.com/users/haudiobe/followers","following_url":"https://api.github.com/users/haudiobe/following{/other_user}","gists_url":"https://api.github.com/users/haudiobe/gists{/gist_id}","starred_url":"https://api.github.com/users/haudiobe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/haudiobe/subscriptions","organizations_url":"https://api.github.com/users/haudiobe/orgs","repos_url":"https://api.github.com/users/haudiobe/repos","events_url":"https://api.github.com/users/haudiobe/events{/privacy}","received_events_url":"https://api.github.com/users/haudiobe/received_events","type":"User","site_admin":false},"created_at":"2016-11-28T05:25:07Z","updated_at":"2016-11-28T05:25:07Z","body":"Candidate Proposal accepted with reservations: \"Qualcomm states reservation on the process and believes that this unnecessarily delays publication by several weeks. The problem that was raised is not understood or should have been raised much earlier.\""}}
{"actor":{"display_login":"haudiobe"}}