Opened 2 years ago

Closed 23 months ago

#1548 closed defect (fixed)

A bug in a constraint that requires same content for redundant copies of an SEI message

Reported by: yk Owned by:
Priority: minor Milestone:
Component: spec Version:
Keywords: Cc: ksuehring, bbross, XiangLi, fbossen, jvet@…

Description

As can be seen from here: https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/merge_requests/1944#note_17322

When implementing the following constraint:

When there are multiple SEI messages with a particular value of payloadType not equal to 133 that are associated with a particular AU or DU and apply to a particular OLS or layer, regardless of whether some or all of these SEI messages are scalable-nested, the SEI messages shall have the same SEI payload content.

A bug in the text of the constraint was identified. If a picture has four subpictures, each of which is associated with an SEI message, e.g., the decoded picture hash SEI message, contained in a scalable nesting SEI message with sn_subpic_flag equal to 1, then per the current wording of the constraint, the four SEI messages shall have the same payload content. That's incorrect and not the intent.

Therefore, in the constraint, "OLS or layer" should be changed to be "OLS, layer, or subpicture", which is the intent.

Change history (1)

comment:1 Changed 23 months ago by yk

  • Resolution set to fixed
  • Status changed from new to closed

Thanks! To be fixed in JVET-Z2005-v1.

Note: See TracTickets for help on using tickets.