Opened 8 months ago

Closed 2 months ago

#736 closed defect (fixed)

Mismatch with vtm on slice header extension and entry_point_offset order

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

Description

In VTM, entry_point_offset are written after slice_header_extension, whereas the spec does the opposite. It seems more logical to write the entry_point_offset at the end of the slice_header.

- if( entry_point_offsets_present_flag && NumEntryPoints > 0 ) {
-   offset_len_minus1
-   for( i = 0; i < NumEntryPoints; i++ )
-     entry_point_offset_minus1[ i ]
- }
if( slice_header_extension_present_flag ) {
  slice_header_extension_length
  for( i = 0; i < slice_header_extension_length; i++)
    slice_header_extension_data_byte[ i ]
}
+ if( entry_point_offsets_present_flag && NumEntryPoints > 0 ) {
+   offset_len_minus1
+   for( i = 0; i < NumEntryPoints; i++ )
+     entry_point_offset_minus1[ i ]
+ }
byte_alignment( )

Change history (3)

comment:1 Changed 8 months ago by ksuehring

I agree. Entry points need to be added to the slice header after the slices are encoded. It makes more sense to have them located at the end of the slice header.

comment:2 Changed 6 months ago by bbross

  • Component changed from spec to VTM
  • Version changed from VVC D7 vE to VTM-7.1

This seems to be a SW issue so changing it to VTM.

comment:3 Changed 2 months ago by ksuehring

  • Component changed from VTM to spec
  • Resolution set to fixed
  • Status changed from new to closed

Fixed by adoption of JVET-R0298. So this ends up with the software being correct and the standard text changed. So changing component back to spec and closing as fixed.

Note: See TracTickets for help on using tickets.