Opened 4 months ago

#1568 new defect

Semantics correction for pps_sao_info_in_ph_flag, pps_alf_info_in_ph_flag, and pps_wp_info_in_ph_flag

Reported by: Ye-Kui Wang Owned by:
Priority: minor Milestone:
Component: spec Version:
Keywords: Cc: ksuehring, bbross, XiangLi, fbossen, jvet@…

Description

In the semantics for the three flags pps_sao_info_in_ph_flag, pps_alf_info_in_ph_flag, and pps_wp_info_in_ph_flag, "and not present" should be replaced with "and is not present". I guess the reason why it ended up like this was historical. My guess is that, initially, the "could be present" in the first half of the sentence was "is present", and in that case, it was OK to use "and not present" in the second half of the sentence, as they share the same "is". Note that this is still the case for the semantics of the other two flags in the same category, i.e., pps_rpl_info_in_ph_flag and pps_qp_delta_info_in_ph_flag. However, later on, we made the semantics of the three flags more accurate and replaced "is present" with "could be present", but forgot to change "and not present" to "and is not present".

For convenience, the semantics of the five flags are copied below:

pps_rpl_info_in_ph_flag equal to 1 specifies that RPL information is present in the PH syntax structure and not present in slice headers referring to the PPS that do not contain a PH syntax structure. pps_rpl_info_in_ph_flag equal to 0 specifies that RPL information is not present in the PH syntax structure and could be present in slice headers referring to the PPS. When not present, the value of pps_rpl_info_in_ph_flag is inferred to be equal to 0.

pps_sao_info_in_ph_flag equal to 1 specifies that SAO filter information could be present in the PH syntax structure and not present in slice headers referring to the PPS that do not contain a PH syntax structure. pps_sao_info_in_ph_flag equal to 0 specifies that SAO filter information is not present in the PH syntax structure and could be present in slice headers referring to the PPS. When not present, the value of
pps_sao_info_in_ph_flag is inferred to be equal to 0.

pps_alf_info_in_ph_flag equal to 1 specifies that ALF information could be present in the PH syntax structure and not present in slice headers referring to the PPS that do not contain a PH syntax structure. pps_alf_info_in_ph_flag equal to 0 specifies that ALF information is not present in the PH syntax structure and could be present in slice headers referring to the PPS. When not present, the value of pps_alf_info_in_ph_flag is inferred to be equal to 0.

pps_wp_info_in_ph_flag equal to 1 specifies that weighted prediction information could be present in the PH syntax structure and not present in slice headers referring to the PPS that do not contain a PH syntax structure. pps_wp_info_in_ph_flag equal to 0 specifies that weighted prediction information is not present in the PH syntax structure and could be present in slice headers referring to the PPS. When not present, the value of pps_wp_info_in_ph_flag is inferred to be equal to 0.

pps_qp_delta_info_in_ph_flag equal to 1 specifies that QP delta information is present in the PH syntax structure and not present in slice headers referring to the PPS that do not contain a PH syntax structure. pps_qp_delta_info_in_ph_flag equal to 0 specifies that QP delta information is not present in the PH syntax structure and is present in slice headers referring to the PPS. When not present, the value of pps_qp_delta_info_in_ph_flag is inferred to be equal to 0.

Change history (0)

Note: See TracTickets for help on using tickets.