Back to Search Document details
36th Meeting: Kemer, TR, November 2024 2024-10-23 20:23
AHG9: On Encoder Optimization Information SEI
Abstract
Following modifications are proposed related to the encoder optimization information SEI:
JVET-AJ0063 AHG9: On Encoder Optimization Information SEI [S. Deshpande (Sharp)]

Following modifications are proposed related to the encoder optimization information SEI:

  • Proposal 1: It is proposed to code the syntax element eoi_object_based_idc using fixed length coding instead of ue(v) coding.
  • Proposal 2: It is proposed to define following new values for the bits in eoi_object_based_idc:
    • bitmask=0x08: Areas outside the detected objects have been overwritten in some form but not with a constant sample value. (along with slight redefinition of the value for bitmask 0x04)
    • bitmask=0x10: Areas in the objects have been treated differently based on the object size. For example, objects are pre-sorted in size and large objects use higher QP values than smaller objects during encoding.
  • Proposal 3: It is proposed to optionally signal the constant luma, cb and cr sample values used for overwriting areas outside of detected objects when (eoi_object_based_idc & 0x04) > 0.
  • Proposal 4: It is proposed to code the eoi_privacy_protection_method_idc syntax element as a bitmask which can allow simultaneous indication of multiple types of protection methods used. It is also proposed to use 8 bits to code this syntax element.
  • Proposal 5: An additional privacy protection method indication (“pixelation”) is proposed to be added to the table which lists possible privacy protection methods.

Agreed proposal 1 to use fixed length code for eoi_object_based_idc with 16 bits. Also add two reserved bits above eoi_type.

Agreed proposal 2 to add bitmask=0x08: Areas outside the detected objects have been overwritten in some form but not with a constant sample value. (along with slight redefinition of the value for bitmask 0x04)

For second aspect of proposal 2, if was noted that the blocks for QP won’t align with object boundaries.

Agreed proposal 2 second aspect to add a bitmask to indicate that larger objects are coded with coarser quality than the smaller objects.

For proposal 3, it was suggested that it would be relatively straightforward for a decoding system to detect a constant value. No action was taken on this.

For proposal 4, agreed to convert the eoi_privacy_protection_method_idc syntax element to a bitmask of 16 bits. Delegate to the editors to improve the wording to refer to “some” privacy information.

For proposal 5, agreed to add pixelation as a privacy protection method.

Decision: Adopt to WD as described above.

Decisions
adopted
Adopt to WD as described above
Citation