Opened 5 months ago

#1505 new defect

Misleading bitstream requirement related to EOB NAL unit

Reported by: jonatan Owned by:
Priority: minor Milestone:
Component: Text Version: v5 (02/2018)
Keywords: Cc: bbross, wjhan, jct-vc@…

Description

In Section 7.4.2.4.3 "Order of access units and association to CVSs" a requirement is expressed related to access units after an end of bitstream NAL unit.

"It is a requirement of bitstream conformance that, when present, the next access unit after an access unit that contains an end of sequence NAL unit or an end of bitstream NAL unit shall be an IRAP access unit, which may be an IDR access unit, a BLA access unit, or a CRA access unit."

However, in section 7.4.3.7 "End of bitstream RBSP semantics" it is said that there are no NAL units (and thus no access units) present after the EOB NAL unit.

"The end of bitstream RBSP indicates that no additional NAL units are present in the bitstream that are subsequent to the end of bitstream RBSP in decoding order."

It seems misleading to impose a requirement on NAL units after the EOB NAL unit and at the same time state that there are no NAL units after the EOB NAL unit. The suggested fix is to remove "or an end of bitstream NAL unit" from the bitstream requirement in Section 7.4.2.4.3:

"It is a requirement of bitstream conformance that, when present, the next access unit after an access unit that contains an end of sequence NAL unit shall be an IRAP access unit, which may be an IDR access unit, a BLA access unit, or a CRA access unit."

Change History (0)

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber, Participant

  • Benjamin Bross(Subscriber)
  • jct-vc@…(Subscriber)
  • Jonatan Samuelsson(Reporter)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Woo-Jin Han(Subscriber)