Opened 4 years ago

Last modified 4 years ago

#1434 assigned defect

Contradictions in spec, and typos.

Reported by: adil.parvez Owned by: rajan_joshi
Priority: minor Milestone:
Component: SCC text Version:
Keywords: contradiction variable syntax element typo Cc: jct-vc@…

Description

In 8.4.1 General decoding process for coding units coded in intra prediction mode, the invocations of decoding process 8.4.4.1 use controlParaAct, however controlParaAct is not an input to this process and is not used within. This looks like a remnant of an old draft and should be removed.

In 7.1 Method of specifying syntax in tabular form, it is claimed that 'When syntax_element appears, it specifies that a syntax element is parsed from the bitstream'. However, in 7.4.3.3.3 Picture parameter set screen content coding extension semantics, the spec says 'The values of pps_act_y_qp_offset, pps_act_cb_qp_offset and pps_act_cr_qp_offset are derived as pps_act_y_qp_offset_plus5 − 5, pps_act_cb_qp_offset_plus5 − 5 and pps_act_cr_qp_offset_plus3 − 3 respectively'. This is a contradiction, since pps_act_{y,cb,cr}_qp_offset are derived variables. Consider renaming to PpsAct{Y,Cb,Cr}QpOffset. (This also contradicts the text of 5.10 Variables, syntax elements, and tables).

In 7.3.2.3.1 General picture parameter set RBSP syntax, there is a typo
...
if (pps_scc_extension_flag)

pps_scc_extension_flag()

...
should be
...
if (pps_scc_extension_flag)

pps_scc_extension()

...

Change History (1)

comment:1 Changed 4 years ago by rajan_joshi

  • Component changed from HM SCC to SCC text
  • Owner set to rajan_joshi
  • Status changed from new to assigned
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

  • Adil Parvez(Reporter)
  • jct-vc@…(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Rajan Joshi(Owner, Participant)