Opened 5 years ago

Closed 4 years ago

#989 closed defect (fixed)

Typo in semantics of run_copy_flag on palette mode

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

Description

In 7.4.11.6 Palette coding semantics, run_copy_flag is described as follows;

run_copy_flag equal to 1 specifies that the palette run type is the same as the run type at the previously scanned position and palette run index is the same as the index at the previous scanned position if copy_above_palette_indices_flag is equal to 0. Otherwise, run_copy_flag equal to 0 specifies that the palette run type is different from the run type at the previously scanned position.

Palette index is derived based on CopyAboveIndicesFlag, and copy_above_palette_indices_flag is not signaled when run_copy_flag is equal to 1. So, it should be modified as follows;

run_copy_flag equal to 1 specifies that the palette run type is the same as the run type at the previously scanned position and palette run index is the same as the index at the previous scanned position if CopyAboveIndicesFlag[ xC ][ yC ] copy_above_palette_indices_flag is equal to 0. Otherwise, run_copy_flag equal to 0 specifies that the palette run type is different from the run type at the previously scanned position.

Change history (1)

comment:1 Changed 4 years ago by bbross

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

Good catch, thanks!

This will be fixed in the first version of D10.

Note: See TracTickets for help on using tickets.