Conditional signaling of video coding syntax elements

Optimized video encoding and decoding methods using specific formatting rules and syntax elements address inefficiencies in video coding standards, reducing bandwidth demands and enhancing decoding accuracy.

JP7583063B2Active Publication Date: 2024-11-13BYTEDANCE INC
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
JP2022563488
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-04-26
Filing Date
2021-04-23
Publication Date
2024-11-13
Estimated Expiration
2041-04-23

AI Technical Summary

Technical Problem

Existing video coding standards face challenges in efficiently processing and decoding video data due to complex syntax elements and constraints, leading to increased bandwidth demands and inefficiencies in video encoding and decoding processes.

Method used

The implementation of specific formatting rules and syntax elements for video processing, including control information for chroma components, deblocking modes, picture segmentation, saturation quantization parameters, and motion vector differences, to optimize video encoding and decoding methods.

Benefits of technology

Enhances the efficiency of video encoding and decoding processes by reducing bandwidth requirements and improving decoding accuracy through optimized syntax element handling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007583063000176
    Figure 0007583063000176
  • Figure 0007583063000177
    Figure 0007583063000177
  • Figure 0007583063000178
    Figure 0007583063000178
Patent Text Reader

Abstract

Systems, methods, and apparatuses for video processing are described. The video processing may include video encoding, video decoding, or video transcoding. One example of video processing includes converting a video including one or more pictures to a bitstream of the video according to a format rule, where the format rule specifies that a first syntax element indicating whether to indicate a motion vector difference for a particular reference picture list (RPL) is conditionally included in the bitstream based on (i) a second syntax element indicating whether RPL information is included in the picture header, and / or (ii) the number of reference pictures for the particular RPL if RPL information is present in the picture header.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS Book This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 015623, filed April 26, 2020. and International Patent Application No. PCT / US2021 / 028974, filed April 23, 2021. All of the foregoing patent applications are incorporated herein by reference in their entireties.

[0002] This patent specification relates to image and video coding and decoding. [Background technology]

[0003] Digital video accounts for the largest bandwidth usage on the Internet and other digital communications networks, and the bandwidth demands for digital video use are expected to continue to grow as the number of connected user devices capable of receiving and displaying video increases. Summary of the Invention

[0004] This application discloses techniques that may be used by video encoders and decoders to process coded representations of video using control information useful for decoding the coded representations.

[0005] In one example aspect, a video decoding method is disclosed that includes converting video having one or more chroma components, the video including one or more video pictures including one or more slices, to a coded representation of the video, the coded representation conforming to a format rule that specifies that a chroma array type field controls constraints on chroma transformation characteristics used during the conversion.

[0006] In another exemplary aspect, another video processing method is disclosed that includes converting between video, including one or more video pictures, including one or more video regions, and a coded representation of the video, the coded representation conforming to format rules that specify that the coded representation includes a deblocking mode indicator that indicates applicability of a deblocking filter to the video region being converted.

[0007] In another exemplary aspect, another video processing method is disclosed that includes converting between one or more video pictures that include one or more video slices and / or one or more video sub-pictures and a coded representation of the video, the coded representation conforming to a format rule that specifies a flag indicating whether a single slice per sub-picture mode is considered valid for the video picture when picture splitting is disabled for the video picture.

[0008] In another exemplary aspect, another video processing method is disclosed that includes converting between video that includes one or more video pictures that include one or more video slices and a coded representation of the video, the coded representation conforming to format rules that specify signaling a picture- or slice-level chroma quantization parameter offset in a picture header or slice header.

[0009] In another exemplary aspect, another video processing method is disclosed. The method includes transforming between video including one or more video pictures including one or more video slices and a coded representation of the video, where the coded representation complies with format rules that specify that a chroma quantization parameter (QP) table applicable to a transform of video blocks of the video is derived as an XOR operation between (delta_qp_in_val_minus1[i][j]+1) and delta_qp_diff_val[i][j], where delta_qp_in_val_minus1[i][j] specifies a delta value used to derive an input coordinate of a j-th pivot point of an i-th chroma mapping table, and delta_qp_diff_val[i][j] specifies a delta value used to derive an output coordinate of the j-th pivot point of the i-th chroma QP mapping table, where i and j are integers.

[0010] In another exemplary aspect, another video processing method is disclosed. The method includes converting between video including one or more video pictures and a coded representation of the video, the coded representation conforming to a format rule that specifies that a first syntax element (SE) indicating whether to signal a motion vector difference (MVD) for a reference picture list (RPL) is conditionally included in the coded representation based on a number of reference pictures in the RPL, if RPL information is present in the picture header, and a second SE indicating whether reference picture list information is signaled in the picture header.

[0011] In another exemplary aspect, another video processing method is disclosed. The method includes converting between video that includes one or more video pictures and a coded representation of the video, where the coded representation conforms to a format rule that specifies that a first syntax element (SE) indicating whether to disable a decoder motion vector refinement (DMVR) tool is conditionally included in the coded representation based on whether reference picture list (RPL) information is signaled in a picture header (PH), whether this second SE is included in the coded representation, and a number of reference pictures of a previous RPL if this RPL information is present in the picture header (PH), and / or whether a flag indicating applicability of the DMVR tool included at a sequence parameter set level in the coded representation is equal to one.

[0012] In another exemplary aspect, another video processing method is disclosed that includes converting between video that includes one or more video pictures and a coded representation of the video, where the coded representation conforms to a format rule that specifies that a first syntax element (SE) indicating whether to disable bidirectional optical flow (BDOF) tools is conditionally included in the coded representation based on whether reference picture list (RPL) information is signaled in a picture header (PH), whether a second SE is included in the coded representation, and a number of reference pictures in RPL-1 if the RPL information is present in the picture header (PH), and / or a flag indicating applicability of BDOF tools at a sequence parameter set level.

[0013] In another exemplary aspect, another video processing method is disclosed. The method includes converting between video including one or more video pictures and a coded representation of the video, where the coded representation conforms to a format rule that specifies that a first syntax element (SE) indicating whether a co-located picture used for temporal motion vector prediction is derived from reference picture list 0 is conditionally included based on a second SE indicating whether reference picture list information is signaled in a picture header (PH), the number of reference pictures in RPL-1 if RPL information is present in the picture header, and whether a temporal motion vector prediction (TMVP) tool is enabled for the current picture.

[0014] In another exemplary aspect, another video processing method is disclosed. The method includes converting between video including one or more video pictures and a coded representation of the video, the coded representation conforming to a format rule that specifies whether a first syntax element (SE) indicating a table of prediction weights is included in the coded representation conditionally based on a second SE indicating whether weighted prediction (WP) information is signaled in a picture header (PH), whether reference picture list (RPL) information is signaled in the PH, and, if RPL information is present in the PH, the number of reference pictures in RPL-1, and whether a flag indicating applicability of weighted prediction and / or weighted bidirectional prediction is included in a picture parameter set.

[0015] In another exemplary aspect, another video processing method is disclosed that includes converting between video that includes one or more video pictures and a coded representation of the video, the coded representation conforming to format rules that specify whether intra slices are allowed to be used to represent a video picture in the coded representation depending on whether inter slices are allowed for the picture and whether there are multiple partitions.

[0016] In another exemplary aspect, another video processing method is disclosed. The method includes converting video including one or more pictures to a bitstream of the video according to a format rule, where the format rule specifies that a first syntax element indicating whether motion vector differences relative to a particular reference picture list (RPL) are indicated is conditionally included in the bitstream based on (i) whether a second syntax element indicates whether RPL information is included in the picture header, and / or (ii) the number of reference pictures for the particular RPL if RPL information is present in the picture header.

[0017] In another exemplary aspect, another video processing method is disclosed that includes transforming a video including one or more pictures to a bitstream of the video according to rules that specify which syntax elements to group in a general constraint information syntax structure that indicates one or more constraints applicable to the transformation.

[0018] In another exemplary aspect, another video processing method is disclosed that includes converting video including one or more pictures to a bitstream of the video in accordance with format rules that selectively include instructions for enabling use of intra slices within a picture based on (i) whether inter slices are allowed in the picture and / or (ii) whether the picture is divided into multiple partitions.

[0019] In another exemplary aspect, another video processing method is disclosed. The method includes converting video including one or more pictures to a bitstream of the video according to a format rule, wherein the format rule specifies that a first syntax element indicating whether to disable a decoder motion vector refinement (DMVR) tool is conditionally included in the bitstream based on (i) whether a second syntax element indicates whether reference picture list (RPL) information is included in a picture header (PH), and / or (ii) the number of reference pictures in the RPL if RPL information is present in the PH, and / or (iii) whether a flag indicating applicability of the DMVR tool included at a sequence parameter set level in the bitstream is equal to a particular value.

[0020] In another exemplary aspect, another video processing method is disclosed. The method includes converting video including one or more pictures to a bitstream of the video according to a format rule, wherein the format rule specifies that a first syntax element indicating whether to disable a bidirectional optical flow (BDOF) tool is conditionally included in the bitstream based on (i) whether a second syntax element indicates whether reference picture list (RPL) information is included in a picture header (PH), and / or (ii) the number of reference pictures in the RPL if RPL information is present in the PH, and / or (iii) a flag indicating applicability of the BDOF tool at a sequence parameter set level.

[0021] In another exemplary aspect, another video processing method is disclosed. The method includes converting a video including one or more pictures to a bitstream of the video according to a format rule, the format rule specifying that a first syntax element indicating whether a co-located picture used for temporal motion vector prediction is derived from reference picture list 0 is conditionally included based on (i) a second syntax element indicating whether reference picture list (RPL) information is signaled in a picture header (PH), and / or (ii) the number of reference pictures in the RPL if RPL information is present in the PH, and / or (iii) a flag indicating applicability of temporal motion vector prediction (TMVP) tools for coding the current picture.

[0022] In another exemplary aspect, another video processing method is disclosed. The method includes converting video including one or more pictures to a bitstream of the video according to a format rule, wherein the format rule specifies whether a first syntax element indicating a table of prediction weights is conditionally included in the bitstream based on (i) a second syntax element indicating whether weighted prediction (WP) information is included in a picture header (PH), and / or (ii) a third syntax element indicating whether reference picture list (RPL) information is included in the PH, and / or (iii) the number of reference pictures in the RPL when RPL information is present in the PH, and / or (iv) a fourth syntax element indicating applicability of weighted prediction and / or a fifth syntax element indicating applicability of weighted bidirectional prediction included in a picture parameter set.

[0023] In another exemplary aspect, another video processing method is disclosed. The method includes converting video including one or more pictures to a bitstream of the video according to a format rule that specifies conditionally including a first syntax element, indicating a number of weights signaled for a particular reference picture list entry, in a syntax structure indicating a table of prediction weight parameters in the bitstream based on (i) a second syntax element, indicating whether a picture header includes weighted prediction (WP) information, and / or (ii) a third syntax element, indicating whether the picture header includes reference picture list (RPL) information, and / or (iii) a number of reference pictures in a particular RPL, and / or (iv) a fourth syntax element, included in a picture parameter set, indicating applicability of explicit weighted prediction for a B slice that references the picture parameter set.

[0024] In yet another exemplary aspect, a video encoder apparatus is disclosed, the video encoder comprising a processing unit configured to implement the above-described method.

[0025] In yet another exemplary aspect, a video decoder apparatus is disclosed, the video decoder comprising a processing unit configured to implement the above-described method.

[0026] In yet another exemplary aspect, a computer readable medium having code stored thereon is disclosed, the code performing one of the methods described herein in the form of processor executable code.

[0027] These and other features are described throughout this specification. [Brief explanation of the drawings]

[0028] [Figure 1] FIG. 1 is a block diagram illustrating an example of a video processing system. [Figure 2] FIG. 1 is a block diagram of a video processing device. [Figure 3]1 is a flowchart illustrating an example of a video processing method. [Figure 4] 1 is a block diagram illustrating a video coding system according to some embodiments of the present invention. [Figure 5] 1 is a block diagram illustrating an encoder according to some embodiments of the present invention. [Figure 6] FIG. 2 is a block diagram illustrating a decoder according to some embodiments of the present invention. [Figure 7] 1 is a flowchart illustrating an example of a video processing method. [Figure 8A] 1 is a flowchart illustrating an example of a video processing method. [Figure 8B] 1 is a flowchart illustrating an example of a video processing method. [Figure 8C] 1 is a flowchart illustrating an example of a video processing method. [Figure 8D] 1 is a flowchart illustrating an example of a video processing method. [Figure 8E] 1 is a flowchart illustrating an example of a video processing method. [Figure 8F] 1 is a flowchart illustrating an example of a video processing method. [Figure 8G] 1 is a flowchart illustrating an example of a video processing method. [Figure 9] 1 is a flowchart illustrating an example of a video processing method. DETAILED DESCRIPTION OF THE INVENTION

[0029] Section headings are used herein for ease of understanding and are not intended to limit the applicability of the technology and embodiments described in each section to that section alone. Furthermore, the term H.266 is used in certain descriptions for ease of understanding only and is not intended to limit the scope of the disclosed technology. Thus, the technology described herein is applicable to other video codec protocols and designs.

[0030] 1. Introduction This specification relates to video coding technology. Specifically, it relates to syntax designs for APS, deblocking, subpictures, and QP delta in video coding. The concepts may be applied individually or in various combinations to any video coding standard or non-standard video codec that supports multi-layer video coding, such as the currently developed Versatile Video Coding (VVC).

[0031] 2. Abbreviations APS Adaptation Parameter Set AU Access Unit AUD Access Unit Delimiter AVC Advanced Video Coding CLVS Coded Layer Video Sequence CPB Coded Picture Buffer CRA Clean Random Access CTU Coding Tree Unit CVS Coded Video Sequence DPB Decoded Picture Buffer DPS Decoding Parameter Set EOB End Of Bitstream EOS End Of Sequence GDR Gradual Decoding Refresh HEVC High Efficiency Video Coding HRD Hypothetical Reference Decoder IDR Instantaneous Decoding Refresh JEM Joint Exploration Model MCTS Motion-Constrained Tile Sets NAL Network Abstraction Layer OLS Output Layer Set PH Picture Header PPS Picture Parameter Set PROF Prediction Refinement with Optical Flow PTL Profile, Tier and Level PU Picture Unit RBSP Raw Byte Sequence Payload SEI Supplemental Enhancement Information SH Slice Header SPS Sequence Parameter Set SVC Scalable Video Coding VCL Video Coding Layer VPS Video Parameter Set VTM VVC Test Model VUI Video Usability Information VVC Versatile Video Coding

[0032] 3. Initial consultations Video coding standards have evolved primarily through the development of well-known ITU-T and ISO / IEC standards. ITU-T developed H.261 and H.263, while ISO / IEC developed MPEG-1 and MPEG-4 Visual. The two organizations jointly developed H.262 / MPEG-2 Video, H.264 / MPEG-4 Advanced Video Coding (AVC), and H.265 / HEVC. Since H.262, video coding standards have been based on hybrid video coding architectures that utilize temporal prediction and transform coding. To explore future video coding technologies beyond HEVC, VCEG and MPEG jointly established the Joint Video Exploration Team (JVET) in 2015. Since then, many new methods have been adopted by the JVET and incorporated into reference software called the Joint Exploration Model (JEM). JVET meets quarterly, and the new coding standards aim for a 50% bitrate reduction compared to HEVC. At the April 2018 JVET meeting, the new video coding standard was officially named "VVC (Versatile Video Coding)" and the first version of the VVC Test Model (VTM) was released at that time. As efforts to contribute to the standardization of VVC continue, new coding techniques are adopted for the VVC standard at every JVET meeting. After each meeting, the VVC Working Draft and Test Model VTM are updated. The VVC project is currently aiming for Technical Finalization (FDIS) at the July 2020 meeting.

[0033] 3.1 PPS Syntax and Semantics In the latest VVC draft text, the PPS syntax and semantics are as follows:

[0034] [Table 1] [Table 2] [Table 3] [Table 4] [Table 5] [Table 6]

[0035] The PPS RBSP shall be available to the decoding process before it is referenced, or shall be contained in at least one AU with a TemporalId less than or equal to the TemporalId of the PPS NAL unit that references it, or shall be provided through external means. All PPS NAL units with a particular value of pps_pic_parameter_set_id within one PU shall have the same content.

[0036] pps_pic_parameter_set_id indicates the PPS to which other syntax elements refer. The value of pps_pic_parameter_set_id is in the range of 0 to 63. PPS NAL units share the same value space for pps_pic_parameter_set_id regardless of the nuh_layer_id value. Let ppsLayerId be the value of nuh_layer_id of a particular PPS NAL unit, and vclLayerId be the value of nuh_layer_id of a particular VCL NAL unit. A particular VCL NAL unit shall not reference a particular PPS NAL unit unless its ppsLayerId is less than or equal to vclLayerId and the layer whose nuh_layer_id equals ppsLayerId is contained in at least one OLS that contains a layer whose nuh_layer_id equals vclLayerId.

[0037] pps_seq_parameter_set_id specifies the value of sps_seq_parameter_set_id of the SPS. The value of pps_seq_parameter_set_id is in the range of 0 to 15. The value of pps_seq_parameter_set_id shall be the same in all PPSs referenced by coded pictures in one CLVS.

[0038] mixed_nalu_types_nalu_pic_flag equal to 1 specifies that each picture that references a PPS has two or more VCL NAL units, no VCL NAL units have the same value of nal_unit_type, and the picture is not an IRAP picture. mixed_nalu_types_in_pic_flag equal to 0 specifies that each picture that references a PPS has one or more VCL NAL units, and the VCL NALs of each picture that references a PPS have the same value of nal_unit_type. If no_mixed_nalu_types_in_pic_constraint_flag is equal to 1, the value of mixed_nalu_types_in_pic_flag shall be equal to 0.

[0039] For each slice whose nal_unit_type value nalUnitTypeA is in the range IDR_W_RADL to CRA_NUT, and which also contains one or more slices with another value of nal_unit_type (i.e., the value of mixed_nalu_types_in_pic_flag of picture picA is equal to 1), the following applies: - This slice shall belong to subpicA, whose corresponding subpic_treated_as_pic_flag[i] value is equal to 1. - This slice shall not belong to a subpicture of picA that contains a VCL NAL unit whose nal_unit_type is not equal to nalUnitTypeA. - If nalUnitTypeA is equal to CRA, then for all PUs that follow the current picture in CLVS in decoding order and output order, RefPicList[0] and RefPicList[1] of slices in subpicA in those PUs shall not contain any pictures that precede picA in decoding order in the active entry. - Otherwise (i.e., nalUnitTypeA is IDR_W_RADL or IDR_N_LP), for all PUs in the CLVS that follow the current picture in decoding order, neither RefPicList[0] nor RefPicList[1] of slices in subpicA in these PUs shall contain any picture that precedes picA in decoding order in the active entry.

[0040] mixed_nalu_types_in_pic_flag equal to NOTE 1-1 indicates that the picture referencing the PPS contains slices with different NAL unit types, e.g., is a coded picture resulting from a sub-picture bitstream merge operation, and must ensure matching of the bitstream structure and also alignment of the parameters of the original bitstreams. An example of such alignment is as follows: If the value of sps_idr_rpl_flag is equal to 0 and mixed_nalu_types_in_pic_flag is equal to 1, the picture referencing the PPS cannot have slices with nal_unit_type equal to IDR_W_RADL or IDR_N_LP.

[0041] pic_width_in_luma_samples specifies the width, in units of luma samples, of each picture decoded with reference to the PPS. pic_width_in_luma_samples shall not be equal to 0, shall be an integer multiple of Max(8,MinCbSizeY), and shall be less than or equal to pic_width_max_in_luma_samples. If res_change_in_clvs_allowed_flag is equal to 0, the value of pic_width_in_luma_samples shall be equal to pic_width_max_in_luma_samples.

[0042] pic_height_in_luma_samples specifies the height, in units of luma samples, of each picture decoded with reference to the PPS. pic_height_in_luma_samples shall not be equal to 0, shall be an integer multiple of Max(8,MinCbSizeY), and shall be less than or equal to pic_height_max_in_luma_samples. If res_change_in_clvs_allowed_flag is equal to 0, the value of pic_height_in_luma_samples shall be equal to pic_height_max_in_luma_samples.

[0043] The variables PicWidthInCtbsY, PicHeightInCtbsY, PicSizeInCtbsY, PicWidthInMinCbsY, PicHeightInMinCbsY, PicSizeInMinCbsY, PicSizeInSamplesY, PicWidthInSamplesC, and PicHeightInSamplesC are derived as follows: PicWidthInCtbsY=Ceil(pic_width_in_luma_samples÷CtbSizeY) (69) PicHeightInCtbsY=Ceil(pic_height_in_luma_samples÷CtbSizeY) (70) PicSizeInCtbsY=PicWidthInCtbsY*PicHeightInCtbsY (71) PicWidthInMinCbsY=pic_width_in_luma_samples / MinCbSizeY (72) PicHeightInMinCbsY=pic_height_in_luma_samples / MinCbSizeY (73) PicSizeInMinCbsY=PicWidthInMinCbsY*PicHeightInMinCbsY (74) PicSizeInSamplesY=pic_width_in_luma_samples*pic_height_in_luma_samples (75) PicWidthInSamplesC=pic_width_in_luma_samples / SubWidthC (76) PicHeightInSamplesC=pic_height_in_luma_samples / SubHeightC (77)

[0044] A pps_conformance_window_flag equal to 1 indicates that the next conformance cropping window offset parameters in the SPS follow next in the PPS. A pps_conformance_window_flag equal to 0 indicates that no conformance cropping window offset parameters are present in the PPS.

[0045] pps_conf_win_left_offset, pps_conf_win_right_offset, pps_conf_win_top_offset, and pps_conf_win_bottom_offset specify the samples of the CLVS picture output from the decoding process with respect to the rectangular area set by the output picture coordinates. If pps_conformance_window_flag is equal to 0, the values ​​of pps_conf_win_left_offset, pps_conf_win_right_offset, pps_conf_win_top_offset, and pps_conf_win_bottom_offset are inferred to be equal to 0.

[0046] The adaptive cropping window includes luma samples having horizontal picture coordinates from SubWidthC*pps_conf_win_left_offset to pic_width_in_luma_samples-(SubWidthC*pps_conf_win_right_offset+1) and vertical picture coordinates from SubHeightC*pps_conf_win_top_offset to pic_height_in_luma_samples-(SubHeightC*pps_conf_win_bottom_offset+1). The value of SubWidthC*(pps_conf_win_left_offset+pps_conf_win_right_offset) is smaller than pic_width_in_luma_samples, and the value of SubHeightC*(pps_conf_win_top_offset+pps_conf_win_bottom_offset) is smaller than pic_height_in_luma_samples.

[0047] If ChromaArrayType is not equal to 0, the corresponding specified samples of the two chroma arrays are samples with picture coordinates (x / SubWidthC, y / SubHeightC), where (x, y) are the picture coordinates of the specified luma sample.

[0048] NOTE 2 – The conformance cropping window offset parameters are applied only at the output side. All internal decoding processes are applied to the uncropped picture size.

[0049] Let ppsA and ppsB be any two PPSs that refer to the same SPS. It is a bitstream conformance requirement that if ppsA and ppsB have the same values ​​for pic_width_in_luma_samples and pic_height_in_luma_samples, respectively, then ppsA and ppsB shall have the same values ​​for pps_conf_win_left_offset, pps_conf_win_right_offset, pps_conf_win_top_offset, and pps_conf_win_bottom_offset, respectively.

[0050] It is a bitstream conformance requirement that when pic_width_in_luma_samples is equal to pic_width_max_in_luma_samples and pic_height_in_luma_samples is equal to pic_height_max_in_luma_samples, pps_conf_win_left_offset, pps_conf_win_right_offset, pps_conf_win_top_offset, and pps_conf_win_bottom_offset are equal to sps_conf_win_left_offset, sps_conf_win_right_offset, sps_conf_win_top_offset, and sps_conf_win_bottom_offset, respectively.

[0051] scaling_window_explicit_signalling_flag equal to 1 specifies that the scaling window offset parameter is present in the PPS. scaling_window_explicit_signalling_flag equal to 0 specifies that the scaling window offset parameter is not present in the PPS. If res_change_in_clvs_allowed_flag is equal to 0, the value of scaling_window_explicit_signalling_flag shall be equal to 0.

[0052] scaling_win_left_offset, scaling_win_right_offset, scaling_win_top_offset, and scaling_win_bottom_offset specify offsets applied to the picture size for the calculation of the scaling ratio. If not present, the values ​​of scaling_win_left_offset, scaling_win_right_offset, scaling_win_top_offset, and scaling_win_bottom_offset are inferred to be equal to pps_conf_win_left_offset, pps_conf_win_right_offset, pps_conf_win_top_offset, and pps_conf_win_bottom_offset, respectively. The value of SubWidthC * (scaling_win_left_offset + scaling_win_right_offset) shall be smaller than pic_width_in_luma_samples, and the value of SubHeightC * (scaling_win_top_offset + scaling_win_bottom_offset) shall be smaller than pic_height_in_luma_samples.

[0053] The PicOutputWidthL and PicOutputHeightL variables are derived as follows: PicOutputWidthL=pic_width_in_luma_samples- (78) SubWidthC*(scaling_win_right_offset+scaling_win_left_offset) PicOutputHeightL=pic_height_in_luma_samples- SubWidthC*(scaling_win_bottom_offset+scaling_win_top_offset) (79)

[0054] The PicOutputWidthL and PicOutputHeightL of the reference picture of the current picture that refers to this PPS are set to refPicOutputWidthL and refPicOutputHeightL, respectively. The bitstream conformance requirement is that all of the following conditions be satisfied. - PicOutputWidthL*2 shall be equal to or greater than refPicWidthInLumaSamples. - PicOutputHeightL*2 shall be greater than or equal to refPicHeightInLumaSamples. - PicOutputWidthL shall be less than or equal to refPicWidthInLumaSamples*8. - PicOutputHeightL shall be less than or equal to refPicHeightInLumaSamples*8. - PicOutputWidthL*pic_width_max_in_luma_samples shall be greater than or equal to refPicOutputWidthL*(pic_width_in_luma_samples-Max(8,MinCbSizeY). - PicOutputHeightL*pic_height_max_in_luma_samples shall be greater than or equal to refPicOutputHeightL*(pic_height_in_luma_samples-Max(8,MinCbSizeY)).

[0055] output_flag_present_flag equal to 1 indicates the presence of the pic_output_flag syntax element in the slice header that references the PPS. output_flag_present_flag equal to 0 indicates the absence of the pic_output_flag syntax element in the slice header that references the PPS. subpic_id_mapping_in_pps_flag equal to 1 specifies that subpic_id_mapping_in_pps_flag is signaled in the PPS. subpic_id_mapping_in_pps_flag equal to 0 specifies that subpic_id_mapping_in_pps_flag is not signaled in the PPS. If subpic_id_mapping_explicitly_signalled_flag is 0 or subpic_id_mapping_in_sps_flag is 1, the value of subpic_id_mapping_in_pps_flag shall be 0. Otherwise (subpic_id_mapping_explicitly_signalled_flag is equal to 1 and subpic_id_mapping_in_sps_flag is equal to 0), the value of subpic_id_mapping_in_pps_flag shall be equal to 1.

[0056] pps_num_subpics_minus1 shall be equal to sps_num_subpics_minus1. pps_subpic_id_len_minus1 shall be equal to sps_subpic_id_len_minus1. pps_subpic_id[i] specifies the subpicture ID of the i-th subpicture. The length of the pps_subpic_id[i] syntax element is pps_subpic_id_len_minus1+1 bits.

[0057] The variable SubpicIdVal[i] is derived as follows for each value of i in the range 0 to sps_num_subpics_minus1: for(i=0;i<=sps_num_subpics_minus1;i++) if(subpic_id_mapping_explicitly_signalled_flag) SubpicIdVal[i]=subpic_id_mapping_in_pps_flag?pps_subpic_id[i]:sps_subpic_id[i](80) else SubpicIdVal[i]=i

[0058] A requirement for bitstream conformance is that both of the following constraints apply: - SubpicIdVal[i] shall not equal SubpicIdVal[j] if i and j are two distinct values ​​in the range from 0 to sps_num_subpics_minus1. - If the current picture is not the first picture in the CLVS, for each value of i in the range from 0 to sps_num_subpics_minus1, if the value of SubpicIdVal[i] is not equal to the value of SubpicIdVal[i] of the previous picture in decoding order in the same layer, then the nal_unit_type of all coded slice NAL units of subpictures in the current picture with subpicture index i shall be equal to a specific value in the range from IDR_W_RADL to CRA_NUT.

[0059] When no_pic_partition_flag is equal to 1, it specifies that picture partitioning is not applied to each picture that references a PPS. When no_pic_partition_flag is equal to 0, it specifies that each picture that references a PPS can be divided into multiple tiles or slices. It is a bitstream conformance requirement that the value of no_pic_partition_flag shall be the same for all PPSs referenced by coded pictures within one CLVS. If the value of sps_num_subpics_minus1+1 is greater than 1, it is a bitstream conformance requirement that the value of no_pic_partition_flag is not 1. pps_log2_ctu_size_minus5+5 specifies the block size of the luma coding tree block of each CTU. pps_log2_ctu_size_minus5 shall be equal to sps_log2_ctu_size_minus5. num_exp_tile_columns_minus1+1 explicitly specifies the number of tile column widths provided. The value of num_exp_tile_columns_minus1 shall be in the range from 0 to PicWidthInCtbsY-1. If no_pic_partition_flag is equal to 1, the value of num_exp_tile_columns_minus1 is inferred to be equal to 0. num_exp_tile_rows_minus1+1 explicitly specifies the number of tile row heights provided. The value of num_exp_tile_rows_minus1 shall be in the range from 0 to PicHeightInCtbsY-1. If no_pic_partition_flag is equal to 1, the value of num_tile_rows_minus1 is inferred to be equal to 0. tile_column_width_minus1[i]+1 specifies the width of the ith tile column, in CTB units of the ith tile column, in the range 0 to num_exp_tile_columns_minus1-1. tile_column_width_minus1[num_exp_tile_columns_minus1] is used to derive the width of tile columns with indices greater than or equal to num_exp_tile_columns_minus1 as specified in Section 6.5.1. The value of tile_column_width_minus1[i] shall be in the range 0 to PicWidthInCtbsY-1. If not present, the value of tile_column_width_minus1[0] is inferred to be equal to PicWidthInCtbsY-1. tile_row_height_minus1[i]+1 specifies the height of the ith tile column, in CTB units of the ith tile row, in the range 0 to num_exp_tile_rows_minus1-1. tile_row_height_minus1[num_exp_tile_rows_minus1] is used to derive the height of tile rows with indices greater than or equal to num_exp_tile_rows_minus1 as specified in Section 6.5.1. The value of tile_row_height_minus1[i] shall be in the range 0 to PicHeightInCtbsY-1. If not present, the value of tile_row_height_minus1[0] is inferred to be equal to PicHeightInCtbsY-1.

[0060] rect_slice_flag equal to 0 specifies that the tiles in each slice are arranged in raster scan order and slice information is not signaled in the PPS. rect_slice_flag equal to 1 specifies that the tiles in each slice cover a rectangular area of ​​the picture and slice information is signaled in the PPS. If not present, rect_slice_flag is inferred to be equal to 1. When subpic_info_present_flag is equal to 1, the value of rect_slice_flag shall be equal to 1. single_slice_per_subpic_flag equal to 1 specifies that each subpicture consists of one and only one rectangular slice. single_slice_per_subpic_flag equal to 0 specifies that each subpicture may consist of one or more rectangular slices. If single_slice_per_subpic_flag is equal to 1, num_slices_in_pic_minus1 is inferred to be equal to sps_num_subpics_minus1. If not present, the value of single_slice_per_subpic_flag is inferred to be equal to 0.

[0061] num_slices_in_pic_minus1+1 specifies the number of rectangular slices in each picture that refer to the PPS. The value of num_slices_in_pic_minus1 shall be in the range from 0 to MaxSlicesPerPicture-1, where MaxSlicesPerPicture shall be as specified in Annex A. If no_pic_partition_flag is 1, the value of num_slices_in_pic_minus1 is inferred to be equal to 0.

[0062] A tile_idx_delta_present_flag equal to 0 specifies that there are no tile_idx_delta values ​​in the PPS and that all rectangular slices of pictures referencing the PPS are provided in raster order according to the processing in Section 6.5.1. A tile_idx_delta_present_flag equal to 1 specifies that there are tile_idx_delta values ​​in the PPS and that all rectangular slices of pictures referencing the PPS are provided in the order indicated by the tile_idx_delta values. If not present, the value of tile_idx_delta_present_flag is inferred to be 0. slice_width_in_tiles_minus1[i]+1 specifies the width of the i-th rectangular slice in tile columns. The value of slice_width_in_tiles_minus1[i] must be in the range from 0 to NumTileColumns-1.

[0063] If slice_width_in_tiles_minus1[i] is not present, the following applies: - If NumTileColumns is equal to 1, the value of slice_width_in_tiles_minus1[i] is inferred to be equal to 0. - Otherwise, infer the value of slice_width_in_tiles_minus1[i] as specified in Section 6.5.1.

[0064] slice_height_in_tiles_minus1[i]+1 specifies the height of the i-th rectangular slice in tile rows. The value of slice_height_in_tiles_minus1[i] must be in the range from 0 to NumTileRows-1. If slice_height_in_tiles_minus1[i] is not present, the following applies: - If NumTileRows is equal to 1, or tile_idx_delta_present_flag is equal to 0 and tileIdx%NumTileColumns is greater than 0, the value of slice_height_in_tiles_minus1[i] is equal to 0. - Otherwise (NumTileRows is not equal to 1 and tile_idx_delta_present_flag is equal to 1 or tileIdx%NumTileColumns is equal to 0), if tile_idx_delta_present_flag is equal to 1 or tileIdx%NumTileColumns is equal to 0, the value of slice_height_in_tiles_minus1[i] is inferred to be equal to slice_height_in_tiles_minus1[i-1].

[0065] num_exp_slices_in_tile[i] specifies the number of slice heights explicitly provided for the current tile, including two or more rectangular slices. The value of num_exp_slices_in_tile[i] shall be in the range of 0 to RowHeight[tileY]-1, where tileY is the tile row index containing the i-th slice. If not present, the value of num_exp_slices_in_tile[i] is inferred to be equal to 0. If num_exp_slices_in_tile[i] is equal to 0, the value of the variable NumSlicesInTile[i] is derived to be equal to 1. exp_slice_height_in_ctus_minus1[j]+1 specifies the height of the jth rectangular slice in the current tile, in CTU rows. The value of exp_slice_height_in_ctus_minus1[j] shall be in the range 0 to RowHeight[tileY]-1, where tileY is the tile row index of the current tile.

[0066] When num_exp_slices_in_tile[i] is greater than 0, the variables NumSlicesInTile[i] and SliceHeightInCtusMinus1[i+k] for k in the range 0 to NumSlicesinTile[i]-1 are derived as follows: remainingHeightInCtbsY=RowHeight[SliceTopLeftTileIdx[i] / NumTileColumns] numExpSliceInTile=num_exp_slices_in_tile[i] for(j=0;j <numExpSliceInTile-1;j++){ SliceHeightInCtusMinus1[i++]=exp_slice_height_in_ctu_minus1[j] remainingHeightInCtbsY-=SliceHeightInCtusMinus1[j] } uniformSliceHeightMinus1=SliceHeightInCtusMinus1[i-1] while(remainingHeightInCtbsY>=(uniformSliceHeightMinus1+1)){ SliceHeightInCtusMinus1[i++]=uniformSliceHeightMinus1 remainingHeightInCtbsY-=(uniformSliceHeightMinus1+1) j++ } if(remainingHeightInCtbsY>0){ SliceHeightInCtusMinus1[i++]=remainingHeightInCtbsY j++ } NumSlicesInTile[i]=j (81)

[0067] tile_idx_delta[i] specifies the difference between the tile index of the first tile in the i-th rectangular slice and the tile index of the first tile in the (i+1)-th rectangular slice. The value of tile_idx_delta[i] shall be in the range of -NumTilesInPic+1 to NumTilesInPic-1. If not present, the value of tile_idx_delta[i] is inferred to be equal to 0. If present, the value of tile_idx_delta[i] is inferred to be equal to 0.

[0068] loop_filter_across_tiles_enabled_flag equal to 1 specifies that in-loop filtering operations can occur across tile boundaries in pictures referencing the PPS. loop_filter_across_tiles_enabled_flag equal to 0 specifies that in-loop filtering operations cannot occur across tile boundaries in pictures referencing the PPS. In-loop filtering operations include deblocking filter, sample adaptive offset filter, and adaptive loop filter operations. If not present, the value of loop_filter_across_tiles_enabled_flag is inferred to be equal to 1. loop_filter_across_slices_enabled_flag equal to 1 specifies that in-loop filtering operations can be performed across slice boundaries in pictures referencing the PPS. loop_filter_across_slice_enabled_flag equal to 0 specifies that in-loop filtering operations are not performed across slice boundaries in pictures referencing the PPS. In-loop filtering operations include deblocking filter, sample adaptive offset filter, and adaptive loop filter operations. If not present, the value of loop_filter_across_slices_enabled_flag is inferred to be equal to 0.

[0069] cabac_init_present_flag equal to 1 specifies that cabac_init_flag is present in the slice header referencing the PPS. cabac_init_present_flag equal to 0 specifies that cabac_init_flag is not present in the slice header referencing the PPS. num_ref_idx_default_active_minus1[i]+1 equal to 0 specifies the inferred value of the variable NumRefIdxActive[0] for P or B slices as num_ref_idx_active_override_flag=0 when i is equal to 0, and num_ref_idx_active_override_flag equal to 0 specifies the inferred value of the variable NumRefIdxActive[1] for B slices as num_ref_idx_active_override_flag=0 when i is equal to 1. The value of num_ref_idx_default_active_minus1[i] shall be in the range of 0 to 14. rpl1_idx_present_flag equal to 0 specifies that ref_pic_list_sps_flag[1] and ref_pic_list_idx[1] are not present in the PH syntax structure or slice header of a picture that references the PPS. rpl1_idx_present_flag equal to 1 specifies that ref_pic_list_sps_flag[1] and ref_pic_list_idx[1] may be present in the PH syntax structure or slice header of a picture that references the PPS.

[0070] init_qp_minus26+26 is the SliceQp for each slice that references the PPS Y Specifies the initial value of SliceQp Y The initial value of init_qp_minus26 shall be modified at the picture level when a non-zero value of ph_qp_delta is decoded, or at the slice level when a non-zero value of slice_qp_delta is decoded. The value of init_qp_minus26 shall be in the range of -(26+QpBdOffset) to +37.

[0071] cu_qp_delta_enabled_flag equal to 1 specifies that the ph_cu_qp_delta_subdiv_intra_slice and ph_cu_qp_delta_subdiv_inter_slice syntax elements may be present in PHs that reference a PPS, and cu_qp_delta_abs may be present in the transform unit syntax. cu_qp_delta_enabled_flag equal to 0 specifies that the ph_cu_qp_subdiv_intra_slice and ph_cu_qp_subdiv_inter_slice syntax elements are not present in PHs that reference a PPS, and cu_qp_delta_abs is not present in the transform unit syntax. pps_chroma_tool_offsets_present_flag equal to 1 specifies that chroma tool offset related syntax elements are present in the PPS RBSP syntax structure. pps_chroma_tool_offsets_present_flag equal to 0 specifies that chroma tool offset related syntax elements are present in the PPS RBSP syntax structure. If ChromaArrayType is equal to 0, the value of pps_chroma_tool_offsets_present_flag shall be equal to 0.

[0072] pps_cb_qp_offset, pps_cr_qp_offset are Qp' Cb , Qp' Cr The luminance quantization parameter Qp' used in the derivation of each of Y Specifies the offset to the pps_cb_qp_offset. The values ​​of pps_cb_qp_offset and pps_cr_qp_offset shall be in the range of -12 to +12. If ChromaArrayType is equal to 0, pps_cb_qp_offset and pps_cr_qp_offset shall not be used in the decoding process and the decoder shall ignore their values. If not present, the values ​​of pps_cb_qp_offset and pps_cr_qp_offset shall be inferred to be equal to 0.

[0073] pps_joint_cbcr_qp_offset_present_flag equal to 1 specifies that pps_joint_cbcr_qp_offset_value and joint_cbcr_qp_offset_list[i] are present in the PPSRBSP syntax structure. pps_joint_cbcr_qp_offset_present_flag equal to 0 specifies that pps_joint_cbcr_qp_offset_value and joint_cbcr_qp_offset_list[i] are not present in the PPSRBSP syntax structure. If ChromaArrayType is 0 or sps_joint_cbcr_enabled_flag is equal to 0, the value of pps_joint_cbcr_qp_offset_present_flag shall be equal to 0. If not present, the value of pps_joint_cbcr_qp_offset_present_flag is inferred. pps_joint_cbcr_qp_offset_value is Qp' CbCr The luminance quantization parameter Qp' used to derive Y The value of pps_joint_cbcr_qp_offset_value shall be in the range of -12 to 12. If ChromaArrayType is equal to 0 or sps_joint_cbcr_enabled_flag is equal to 0, pps_joint_cbcr_qp_offset_value shall not be used in the decoding process and its value shall be ignored by the decoding module. If pps_joint_cbcr_qp_offset_present_flag is equal to 0, pps_joint_cbcr_qp_offset_value is not present and is inferred to be equal to 0.

[0074] pps_slice_chroma_qp_offsets_present_flag equal to 1 specifies that the slice_cb_qp_offset and slice_cr_qp_offset syntax elements are present in the associated slice header. pps_slice_slice_chroma_qp_offsets_present_flag equal to 0 specifies that the slice_cb_qp_offset and slice_cr_qp_offset syntax elements are not present in the associated slice header. If not present, the value of pps_slice_chroma_qp_offsets_present_flag is inferred. pps_cu_chroma_qp_offset_list_enabled_flag equal to 1 specifies that the ph_cu_chroma_qp_offset_subdiv_intra_slice and ph_cu_chroma_qp_offset_subdiv_inter_slice syntax elements are present in the PH that references the PPS, and cu_chroma_qp_offset_flag may also be present in the transform unit syntax and palette coding syntax. pps_cu_chroma_qp_list_enabled_flag equal to 0 specifies that the ph_cu_chroma_qp_offset_subdiv_intra_slice and ph_cu_chroma_qp_offset_subdiv_inter_slice syntax elements are not present in the PH that references the PPS, and cu_chroma_qp_offset_flag is not present in the transform unit syntax and palette coding syntax. If not present, the value of pps_cu_chroma_qp_offset_list_enabled_flag is inferred to be equal to 0.

[0075] chroma_qp_offset_list_len_minus1+1 specifies the number of syntax elements of cb_qp_offset_list[i], cr_qp_offset_list[i], and joint_cbcr_qp_offset_list[i] included in the PPS RBSP syntax structure. The value of chroma_qp_offset_list_len_minus1 shall be in the range of 0 to 5. cb_qp_offset_list[i], cr_qp_offset_list[i], and joint_cbcr_qp_offset_list[i] are the offsets of Qp' Cb、 Qp' Cr、 Qp' CbCr Specifies the offsets to be used in the derivation of each of the above. The values ​​of cb_qp_offset_list[i], cr_qp_offset_list[i], and joint_cbcr_qp_offset_list[i] shall be in the range of -12 to +12. If pps_joint_cbcr_qp_offset_present_flag is equal to 0, joint_cbcr_qp_offset_list[i] does not exist and is inferred to be equal to 0.

[0076] pps_weighted_pred_flag equal to 0 specifies that weighted prediction is not applied to P slices referencing the PPS. pps_weighted_pred_flag equal to 1 specifies that weighted prediction is applied to P slices referencing the PPS. If sps_weighted_pred_flag is equal to 0, the value of pps_weighted_pred_flag shall be equal to 0. pps_weighted_bipred_flag equal to 0 specifies that explicit weighted prediction is not applied to B slices referencing a PPS. pps_weighted_bipred_flag equal to 1 specifies that explicit weighted prediction is applied to B slices referencing a PPS. If sps_weighted_bipred_flag is equal to 0, the value of pps_weighted_bipred_flag shall be equal to 0.

[0077] deblocking_filter_control_present_flag equal to 1 specifies the presence of a deblocking filter control syntax element in the PPS. deblocking_filter_control_present_flag equal to 0 specifies the absence of a deblocking filter control syntax element in the PPS. A deblocking_filter_override_enabled_flag equal to 1 specifies the presence of ph_deblocking_filter_override_flag in PHs referencing the PPS and specifies the presence of slice_deblocking_filter_override_flag in slice headers referencing the PPS. A deblocking_filter_override_enabled_flag equal to 0 specifies the absence of ph_deblocking_filter_override_flag in PHs referencing the PPS and specifies the absence of slice_deblocking_filter_override_flag in slice headers referencing the PPS. If not present, the value of deblocking_filter_override_enabled_flag equal to 0 is inferred. pps_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is not applied to slices that refer to PPSs for which slice_deblocking_filter_disabled_flag is not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is applied to slices that refer to PPSs for which slice_deblocking_filter_disabled_flag is not present. If not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0.

[0078] pps_beta_offset_div2 and pps_tc_offset_div2 specify the default deblocking parameter offsets (divided by 2) for β and tC to be applied to the luma component of a slice referencing the PPS, unless the default deblocking parameter offset is overridden by a deblocking parameter offset present in the picture header or slice header of the slice referencing the PPS. The values ​​of pps_beta_offset_div2 and pps_tc_offset_div2 shall both be in the range of -12 to 12. If not present, the values ​​of pps_beta_offset_div2 and pps_tc_offset_div2 are both inferred to be equal to 0. pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 specify the default deblocking parameter offsets (divided by 2) for β and tC that apply to the Cb component of a slice that references the PPS, unless the default deblocking parameter offsets are overridden by a deblocking parameter offset present in the picture header or slice header of the slice that references the PPS. The values ​​of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 shall both be in the range of -12 to +12. If not present, the values ​​of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are inferred to be equal to 0. pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 specify the default deblocking parameter offsets (divided by 2) for β and tC that apply to the Cr component of a slice that references the PPS, unless the default deblocking parameter offsets are overridden by a deblocking parameter offset present in the picture header or slice header of the slice that references the PPS. The values ​​of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 shall both be in the range of -12 to +12. If not present, the values ​​of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are inferred to be equal to 0.

[0079] rpl_info_in_ph_flag equal to 1 specifies that reference picture list information is present in PH syntax structures and not present in slice headers referencing PPSs that do not contain PH syntax structures. rpl_info_in_ph_flag equal to 0 specifies that reference picture list information is not present in PH syntax structures and may be present in slice headers referencing PPSs that do not contain PH syntax structures. dbf_info_in_ph_flag equal to 1 specifies that deblocking filter information is present in the PH syntax structure and is not present in slice headers that reference PPSs that do not contain a PH syntax structure. dbf_info_in_ph_flag equal to 0 specifies that deblocking filter information is not present in the PH syntax structure and may be present in slice headers that reference PPSs that do not contain a PH syntax structure. If not present, the value of dbf_info_in_ph_flag is inferred to be equal to 0. sao_info_in_ph_flag equal to 1 specifies that SAO filter information is present in the PH syntax structure and is not present in slice headers that reference PPSs that do not contain a PH syntax structure. sao_info_in_ph_flag equal to 0 specifies that SAO filter information is not present in the PH syntax structure and may be present in slice headers that reference PPSs that do not contain a PH syntax structure.

[0080] alf_info_in_ph_flag equal to 1 specifies that ALF information is present in the PH syntax structure and is not present in slice headers that reference PPSs that do not contain a PH syntax structure. alf_info_in_ph_flag equal to 0 specifies that ALF information is not present in the PH syntax structure and may be present in slice headers that reference PPSs that do not contain a PH syntax structure. wp_info_in_ph_flag equal to 1 specifies that weighted prediction information may be present in the PH syntax structure and may not be present in slice headers that reference PPSs that do not contain a PH syntax structure. wp_info_in_ph_flag equal to 0 specifies that weighted prediction information is not present in the PH syntax structure and may be present in slice headers that reference PPSs that do not contain a PH syntax structure. If not present, the value of wp_info_in_ph_flag is inferred to be equal to 0. qp_delta_info_in_ph_flag equal to 1 specifies that QP delta information is present in the PH syntax structure and is not present in slice headers referencing PPSs that do not contain a PH syntax structure. qp_delta_info_in_ph_flag equal to 0 specifies that QP delta information is not present in the PH syntax structure and may be present in slice headers referencing PPSs that do not contain a PH syntax structure. pps_ref_wraparound_enabled_flag equal to 1 specifies that horizontal wraparound motion compensation is applied in inter prediction. pps_ref_wraparound_enabled_flag equal to 0 specifies that horizontal wraparound motion compensation is applied. If the value of CtbSizeY / MinCbSizeY+1 is greater than pic_width_in_luma_samples / MinCbSizeY-1, the value of pps_ref_wraparound_enabled_flag shall be equal to 0. If sps_ref_wraparound_enabled_flag is equal to 0, the value of pps_ref_wraparound_enabled_flag shall be equal to 0.

[0081] pps_ref_wraparound_offset+(CtbSizeY / MinCbSizeY)+2 specifies the offset, in units of MinCbSizeY luma samples, used to calculate the horizontal wraparound position. The value of pps_ref_wraparound_offset shall be in the range 0 to (pic_width_in_luma_samples / MinCbSizeY)-(CtbSizeY / MinCbSizeY)-2. The variable PpsRefWraparoundOffset is set equal to pps_ref_wraparound_offset+(CtbSizeY / MinCbSizeY)+2.

[0082] picture_header_extension_present_flag equal to 0 specifies that the PH extension syntax element is not present in the PH that references the PPS. picture_header_extension_present_flag equal to 1 specifies that the PH extension syntax element is present in the PHs that reference the PPS. picture_header_extension_present_flag shall be equal to 0 in bitstreams conforming to this version of this specification. slice_header_extension_present_flag equal to 0 specifies that the slice header extension syntax element is not present in the slice header of the coded picture that references the PPS. slice_header_extension_present_flag equal to 1 specifies that the slice header extension syntax element is present in the slice header of the coded picture that references the PPS. slice_header_extension_present_flag shall be equal to 0 in bitstreams conforming to this version of this specification. pps_extension_flag equal to 0 specifies that the PPS RBSP syntax structure does not include the pps_extension_data_flag syntax element. pps_extension_flag equal to 1 specifies that the PPS RBSP syntax structure includes the pps_extension_data_flag syntax element.

[0083] pps_extension_data_flag can have any value. Its presence and value do not affect a decoder's conformance to the features specified in this specification version. Decoders conforming to this specification version must ignore all pps_extension_data_flag syntax elements.

[0084] 3.2. APS Syntax and Semantics In the latest VVC draft text, the APS syntax and semantics are as follows:

[0085] [Table 7]

[0086] The APS RBSP contains the ALF syntax structure, alf_data().

[0087] [Table 8] [Table 9] [Table 10]

[0088] The APS RBSP contains the LMCS syntax structure, lmcs_data().

[0089] [Table 11]

[0090] The APS RBSP includes a syntax structure for scaling list data, namely scaling_list_data().

[0091] [Table 12] [Table 13]

[0092] Each APS RBSP shall be available to the decoding process before it is referenced, contained within at least one AU with a TemporalId less than or equal to the TemporalId of the coded slice NAL unit that references it, or provided through external means. All APS NAL units with a particular value of adaptation_parameter_set_id and with a particular value of aps_params_type within a PU shall have the same content, regardless of whether they are prefix or suffix APS NAL units.

[0093] The adaptation_parameter_set_id provides an identifier for the APS to which other syntax elements refer. If aps_params_type is equal to ALF_APS or SCALING_APS, the value of adaptation_parameter_set_id shall be in the range 0 to 7. If aps_params_type is equal to LMCS_APS, the value of adaptation_parameter_set_id shall be in the range of 0 to 3. Let apsLayerId be the value of nuh_layer_id of a particular APS NAL unit, and vclLayerId be the value of nuh_layer_id of a particular VCL NAL unit. A particular VCL NAL unit shall not reference a particular APS NAL unit unless apsLayerId is less than or equal to vclLayerId and the layer whose nuh_layer_id equals apsLayerId is included in at least one OLS that contains a layer whose nuh_layer_id equals vclLayerId. aps_params_type specifies the type of APS parameters implemented in the APS, as shown in Table 6.

[0094] [Table 14]

[0095] All APS NAL units with a particular value of aps_params_type share the same value space for adaptation_parameter_set_id, regardless of the value of nuh_layer_id. APS NAL units with different values ​​of aps_params_type use distinct value spaces for adaptation_parameter_set_id.

[0096] NOTE 1 - APS NAL units (with specific values ​​of adaptation_parameter_set_id and specific values ​​of aps_params_type) may be shared between pictures, and different slices within a picture may reference different ALF APSs. NOTE 2 - The suffix APS NAL unit associated with a particular VCL NAL unit (which precedes the suffix APS NAL unit in decoding order) is not used by the particular VCL NAL unit, but is used by the VCL NAL unit that follows the suffix APS NAL unit in decoding order.

[0097] aps_extension_flag equal to 0 specifies that the APS RBSP syntax structure does not include the aps_extension_data_flag syntax element. aps_extension_flag equal to 1 specifies that the APS RBSP syntax structure does include the aps_extension_data_flag syntax element. aps_extension_data_flag can have any value. Its presence and value do not affect a decoder's conformance to the features specified in this specification version. Decoders conforming to this specification version must ignore all aps_extension_data_flag syntax elements.

[0098] alf_luma_filter_signal_flag equal to 1 indicates that the luma filter set is signaled. alf_luma_filter_signal_flag equal to 0 indicates that the luma filter set is not signaled. alf_chroma_filter_signal_flag equal to 1 indicates that the chroma filter is signaled. alf_chroma_filter_signal_flag equal to 0 indicates that the chroma filter is not signaled. If ChromaArrayType is equal to 0, then alf_chroma_filter_signal_flag shall be equal to 0. At least one of the values ​​of alf_luma_filter_signal_flag, alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, and alf_cc_cr_filter_signal_flag shall be equal to 1.

[0099] The variable NumAlfFilters, which defines the number of different adaptive loop filters, is set to 25. alf_luma_clip_flag equal to 0 specifies that linear adaptive loop filtering is applied to the luma component. alf_luma_clip_flag equal to 1 specifies that non-linear adaptive loop filtering may be applied to the luma component. alf_luma_num_filters_signalled_minus1+1 specifies the number of adaptive loop filter classes that can signal luma coefficients. The value of alf_luma_num_filters_signalled_minus1 shall be in the range of 0 to NumAlfFilters-1.

[0100] alf_luma_coeff_delta_idx[filtIdx] specifies the index of the signaled adaptive loop filter brightness coefficient delta, ranging from 0 to NumAlfFilters-1, for the filter class indicated by filtIdx. If alf_luma_coeff_delta_idx[filtIdx] is not present, it is inferred to be equal to 0. The length of alf_luma_coeff_delta_idx[filtIdx] is Ceil(Log2(alf_luma_num_filters_signalled_minus1+1) bits. The value of alf_luma_coeff_delta_idx[filtIdx] shall be in the range 0 to alf_luma_num_filters_signalled_minus1. alf_luma_coeff_abs[sfIdx][j] specifies the absolute value of the jth coefficient of the signal luminance filter indicated by sfIdx. If alf_luma_coeff_abs[sfIdx][j] is not present, it is inferred to be equal to 0. The value of alf_luma_coeff_abs[sfIdx][j] shall be in the range from 0 to 128.

[0101] alf_luma_coeff_sign[sfIdx][j] specifies the sign of the j-th luminance coefficient of the filter indicated by sfIdx as follows: If alf_luma_coeff_sign[sfIdx][j] is equal to 0, the corresponding luma filter coefficient has a positive value. Otherwise (alf_luma_coeff_sign[sfIdx][j] equals 1), the corresponding luma filter coefficient has a negative value. If alf_luma_coeff_sign[sfIdx][j] is not present, it is inferred to be equal to 0.

[0102] The variable filtCoeff[sfIdx][j], with sfIdx=0..alf_luma_num_filters_signalled_minus1,j=0..11, is initialized as follows: filtCoeff[sfIdx][j]=alf_luma_coeff_abs[sfIdx][j]* (1-2*alf_luma_coeff_sign[sfIdx][j]) (93)

[0103] Element AlfCoeff L Luminance filter coefficient AlfCoeff with [adaptation_parameter_set_id][filtIdx][j] L [adaptation_parameter_set_id] (where filtIdx=0..NumAlfFilters-1, j=0..11) is derived as follows: AlfCoeff L [adaptation_parameter_set_id][filtIdx][j]=filtCoeff[alf_luma_coeff_delta_idx[filtIdx]][j] (94)

[0104] The classes for filter mapping the fixed filter coefficients AlfFixFiltCoeff[i][j] (where i=0..64, j=0..11) and AlfClassToFiltMap[m][n] (where m=0..15, n=0..24) are derived as follows: AlfFixFiltCoeff= (95) { {0,0,2,-3,1,-4,1,7,-1,1,-1,5} {0,0,0,0,0,-1,0,1,0,0,-1,2} {0,0,0,0,0,0,0,1,0,0,0,0} {0,0,0,0,0,0,0,0,0,0,0,-1,1} {2,2,-7,-3,0,-5,13,22,12,-3,-3,17} {-1,0,6,-8,1,-5,1,23,0,2,-5,10} {0,0,-1,-1,0,-1,2,1,0,0,-1,4} {0,0,3,-11,1,0,-1,35,5,2,-9,9} {0,0,8,-8,-2,-7,4,4,2,1,-1,25} {0,0,1,-1,0,-3,1,3,-1,1,-1,3} {0,0,3,-3,0,-6,5,-1,2,1,-4,21} {-7,1,5,4,-3,5,11,13,12,-8,11,12} {-5,-3,6,-2,-3,8,14,15,2,-7,11,16} {2,-1,-6,-5,-2,-2,20,14,-4,0,-3,25} {3,1,-8,-4,0,-8,22,5,-3,2,-10,29} {2,1,-7,-1,2,-11,23,-5,0,2,-10,29} {-6,-3,8,9,-4,8,9,7,14,-2,8,9} {2,1,-4,-7,0,-8,17,22,1,-1,-4,23} {3,0,-5,-7,0,-7,15,18,-5,0,-5,27} {2,0,0,-7,1,-10,13,13,-4,2,-7,24} {3,3,-13,4,-2,-5,9,21,25,-2,-3,12} {-5,-2,7,-3,-7,9,8,9,16,-2,15,12} {0,-1,0,-7,-5,4,11,11,8,-6,12,21} {3,-2,-3,-8,-4,-1,16,15,-2,-3,3,26} {2,1,-5,-4,-1,-8,16,4,-2,1,-7,33} {2,1,-4,-2,1,-10,17,-2,0,2,-11,33} {1,-2,7,-15,-16,10,8,8,20,11,14,11} {2,2,3,-13,-13,4,8,12,2,-3,16,24} {1,4,0,-7,-8,-4,9,9,-2,-2,8,29} {1,1,2,-4,-1,-6,6,3,-1,-1,-3,30} {-7,3,2,10,-2,3,7,11,19,-7,8,10} {0,-2,-5,-3,-2,4,20,15,-1,-3,-1,22} {3,-1,-8,-4,-1,-4,22,8,-4,2,-8,28} {0,3,-14,3,0,1,19,17,8,-3,-7,20} {0,2,-1,-8,3,-6,5,21,1,1,-9,13} {-4,-2,8,20,-2,2,3,5,21,4,6,1} {2,-2,-3,-9,-4,2,14,16,3,-6,8,24} {2,1,5,-16,-7,2,3,11,15,-3,11,22} {1,2,3,-11,-2,-5,4,8,9,-3,-2,26} {0,-1,10,-9,-1,-8,2,3,4,0,0,29} {1,2,0,-5,1,-9,9,3,0,1,-7,20} {-2,8,-6,-4,3,-9,-8,45,14,2,-13,7} {1,-1,16,-19,-8,-4,-3,2,19,0,4,30} {1,1,-3,0,2,-11,15,-5,1,2,-9,24} {0,1,-2,0,1,-4,4,0,0,1,-4,7} {0,1,2,-5,1,-6,4,10,-2,1,-4,10} {3,0,-3,-6,-2,-6,14,8,-1,-1,-3,31} {0,1,0,-2,1,-6,5,1,0,1,-5,13} {3,1,9,-19,-21,9,7,6,13,5,15,21} {2,4,3,-12,-13,1,7,8,3,0,12,26} {3,1,-8,-2,0,-6,18,2,-2,3,-10,23} {1,1,-4,-1,1,-5,8,1,-1,2,-5,10} {0,1,-1,0,0,-2,2,0,0,1,-2,3} {1,1,-2,-7,1,-7,14,18,0,0,-7,21} {0,1,0,-2,0,-7,8,1,-2,0,-3,24} {0,1,1,-2,2,-10,10,0,-2,1,-7,23} {0,2,2,-11,2,-4,-3,39,7,1,-10,9} {1,0,13,-16,-5,-6,-1,8,6,0,6,29} {1,3,1,-6,-4,-7,9,6,-3,-2,3,33} {4,0,-17,-1,-1,5,26,8,-2,3,-15,30} {0,1,-2,0,2,-8,12,-6,1,1,-6,16} {0,0,0,-1,1,-4,4,0,0,0,-3,11} {0,1,2,-8,2,-6,5,15,0,2,-7,9} {1,-1,12,-15,-7,-2,3,6,6,-1,7,30} }, AlfClassToFiltMap= (96) { {8,2,2,2,3,4,53,9,9,52,4,4,5,9,2,8,10,9,1,339,39,10,9,52} {11,12,13,14,15,30,11,17,18,19,16,20,20,4,53,21,22,23,14,25,26,26,27,28,10} {16,12,31,32,14,16,30,33,53,34,35,16,20,4,7,16,21,36,18,19,21,26,37,38,39} {35,11,13,14,43,35,16,4,34,62,35,35,30,56,7,35,21,38,24,40,16,21,48,57,39} {11,31,32,43,44,16,4,17,34,45,30,20,20,7,5,21,22,46,40,47,26,48,63,58,10} {12,13,50,51,52,11,17,53,45,9,30,4,53,19,0,22,23,25,43,44,37,27,28,10,55} {30,33,62,51,44,20,41,56,34,45,20,41,41,56,5,30,56,38,40,47,11,37,42,57,8} {35,11,23,32,14,35,20,4,17,18,21,20,20,20,4,16,21,36,46,25,41,26,48,49,58} {12,31,59,59,3,33,33,59,59,52,4,33,17,59,55,22,36,59,59,60,22,36,59,25,55} {31,25,15,60,60,22,17,19,55,55,20,20,53,19,55,22,46,25,43,60,37,28,10,55,52} {12,31,32,50,51,11,33,53,19,45,16,4,4,53,5,22,36,18,25,43,26,27,27,28,10} {5,2,44,52,3,4,53,45,9,3,4,56,5,0,2,5,10,47,52,3,63,39,10,9,52} {12,34,44,44,3,56,56,62,45,9,56,56,7,5,0,22,38,40,47,52,48,57,39,10,9} {35,11,23,14,51,35,20,41,56,62,16,20,41,56,7,16,21,38,24,40,26,26,42,57,39} {33,34,51,51,52,41,41,34,62,0,41,41,56,7,5,56,38,38,40,44,37,42,57,39,10} {16,31,32,15,60,30,4,17,19,25,22,20,4,53,19,21,22,46,25,55,26,48,63,58,55} },

[0105] AlfCoeff L The value of [adaptation_parameter_set_id][filtIdx][j] (where filtIdx=0..NumAlfFilters-1, j=0..11) is -2 7 ~2 7 Being in the range of -1 is a bitstream conformance requirement. alf_luma_clip_idx[sfIdx][j] specifies the clipping index of the clipping value to be used before multiplying by the jth coefficient of the signaled luma filter indicated by sfIdx. The value of alf_luma_clip_idx[sfIdx][j] (where sfIdx=0..alf_luma_num_filters_signalled_minus1 and j=0..11) must be in the range 0..3 for bitstream conformance.

[0106] Element AlfClip L Luminance filter clipping value AlfClip with [adaptation_parameter_set_id][fltIdx][j] (where filtIdx=0..NumAlfFilters-1, j=0..11) L [adaptation_parameter_set_id] is derived as specified in Table 8 depending on BitDepth and clipIdx, which is set equal to alf_luma_clip_idx[alf_luma_coeff_delta_idx[filtIdx][j].

[0107] alf_chroma_clip_flag equal to 0 specifies that linear adaptive loop filtering is applied to the chroma component, and alf_chroma_clip_flag equal to 1 specifies that non-linear adaptive loop filtering is applied to the chroma component. If not present, alf_chroma_clip_flag is inferred to be equal to 0. alf_chroma_num_alt_filters_minus1plus1 specifies the number of alternative filters for the chroma component. The value of alf_chroma_num_alt_filters_minus1 must be in the range from 0 to 7. alf_chroma_coeff_abs[altIdx][j] specifies the absolute value of the jth chroma filter coefficient for the alternative chroma filter with index altIdx. If alf_chroma_coeff_abs[altIdx][j] is not present, it is inferred to be equal to 0. The value of alf_chroma_coeff_abs[sfIdx][j] shall be in the range from 0 to 128.

[0108] alf_chroma_coeff_sign[altIdx][j] specifies the sign of the j-th chroma filter coefficient of the alternative chroma filter with index altIdx as follows: - If alf_chroma_coeff_sign[altIdx][j] is equal to 0, the corresponding chroma filter coefficient has a positive value. - Otherwise (alf_chroma_coeff_sign[altIdx][j]=1), the corresponding chroma filter coefficient has a negative value. If alf_chroma_coeff_sign[altIdx][j] is not present, it is inferred to be equal to 0.

[0109] Element AlfCoeff CChroma filter coefficient AlfCoeff with [adaptation_parameter_set_id][altIdx][j] (where altIdx=0..alf_chroma_num_alt_filters_minus1, j=0..5) C [adaptation_parameter_set_id][altIdx] is derived as follows: AlfCoeff C [adaptation_parameter_set_id][altIdx][j]=alf_chroma_coeff_abs[altIdx][j]* (1-2*alf_chroma_coeff_sign[altIdx][j]) (97) AlfCoeff C [adaptation_parameter_set_id][altIdx][j] (where altIdx=0..alf_chroma_num_alt_filters_minus1,j=0..5) has a value of -2 7 -1~2 7 Being in the range of -1 is a requirement for bitstream conformance.

[0110] alf_cc_cb_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cb color component is signaled. alf_cc_cb_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cb color component is not signaled. If ChromaArrayType is equal to 0, then alf_cc_cb_filter_signal_flag shall be equal to 0. alf_cc_cb_filters_signalled_minus1plus1 specifies the number of cross-component filters for the Cb color components signaled in the current ALFAPS. The value of alf_cc_cb_filters_signalled_minus1 shall be in the range of 0 to 3. alf_cc_cb_mapped_coeff_abs[k][j] specifies the absolute value of the j-th mapped coefficient of the k-th cross-component filter signaled for the Cb color component. If alf_cc_cb_mapped_coeff_abs[k][j] is not present, it is inferred to be equal to 0.

[0111] alf_cc_cb_coeff_sign[k][j] specifies the sign of the j-th coefficient of the k-th cross-component filter signaled for the Cb color component as follows: If alf_cc_cb_coeff_sign[k][j] is equal to 0, the corresponding cross-component filter coefficient has a positive value. Otherwise (alf_cc_cb_sign[k][j] equals 1), the corresponding cross-component filter coefficient has a negative value.

[0112] If alf_cc_cb_coeff_sign[k][j] is not present, it is inferred to be equal to 0.

[0113] Cb color component CcAlfApsCoeff Cb The signed kth cross-component filter coefficient for [adaptation_parameter_set_id][k][j] (where j=0..6) is derived as follows: - If alf_cc_cb_mapped_coeff_abs[k][j] is equal to 0, then CcAlfApsCoeff Cb [adaptation_parameter_set_id][k][j] is set equal to 0. - If not, CcAlfApsCoeff Cb [adaptation_parameter_set_id][k][j] is 1-2*alf_cc_cb_coeff_sign[k][j])*2 alf_cc_cb_mapped_coeff_abs[k][j]-1 is set equal to

[0114] alf_cc_cr_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cr color component is signaled. alf_cc_cr_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cr color component is not signaled. If ChromaArrayType is equal to 0, then alf_cc_cr_filter_signal_flag shall be equal to 0. alf_cc_cr_filters_signalled_minus1+1 specifies the number of cross-component filters for the Cr color component signaled in the current ALFAPS. The value of alf_cc_cr_filters_signalled_minus1 shall be in the range of 0 to 3. alf_cc_cr_mapped_coeff_abs[k][j] specifies the absolute value of the j-th mapped coefficient of the k-th cross-component filter signaled for the Cr color component. If alf_cc_cr_mappedcoeff_abs[k][j] is not present, it is inferred to be equal to 0.

[0115] alf_cc_cr_coeff_sign[k][j] specifies the sign of the j-th coefficient of the k-th cross-component filter signaled for the Cr color component as follows: If alf_cc_cr_coeff_sign[k][j] is equal to 0, the corresponding cross-component filter coefficient has a positive value. otherwise (alf_cc_cr_sign[k][j]=1), the corresponding cross-component filter coefficients have negative values. If alf_cc_cr_coeff_sign[k][j] is not present, it is inferred to be equal to 0.

[0116] Cr color component CcAlfApsCoeff CrThe signed kth cross-component filter coefficient for [adaptation_parameter_set_id][k][j] (where j=0..6) is derived as follows: - If alf_cc_cr_mapped_coeff_abs[k][j] is equal to 0, then CcAlfApsCoeff Cr [adaptation_parameter_set_id][k][j] is set equal to 0. - If not, CcAlfApsCoeff Cr [adaptation_parameter_set_id][k][j] is (1-2*alf_cc_cr_coeff_sign[k][j])*2 alf_cc_cr_mapped_coeff_abs[k][j]-1 is set equal to

[0117] alf_chroma_clip_idx[altIdx][j] specifies the clipping index of the clipping value to use before multiplying by the jth coefficient of the alternative chroma filter with index altIdx. The value of alf_chroma_clip_idx[altIdx][j] (where altIdx=0..alf_chroma_num_alt_filters_minus1, j=0..5) must be in the range 0 to 3 for bitstream conformance.

[0118] Element AlfClip C Chroma filter clipping value AlfClip with [adaptation_parameter_set_id][altIdx][j] C [adaptation_parameter_set_id][altIdx], where altIdx=0.. alf_chroma_num_alt_filters_minus1, j=0..5, is derived as a function of BitDepth and clipIdx set equal to alf_chroma_clip_idx[altIdx][j] as specified in Table 8.

[0119] [Table 15]

[0120] lmcs_min_bin_idx indicates the minimum bin index used for luma mapping with the chroma scaling construction process. The value of lmcs_min_bin_idx should be in the range of 0 to 15, inclusive.

[0121] lmcs_delta_max_bin_idx indicates the delta value between 15 and the maximum bin index, LmcsMaxBinIdx, used for luma mapping with the chroma scaling construction process. The value of lmcs_delta_max_bin_idx should be in the range of 0 to 15. The value of LmcsMaxBinIdx is set equal to 15 - lmcs_delta_max_bin_idx. The value of LmcsMaxBinIdx should be greater than or equal to lmcs_min_bin_idx. lmcs_delta_cw_prec_minus1+1 indicates the number of bits used to represent the syntax lmcs_delta_abs_cw[i]. The value of lmcs_delta_cw_prec_minus1 should be in the range of 0 to BitDepth-2. lmcs_delta_abs_cw[i] denotes the absolute value of the delta codeword in the ith bin.

[0122] lmcs_delta_sign_cw_flag[i] indicates the sign of the variable lmcsDeltaCW[i] as follows: - If lmcs_delta_sign_cw_flag[i] is equal to 0, lmcsDeltaCW[i] is a positive value. - Otherwise (lmcs_delta_sign_cw_flag[i] is not equal to 0), lmcsDeltaCW[i] is a negative value. If lmcs_delta_sign_cw_flag[i] is not present, it is inferred to be equal to 0.

[0123] The variable OrgCW is derived as follows: OrgCW=(1< <BitDepth) / 16 (98)

[0124] The variable lmcsDeltaCW[i] (where i=lmcs_min_bin_idx..LmcsMaxBinIdx) is derived as follows. lmcsDeltaCW[i]=(1-2*lmcs_delta_sign_cw_flag[i])*lmcs_delta_abs_cw[i] (99)

[0125] The variable lmcsCW[i] is derived as follows: - For i=0..lmcs_min_bin_idx-1, lmcsCW[i] is set equal to 0. - For i=lmcs_min_bin_idx..LmcsMaxBinIdx, the following applies: lmcsCW[i]=OrgCW+lmcsDeltaCW[i] (100) The value of lmcsCW[i] should be in the range (OrgCW>>3) to (OrgCW<<3-1). - For i=LmcsMaxBinIdx+1..15, lmcsCW[i] is set to 0.

[0126] The requirements for bitstream conformance are that the following conditions are true:

[0127]

number

[0128] The variable InputPivot[i] is derived as follows, for i=0..16: InputPivot[i]=i*OrgCW (102)

[0129] The variable LmcsPivot[i] (where i=0..16) is derived as follows using the variables ScaleCoeff[i] and InvScaleCoeff[i] (where i=0..15): LmcsPivot[0]=0; for(i=0;i<=15;i++){ LmcsPivot[i+1]=LmcsPivot[i]+lmcsCW[i] ScaleCoeff[i]=(lmcsCW[i]*(1<<11)+(1<<(Log2(OrgCW)-1)))>>(Log2(OrgCW)) if(lmcsCW[i]==0) InvScaleCoeff[i]=0 else InvScaleCoeff[i]=OrgCW*(1<<11) / lmcsCW[i] } (103)

[0130] It is a bitstream compliance requirement that if the value of LmcsPivot[i] is not a multiple of 1<<(BitDepth-5), for i=lmcs_min_bin_idx..LmcsMaxBinIdx, then the value of (LmcsPivot[i]>>(BitDepth-5)) is not equal to the value of (LmcsPivot[i+1]>>(BitDepth-5)).

[0131] lmcs_delta_abs_crs specifies the absolute value of the codeword value of the variable lmcsDeltaCrs. The value of lmcs_delta_abs_crs should be in the range of 0 to 7. If not present, lmcs_delta_abs_crs is inferred to be equal to 0. lmcs_delta_sign_crs_flag specifies the sign of the variable lmcsDeltaCrs. If not present, lmcs_delta_sign_crs_flag is inferred to be equal to 0.

[0132] The variable lmcsDeltaCrs is derived as follows: lmcsDeltaCrs=(1-2*lmcs_delta_sign_crs_flag)*lmcs_delta_abs_crs (104)

[0133] If lmcsCW[i] is not equal to 0, it is a bitstream compliance requirement that (lmcsCW[i]+lmcsDeltaCrs) should be in the range (OrgCW>>3)~((OrgCW<<3)-1).

[0134] The variable ChromaScaleCoeff[i], for i=0...15, is derived as follows: if(lmcsCW[i]==0) ChromaScaleCoeff[i]=(1<<11) else ChromaScaleCoeff[i]=OrgCW*(1<<11) / (lmcsCW[i]+lmcsDeltaCrs)

[0135] scaling_matrix_for_lfnst_disabled_flag equal to 1 specifies that a scaling matrix is ​​not applied to LFNST coded blocks. scaling_matrix_for_lfnst_disabled_flag equal to 0 specifies that a scaling matrix can be applied to LFNST coded blocks. scaling_list_chroma_present_flag equal to 1 specifies that the chroma scaling list is present in scaling_list_data(). scaling_list_chroma_present_flag equal to 0 specifies that the chroma scaling list is not present in scaling_list_data(). It is a bitstream-compliant requirement that scaling_list_chroma_present_flag be equal to 0 if ChromaArrayType is equal to 0, and 1 if ChromaArrayType is not 0. scaling_list_copy_mode_flag[id] equal to 1 specifies that the values ​​of the scaling list are the same as the values ​​of the reference scaling list, which is specified by scaling_list_pred_id_delta[id]. If scaling_list_copy_mode_flag[id] equal to 0, it specifies that scaling_list_pred_mode_flag is present. scaling_list_pred_mode_flag[id] equal to 1 specifies that the values ​​of the scaling list can be predicted from the reference scaling list. scaling_list_pred_id_delta[id] specifies the reference scaling list. scaling_list_pred_mode_flag[id] equal to 0 specifies that the values ​​of the scaling list are explicitly signaled. If not present, the value of scaling_list_pred_mode_flag[id] is inferred to be equal to 0.

[0136] scaling_list_pred_id_delta[id] specifies the reference scaling list used to derive the predictive scaling matrix ScalingMatrixPred[id]. If not present, the value of scaling_list_pred_id_delta[id] is inferred to be equal to 0. The value of scaling_list_pred_id_delta[id] should be in the range 0 to maxIdDelta, where maxIdDelta is derived depending on id as follows: maxIdDelta=(id<2)?id:((id<8)?(id-2):(id-8)) (106)

[0137] The variables refId and matrixSize are derived as follows: refId=id-scaling_list_pred_id_delta[id] (107) matrixSize=(id<2)?2:((id<8)?4:8) (108)

[0138] The (matrixSize) x (matrixSize) array ScalingMatrixPred[x][y] (where x=0..matrixSize-1, y=0..matrixSize-1) and the variable ScalingMatrixDCPred are derived as follows. - When scaling_list_copy_mode_flag[id] and scaling_list_pred_mode_flag[id] are both equal to 0, all elements of ScalingMatrixPred are set equal to 8, and the value of ScalingMatrixDCPred is set equal to 8. Otherwise, when scaling_list_pred_id_delta[id] is equal to 0, all elements of ScalingMatrixPred are set equal to 16 and ScalingMatrixDCPred is set equal to 16. - Otherwise (if scaling_list_copy_mode_flag[id] or scaling_list_pred_mode_flag[id] is equal to 1 and scaling_list_pred_id_delta[id] is greater than 0), ScalingMatrixPred is set equal to ScalingMatrixRec[refId] and the following applies to ScalingMatrixDCPred: - If refId is greater than 13, ScalingMatrixDCPred is set equal to ScalingMatrixDCRec[refId-14]. - Otherwise (refId is less than or equal to 13), ScalingMatrixDCPred is set equal to ScalingMatrixPred[0][0].

[0139] If id is greater than 13, scaling_list_dc_coef[id-14] is used to derive the value of the variable ScalingMatrixDC[id-14]. ScalingMatrixDCRec[id-14]=(ScalingMatrixDCPred+scaling_list_dc_coef[id-14])&255 (109)

[0140] If not present, the value of scaling_list_dc_coef[id-14] is inferred to be 0. The value of scaling_list_dc_coef[id-14] must be between -128 and 127 inclusive. The value of ScalingMatrixDCRec[id-14] must be greater than 0.

[0141] scaling_list_delta_coef[id][i] specifies the difference between the current matrix coefficient ScalingList[id][i] and the previous matrix coefficient ScalingList[id][i-1] when scaling_list_copy_mode_flag[id] is equal to 0. The value of scaling_list_delta_coef[id][i] shall be between -128 and 127 inclusive. When scaling_list_copy_mode_flag[id] is equal to 1, all elements of ScalingList[id] are set equal to 0.

[0142] The (matrixSize) x (matrixSize) array ScalingMatrixRec[id] is derived as follows: ScalingMatrixRec[id][x][y]=(ScalingMatrixPred[x][y]+ScalingList[id][k])&255 (110) However, k=0..(matrixSize*matrixSize-1), x = DiagScanOrder[Log2(matrixSize)][Log2(matrixSize)][k][0], and y=DiagScanOrder[Log2(matrixSize)][Log2(matrixSize)][k][1] The value of ScalingMatrixRec[id][x][y] is greater than 0.

[0143] 3.3 PH Syntax and Semantics In the recent VVC draft text, the PH syntax and semantics are as follows:

[0144] [Table 16]

[0145] The PH RBSP contains the PH syntax structure, namely picture_header_structure().

[0146] [Table 17] [Table 18] [Table 19] [Table 20] [Table 21] [Table 22] [Table 23] [Table 24]

[0147] A PH syntax structure contains information that is common to all slices of the coded picture associated with the PH syntax structure.

[0148] gdr_or_irap_pic_flag equal to 1 specifies that the current picture is a GDR or IRAP picture. gdr_or_irap_pic_flag equal to 0 specifies that the current picture may or may not be a GDR or IRAP picture. gdr_pic_flag equal to 1 specifies that the picture associated with the PH is a GDR picture. gdr_pic_flag equal to 0 specifies that the picture associated with the PH is not a GDR picture. If not present, the value of gdr_pic_flag is inferred to be equal to 0. If gdr_enabled_flag is equal to 0, the value of gdr_pic_flag shall be equal to 0.

[0149] ph_inter_slice_allowed_flag equal to 0 specifies that all coded slices of the picture have slice_type 2. ph_inter_slice_allowed_flag equal to 1 specifies that a picture with slice_type equal to 0 or 1 may have one or more coded slices. ph_intra_slice_allowed_flag equal to 0 specifies that all coded slices of the picture have slice_type equal to 0 or 1. ph_intra_slice_allowed_flag equal to 1 specifies that the picture may have one or more coded slices with slice_type equal to 2. If not present, a value of ph_intra_slice_allowed_flag equal to 1 is inferred.

[0150] NOTE 1 - For bitstreams intended to perform sub-picture-based bitstream merging without the need to modify the PH NAL unit, the encoder is expected to set the values ​​of both ph_inter_slice_allowed_flag and ph_intra_slice_allowed_flag equal to 1.

[0151] non_reference_picture_flag equal to 1 specifies that the picture associated with the PH cannot be used as a reference picture. non_reference_picture_flag equal to 0 specifies that the picture associated with the PH may or may not be used as a reference picture.

[0152] The ph_pic_parameter_set_id specifies the value of the pps_pic_parameter_set_id of the PPS in use. The value of ph_pic_parameter_set_id is in the range of 0 to 63. It is a bitstream conformance requirement that when the value of TemporalId of PH is equal to ph_pic_parameter_set_id, the value of pps_pic_parameter_set_id shall be equal to or greater than the value of TemporalId of PPS. ph_pic_order_cnt_lsb specifies the picture order number modulo MaxPicOrderCntLsb of the current picture. The length of the ph_pic_order_cnt_lsb syntax element is log2_max_pic_order_cnt_lsb_minus4+4 bits. The value of ph_pic_order_cnt_lsb shall be in the range of 0 to MaxPicOrderCntLsb-1.

[0153] As specified in Annex C, no_output_of_prior_pics_flag affects the output of the previously decoded picture in the DPB after decoding a CLVSS picture that is not the first picture in the bitstream.

[0154] recovery_poc_cnt specifies the recovery point in output order of the decoded picture. If the current picture is a GDR picture associated with the PH, and there is a picture following the current GDR picture in decoding order in a CLVS with a PicOrderCntVal equal to the PicOrderCntVal of the current GDR picture plus the value of recovery_poc_cnt, then this picture picA is called the recovery point picture. Otherwise, the first picture in output order with a PicOrderCntVal greater than the PicOrderCntVal of the current picture plus the value of recovery_poc_cnt is called the recovery point picture. The recovery point picture shall not precede the current GDR picture in decoding order. The value of recovery_poc_cnt shall be in the range of 0 to MaxPicOrderCntLsb-1.

[0155] If the current picture is a GDR picture, the variable RpPicOrderCntVal is derived as follows: RpPicOrderCntVal=PicOrderCntVal+recovery_poc_cnt (82)

[0156] NOTE 2 - If gdr_enabled_flag is equal to 1 and the PicOrderCntVal of the current picture is greater than or equal to the RpPicOrderCntVal of the associated GDR picture, then the current and subsequent decoded pictures in output order exactly match the corresponding pictures produced by starting the decoding process from the previous IRAP picture (if any) that precedes the associated GDR picture in decoding order.

[0157] ph_extra_bit[i] may be equal to 1 or 0. Decoders conforming to this specification version must ignore the value of ph_extra_bit[i]. Its value does not affect the decoder's conformance to the features specified in this specification version.

[0158] ph_poc_msb_present_flag equal to 1 specifies that the syntax element poc_msb_val is present in PH. ph_poc_msb_present_flag equal to 0 specifies that the syntax element poc_msb_val is not present in PH. If vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is equal to 0 and there is a picture in the current AU of the current layer's reference layer, the value of ph_poc_msb_present_flag shall be equal to 0. poc_msb_val specifies the POC MSB value of the current picture. The length of the syntax element poc_msb_val is poc_msb_len_minus1+1 bits.

[0159] ph_alf_enabled_flag equal to 1 specifies that the adaptive loop filter is enabled for all slices associated with the PH and may be applied to the Y, Cb, or Cr color components in the slice. ph_alf_enabled_flag equal to 0 specifies that the adaptive loop filter may be disabled for one or more or all slices associated with the PH. If not present, ph_alf_enabled_flag is inferred to be equal to 0. ph_num_alf_aps_ids_luma specifies the number of ALFAPS referenced by the slice associated with the PH. ph_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALFAPS referenced by the luminance component of the slice associated with PH.

[0160] The value of alf_luma_filter_signal_flag of an APSNAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to ph_alf_aps_id_luma[i] shall be equal to 1. The TemporalId of an APSNAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the picture associated with the PH.

[0161] ph_alf_chroma_idc equal to 0 indicates that the adaptive loop filter is not applied to the Cb and Cr color components. ph_alf_chroma_idc equal to 1 indicates that the adaptive loop filter is applied to the Cb color component. ph_alf_chroma_idc equal to 2 indicates that the adaptive loop filter is applied to the Cr color component. ph_alf_chroma_idc equal to 3 indicates that the adaptive loop filter is applied to the Cb and Cr color components. If ph_alf_chroma_idc is not present, it is inferred to be equal to 0. ph_alf_aps_id_chroma specifies the adaptation_parameter_set_id of ALFAPS to which the chroma component of the slice associated with PH refers.

[0162] The value of alf_chroma_filter_signal_flag of an APSNAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_chroma shall be equal to 1. The TemporalId of an APSNAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_chroma shall be less than or equal to the TemporalId of the picture associated with PH.

[0163] ph_cc_alf_cb_enabled_flag equal to 1 specifies that the cross-component filter for the Cb color component may be enabled for all slices associated with the PH and may be applied to the Cb color component in the slice. ph_cc_alf_cb_enabled_flag equal to 0 specifies that the cross-component filter for the Cb color component may be disabled for one or more or all slices associated with the PH. If not present, ph_cc_alf_cb_enabled_flag is inferred to be equal to 0. ph_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id of the ALF APS referenced by the Cb color component of the slice associated with the PH.

[0164] The value of alf_cc_cb_filter_signal_flag shall be equal to 1 for APS NAL units whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to ph_cc_alf_cb_aps_id. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_cc_alf_cb_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0165] ph_cc_alf_cr_enabled_flag equal to 1 specifies that the cross-component filter for the Cr color component may be enabled for all slices associated with the PH and may be applied to the Cr color component in the slices. ph_cc_alf_cr_enabled_flag equal to 0 specifies that the cross-component filter for the Cr color component may be disabled for one or more or all slices associated with the PH. If not present, ph_cc_alf_cr_enabled_flag is inferred to be equal to 0. ph_cc_alf_cr_aps_id specifies the adaptation_parameter_set_id of the ALF APS referenced by the Cr color component of the slice associated with the PH.

[0166] The value of alf_cc_cr_filter_signal_flag shall be equal to 1 for APS NAL units whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to ph_cc_alf_cr_aps_id. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_cc_alf_cr_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0167] ph_lmcs_enabled_flag equal to 1 specifies that luma mapping with chroma scaling is enabled for all slices associated with the PH. ph_lmcs_enabled_flag equal to 0 specifies that luma mapping with chroma scaling is disabled for one or more or all slices associated with the PH. If not present, the value of ph_lmcs_enabled_flag is inferred to be equal to 0. ph_lmcs_aps_id specifies the adaptation_parameter_set_id of the LMCS APS referenced by the slice associated with the PH. The TemporalId of an APS NAL unit whose aps_params_type is equal to LMCS_APS and whose adaptation_parameter_set_id is ph_lmcs_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0168] ph_chroma_residual_scale_flag equal to 1 specifies that chroma residual scaling is enabled for all slices associated with the PH. ph_chroma_residual_scale_flag equal to 0 specifies that chroma residual scaling may be disabled for one or more, or all, slices associated with the PH. If ph_chroma_residual_scale_flag is not present, it is inferred to be equal to 0.

[0169] ph_scaling_list_present_flag equal to 1 specifies that the scaling list data used for the slice associated with the PH is derived based on the scaling list data contained in the reference scaling list APS. ph_scaling_list_present_flag equal to 0 specifies that the scaling list data used for the slice associated with the PH is set to 16. If not present, the value of ph_scaling_list_present_flag is inferred to be 0. ph_scaling_list_aps_id specifies the adaptation_parameter_set_id of the scaling list APS. The TemporalId of an APS NAL unit whose aps_params_type is equal to SCALING_APS and whose adaptation_parameter_set_id is ph_scaling_list_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0170] ph_virtual_boundaries_present_flag equal to 1 specifies that virtual boundary information is signaled in PH. ph_virtual_boundaries_present_flag equal to 0 specifies that virtual boundary information is not signaled in PH. If there are one or more virtual boundaries signaled in PH, in-loop filtering operations across the virtual boundaries are disabled in the picture. In-loop filtering operations include deblocking filter, sample adaptive offset filter, and adaptive loop filter operations. If not present, the value of ph_virtual_boundaries_present_flag is inferred to be 0.

[0171] If subpic_info_present_flag is equal to 1, it is a bitstream conformance requirement that the value of ph_virtual_boundaries_present_flag shall be equal to 0.

[0172] The variable VirtualBoundariesPresentFlag is derived as follows: VirtualBoundariesPresentFlag=0 if(sps_virtual_boundaries_enabled_flag) VirtualBoundariesPresentFlag=sps_virtual_boundaries_present_flag|| ph_virtual_boundaries_present_flag (83) ph_num_ver_virtual_boundaries specifies the number of ph_virtual_boundaries_pos_x[i] syntax elements present in PH. If ph_num_ver_virtual_boundaries is not present, it is inferred to be equal to 0.

[0173] The variable NumVerVirtualBoundaries is derived as follows: NumVerVirtualBoundaries=0 if(sps_virtual_boundaries_enabled_flag) NumVerVirtualBoundaries=sps_virtual_boundaries_present_flag? sps_num_ver_virtual_boundaries:ph_num_ver_virtual_boundaries (84) ph_virtual_boundaries_pos_x[i] specifies the position of the i-th vertical virtual boundary in units of luma samples divided by 8. The value of ph_virtual_boundaries_pos_x[i] shall be in the range of 1 to Ceil(pic_width_in_luma_samples÷8)-1.

[0174] Derive a list VirtualBoundariesPosX[i], for i from 0 to NumVerVirtualBoundaries-1, specifying the positions of the vertical virtual boundaries in units of luma samples as follows: for(i=0;i <NumVerVirtualBoundaries;i++) VirtualBoundariesPosX[i]=(sps_virtual_boundaries_present_flag? sps_virtual_boundaries_pos_x[i]:ph_virtual_boundaries_pos_x[i])*8 (85) The distance between any two vertical virtual boundaries shall be at least CtbSizeY luma samples.

[0175] ph_num_hor_virtual_boundaries specifies the number of ph_virtual_boundaries_pos_y[i] syntax elements present in PH. If ph_num_hor_virtual_boundaries is not present, it is inferred to be equal to 0.

[0176] The parameter NumHorVirtualBoundaries is derived as follows: NumHorVirtualBoundaries=0 if(sps_virtual_boundaries_enabled_flag) NumHorVirtualBoundaries=sps_virtual_boundaries_present_flag? sps_num_hor_virtual_boundaries:ph_num_hor_virtual_boundaries (86) If sps_virtual_boundaries_enabled_flag is equal to 1 and ph_virtual_boundaries_present_flag is equal to 1, the sum of ph_num_ver_virtual_boundaries and ph_num_hor_virtual_boundaries shall be greater than 0.

[0177] ph_virtual_boundaries_pos_y[i] specifies the position of the i-th horizontal virtual boundary in units of luma samples divided by 8. The value of ph_virtual_boundaries_pos_y[i] shall be in the range of 1 to Ceil(pic_height_in_luma_samples÷8)-1.

[0178] Derive a list VirtualBoundariesPosY[i], for i from 0 to NumHorVirtualBoundaries-1, specifying the positions of the horizontal virtual boundaries in units of luma samples as follows: for(i=0;i <NumHorVirtualBoundaries;i++) VirtualBoundariesPosY[i]=(sps_virtual_boundaries_present_flag? sps_virtual_boundaries_pos_y[i]:ph_virtual_boundaries_pos_y[i])*8 (87) The distance between any two horizontal virtual boundaries shall be at least CtbSizeY luminance samples.

[0179] pic_output_flag affects the output and deletion process of decoded pictures as specified in Annex C. If pic_output_flag is not present, it is inferred to be equal to 1.

[0180] partition_constraints_override_flag equal to 1 specifies that the partition constraint parameters are present in PH. partition_constraints_override_flag equal to 0 specifies that the partition constraint parameters are not present in PH. If not present, the value of partition_constraints_override_flag is inferred to be equal to 0.

[0181] ph_log2_diff_min_qt_min_cb_intra_slice_luma specifies the difference between the base 2 logarithm of the minimum size of luma samples of luma leaf blocks resulting from the quadtree decomposition of a CTU and the base 2 logarithm of the minimum coding block size of luma samples of luma CUs in slices with slice_type equal to 2(I) associated with PH. The value of ph_log2_diff_min_qt_min_cb_intra_slice_luma shall be in the range of 0 to CtbLog2SizeY-MinCbLog2SizeY. If not present, the value of ph_log2_diff_min_qt_min_cb_luma is inferred to be equal to sps_log2_diff_min_qt_min_cb_intra_slice_luma. ph_max_mtt_hierarchy_depth_intra_slice_luma specifies the maximum hierarchical depth of a coding unit resulting from a quadtree multi-type tree partitioning in slices where the slice_type associated with PH is 2(I). The value of ph_max_mtt_hierarchy_depth_intra_slice_luma shall be in the range of 0 to 2*(CtbLog2SizeY-MinCbLog2SizeY). If not present, the value of ph_max_mtt_hierarchy_depth_intra_slice_luma is inferred to be equal to sps_max_mtt_hierarchy_depth__intra_slice_luma.

[0182] ph_log2_diff_max_bt_min_qt_intra_slice_luma specifies the difference between the base 2 logarithm of the maximum size (width or height) of luma samples of a luma coding block that can be divided using binary division and the minimum size (width or height) of luma samples of a luma leaf block resulting from quadtree division of a CTU of a slice with slice_type equal to 2(I) associated with PH. The value of ph_log2_diff_max_bt_min_qt_intra_slice_luma shall be in the range of 0 to CtbLog2SizeY - MinQtLog2SizeIntraY. If not present, the value of ph_log2_diff_max_bt_min_qt_intra_slice_luma is inferred to be equal to sps_log2_diff_max_bt_min_qt_intra_slice_luma. ph_log2_diff_max_tt_min_qt_intra_slice_luma specifies the difference between the base 2 logarithm of the maximum size (width or height) of luma samples of a luma coding block that can be divided using 3-way division and the minimum size (width or height) of luma samples of a luma leaf block resulting from quadtree division of a CTU of a slice with slice_type equal to 2(I) associated with PH. The value of ph_log2_diff_max_tt_min_qt_intra_slice_luma shall be in the range of 0 to CtbLog2SizeY - MinQtLog2SizeIntraY. If not present, the value of ph_log2_diff_max_tt_min_qt_intra_slice_luma is inferred to be equal to sps_log2_diff_max_tt_min_qt_intra_slice_luma.

[0183] ph_log2_diff_min_qt_min_cb_intra_slice_chroma specifies the difference between the base 2 logarithm of the minimum size of luma samples in a chroma leaf block in a chroma CTU with treeType equal to DUAL_TREE_CHROMA, and the base 2 logarithm of the minimum coding block size of luma samples in a chroma CU with treeType equal to DUAL_TREE_CHROMA in a slice with slice_type equal to 2(I) associated with PH. The value of ph_log2_diff_min_qt_min_cb_intra_slice_chroma shall be in the range of 0 to CtbLog2SizeY - MinCbLog2SizeY. If not present, the value of ph_log2_diff_min_qt_min_cb_intra_slice_chroma is inferred to be equal to sps_log2_diff_min_qt_min_cb_chroma.

[0184] ph_max_mtt_hierarchy_depth_intra_slice_chroma specifies the maximum hierarchical depth of a chroma coding unit resulting from a multi-type quadtree of a chroma quadtree with a treeType of 2(I) where the slice_type associated with PH is DUAL_TREE_CHROMA. The value of ph_max_mtt_hierarchy_depth_intra_slice_chroma shall be in the range of 0 to 2*(CtbLog2SizeY-MinCbLog2SizeY). If not present, the value of ph_max_mtt_hierarchy_depth_intra_slice_chroma is inferred to be equal to sps_max_mtt_hierarchy_depth_intra_slice_chroma.

[0185] ph_log2_diff_max_bt_min_qt_intra_slice_chroma specifies the difference between the base 2 logarithm of the maximum size (width or height) of luma samples of a chroma coding block that can be split using binary splitting and the minimum size (width or height) of luma samples of a chroma leaf block that results from quadtree splitting of a chroma CTU with treeType equal to DUAL_TREE_CHROMA in a slice where the slice_type associated with PH is 2(I). The value of ph_log2_diff_max_bt_min_qt_intra_slice_chroma shall be in the range of 0 to CtbLog2SizeY - MinQtLog2SizeIntraC. If not present, the value of ph_log2_diff_max_bt_min_qt_intra_slice_chroma is inferred to be equal to sps_log2_diff_max_bt_min_qt_intra_slice_chroma. ph_log2_diff_max_tt_min_qt_intra_slice_chroma specifies the difference between the base 2 logarithm of the maximum size (width or height) of luma samples of a chroma coding block that can be divided using 3-way division and the minimum size (width or height) of luma samples of a chroma leaf block that results from quadtree division of a chroma CTU with treeType equal to DUAL_TREE_CHROMA in a slice where the slice_type associated with PH is 2(I). The value of ph_log2_diff_max_tt_min_qt_intra_slice_chroma shall be in the range 0 to CtbLog2SizeY - MinQtLog2SizeIntraC. If not present, the value of ph_log2_diff_max_tt_min_qt_intra_slice_chroma is inferred to be equal to sps_log2_diff_max_tt_min_qt_intra_slice_chroma.

[0186] ph_cu_qp_delta_subdiv_intra_slice specifies the maximum cbSubdiv value of coding units within an intra slice that conveys cu_qp_delta_abs and cu_qp_delta_sign_flag. The value of ph_cu_qp_delta_subdiv_intra_slice shall be within the range of 0 to 2*(CtbLog2SizeY-MinQtLog2SizeIntraY+ph_max_mtt_hierarchy_depth_intra_slice_luma). If not present, the value of ph_cu_qp_delta_subdiv_intra_slice is inferred to be equal to 0. ph_cu_chroma_qp_offset_subdiv_intra_slice specifies the maximum cbSubdiv value of a coding unit in an intra slice that conveys cu_chroma_qp_offset_flag. The value of ph_cu_qp_offset_subdiv_intra_slice shall be within the range of 0 to 2*(CtbLog2SizeY-MinQtLog2SizeIntraY+ph_max_mtt_hierarchy_depth_intra_slice_luma). If not present, the value of ph_cu_chroma_qp_offset_subdiv_intra_slice is inferred to be equal to 0.

[0187] ph_log2_diff_min_qt_min_cb_inter_slice specifies the difference between the base 2 logarithm of the minimum size of luma samples of a luma leaf block resulting from the quadtree decomposition of a CTU and the base 2 logarithm of the minimum luma coding block size of luma samples for a luma CU in a slice whose slice_type associated with PH is equal to 0 (B) or 1 (P). The value of ph_log2_diff_min_qt_min_cb_inter_slice shall be in the range of 0 to CtbLog2SizeY - MinCbLog2SizeY. If not present, the value of ph_log2_diff_min_qt_min_cb_luma is inferred to be equal to sps_log2_diff_min_qt_min_cb_inter_slice.

[0188] ph_max_mtt_hierarchy_depth_inter_slice specifies the maximum hierarchical depth of a coding unit in a multi-type tree of a leaf of a quadtree for slices with slice_type associated with PH equal to 0 (B) or 1 (P). The value of ph_max_mtt_hierarchy_depth_inter_slice shall be in the range of 0 to 2*(CtbLog2SizeY-MinCbLog2SizeY). If not present, the value of ph_max_mtt_hierarchy_depth_inter_slice is inferred to be equal to sps_max_mtt_hierarchy_depth_inter_slice.

[0189] ph_log2_diff_max_bt_min_qt_inter_slice specifies the difference between the base 2 logarithm of the maximum size (width or height) of luma samples of a luma coding block that can be divided using bisection and the minimum size (width or height) of luma samples of a luma leaf block that results from a quadtree division of a CTU in a slice that is 0 (B) or 1 (P) associated with PH. The value of ph_log2_diff_max_bt_min_qt_inter_slice shall be in the range of 0 to CtbLog2SizeY - MinQtLog2SizeInterY. If not present, the value of ph_log2_diff_max_bt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_bt_min_qt_inter_slice. ph_log2_diff_max_tt_min_qt_inter_slice specifies the difference between the base 2 logarithm of the maximum size (width or height) of luma samples of a luma coding block that can be divided using 3-way division and the minimum size (width or height) of luma samples of a luma leaf block that results from the quadtree division of a CTU in a slice that is 0 (B) or 1 (P) associated with PH. The value of ph_log2_diff_max_tt_min_qt_inter_slice shall be in the range 0 to CtbLog2SizeY - MinQtLog2SizeInterY. If not present, the value of ph_log2_diff_max_tt_min_qt_inter_slice is inferred to be equal to sps_log2_diff_max_tt_min_qt_inter_slice.

[0190] ph_cu_qp_delta_subdiv_inter_slice specifies the maximum cbSubdiv value of coding units in an inter-slice that carries cu_qp_delta_abs and cu_qp_delta_sign_flag. The value of ph_cu_qp_delta_subdiv_inter_slice shall be in the range of 0 to 2*(CtbLog2SizeY-MinQtLog2SizeInterY+ph_max_mtt_hierarchy_depth_inter_slice). If not present, the value of ph_cu_qp_delta_subdiv_inter_slice is inferred to be equal to 0.

[0191] ph_cu_chroma_qp_offset_subdiv_inter_slice specifies the maximum cbSubdiv value of a coding unit in an inter-slice that carries cu_chroma_qp_offset_flag. The value of ph_cu_chroma_qp_offset_subdiv_inter_slice shall be within the range of 0 to 2*(CtbLog2SizeY-MinQtLog2SizeInterY+ph_max_mtt_hierarchy_depth_inter_slice). If not present, the value of ph_cu_chroma_qp_offset_subdiv_inter_slice is inferred to be equal to 0.

[0192] ph_temporal_mvp_enabled_flag specifies whether a temporal motion vector predictor can be used for inter prediction of the slice associated with the PH. If ph_temporal_mvp_enabled_flag is equal to 0, the syntax elements of the slice associated with the PH shall be constrained so that a temporal motion vector predictor is not used for decoding the slice. Otherwise (if ph_temporal_mvp_enabled_flag is equal to 1), a temporal motion vector predictor may be used for decoding the slice associated with the PH. If not present, the value of ph_temporal_mvp_enabled_flag is inferred to be equal to 0. If the spatial resolution of the reference picture in the DPB is not the same as that of the current picture, the value of ph_temporal_mvp_enabled_flag shall be equal to 0.

[0193] The maximum number of subblock-based merge MVP candidates, MaxNumSubblockMergeCand, is derived as follows: if(sps_affine_enabled_flag) MaxNumSubblockMergeCand=5-five_minus_max_num_subblock_merge_cand else MaxNumSubblockMergeCand=sps_sbtmvp_enabled_flag&&ph_temporal_mvp_enable_flag (88) The value of MaxNumSubblockMergeCand is in the range of 0 to 5.

[0194] ph_collocated_from_I0_flag equal to 1 specifies that the co-located pictures used for temporal motion vector prediction are derived from reference picture list 0. ph_collocated_from_I0_flag equal to 0 specifies that the co-located pictures used for temporal motion vector prediction are derived from reference picture list 1. ph_collocated_ref_idx specifies the reference index of the co-located picture used for temporal motion vector prediction. If ph_collocated_from_l0_flag is equal to 1, ph_collocated_ref_idx refers to an entry in reference picture list 0, and the value of ph_collocated_ref_idx shall be in the range of 0 to num_ref_entries[0][RplsIdx[0]]-1. If ph_collocated_from_l0_flag is equal to 0, ph_collocated_ref_idx refers to an entry in reference picture list 1, and the value of ph_collocated_ref_idx shall be in the range of 0 to num_ref_entries[1][RplsIdx[1]]-1. If not present, the value of ph_collocated_ref_idx is inferred to be equal to 0.

[0195] mvd_l1_zero_flag equal to 1 indicates that the mvd_coding(x0,y0,1) syntax structure was not parsed and MvdL1[x0][y0][compIdx] and MvdCpL1[x0][y0][cpIdx][compIdx] are set to 0 for compIdx=0..1 and cpIdx=0..2. mvd_l1_zero_flag equal to 0 indicates that the mvd_coding(x0,y0,1) syntax structure was parsed.

[0196] ph_fpel_mmvd_enabled_flag equal to 1 specifies that merge mode with motion vector differences uses integer sample precision of the slice associated with PH. ph_fpel_mmvd_enabled_flag equal to 0 specifies that merge mode with motion vector differences uses fractional sample precision of the slice associated with PH. If not present, the value of ph_fpel_mmvd_enabled_flag is inferred to be 0.

[0197] ph_disable_bdof_flag equal to 1 specifies that bidirectional optical flow inter-prediction based inter bidirectional prediction is disabled in the slice associated with the PH. ph_disable_bdof_flag equal to 0 specifies that bidirectional optical flow inter-prediction based inter bidirectional prediction may or may not be enabled in the slice associated with the PH.

[0198] If ph_disable_bdof_flag is not present, the following applies: - If sps_bdof_enabled_flag is equal to 1, the value of ph_disable_bdof_flag is inferred to be equal to 0. - Otherwise (if sps_bdof_enabled_flag is equal to 0), the value of ph_disable_bdof_flag is inferred to be equal to 1. ph_disable_dmvr_flag equal to 1 specifies that decoder motion vector refinement-based inter bidirectional prediction is disabled in the slice associated with PH. ph_disable_dmvr_flag equal to 0 specifies that decoder motion vector refinement-based inter bidirectional prediction may or may not be enabled in the slice associated with PH.

[0199] If ph_disable_dmvr_flag is not present, the following applies: - If sps_dmvr_enabled_flag is equal to 1, the value of ph_disable_dmvr_flag is inferred to be equal to 0. - Otherwise (if sps_dmvr_enabled_flag is equal to 0), the value of ph_disable_dmvr_flag is inferred to be equal to 1. ph_disable_prof_flag equal to 1 specifies that optical flow prediction refinement is disabled for the slice associated with PH. ph_disable_prof_flag equal to 0 specifies that optical flow prediction refinement may or may not be enabled for the slice associated with PH.

[0200] If ph_disable_prof_flag is not present, the following applies: - If sps_affine_prof_enabled_flag is equal to 1, the value of ph_disable_prof_flag is inferred to be equal to 0. - Otherwise (if sps_affine_prof_enabled_flag is equal to 0), the value of ph_disable_prof_flag is inferred to be equal to 1.

[0201] ph_qp_delta is the Qp used for coding blocks in a picture until modified by the value of CuQpDeltaVal in the coding unit layer. YSpecifies the initial value of

[0202] If qp_delta_info_in_ph_flag is equal to 1, the Qp for all slices of the picture Y quantization parameter SliceQp Y The initial value of is derived as follows: SliceQp Y =26+init_qp_minus26+ph_qp_delta (89) SliceQp Y The value is in the range of -QpBdOffset to +63.

[0203] ph_joint_cbcr_sign_flag specifies whether the co-located residual samples of both chroma components have opposite signs for transform units where tu_joint_cbcr_residual_flag[x0][y0] is equal to 1. When tu_joint_cbcr_residual_flag[x0][y0] is equal to 1 for a transform unit, ph_joint_cbcr_sign_flag equal to 0 specifies that the sign of each residual sample of the Cr (or Cb) component is the same as the sign of the co-located Cb (or Cr) residual sample, and ph_joint_cbcr_sign_flag equal to 1 specifies that the sign of each residual sample of the Cr (or Cb) component is the opposite sign of the co-located Cb (or Cr) residual sample.

[0204] ph_sao_luma_enabled_flag equal to 1 specifies that SAO is enabled for the luma component in all slices associated with the PH, and ph_sao_luma_enabled_flag equal to 0 specifies that SAO for the luma component may be disabled for one or more or all slices associated with the PH. If ph_sao_luma_enabled_flag is not present, it is inferred to be equal to 0. ph_sao_chroma_enabled_flag equal to 1 specifies that SAO is enabled for the chroma component in all slices associated with the PH, and ph_sao_chroma_enabled_flag equal to 0 specifies that SAO for the luma component may be disabled for one or more or all slices associated with the PH. If ph_sao_chroma_enabled_flag is not present, it is inferred to be equal to 0.

[0205] ph_dep_quant_enabled_flag equal to 0 specifies that dependent quantization is disabled for the current picture. ph_dep_quant_enabled_flag equal to 1 specifies that dependent quantization is enabled for the current picture. If ph_dep_quant_enabled_flag is not present, it is inferred to be equal to 0.

[0206] pic_sign_data_hiding_enabled_flag equal to 0 specifies that sign bit hiding is disabled for the current picture. pic_sign_data_hiding_enabled_flag equal to 1 specifies that sign bit hiding is enabled for the current picture. If pic_sign_data_hiding_enabled_flag is not present, it is inferred to be equal to 0.

[0207] ph_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in PH. ph_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in PH. If not present, the value of ph_deblocking_filter_override_flag is inferred to be equal to 0. ph_deblocking_filter_disabled_flag equal to 1 specifies that the operation of a deblocking filter is not applied to the slice associated with the PH. ph_deblocking_filter_disabled_flag equal to 0 specifies that the operation of a deblocking filter is applied to the slice associated with the PH. If ph_deblocking_filter_disabled_flag is not present, it is inferred to be equal to pps_deblocking_filter_disabled_flag.

[0208] ph_beta_offset_div2 and ph_tc_offset_div2 specify the offset (divided by 2) of the β and tC deblocking parameters applied to the luma component of the slice associated with PH. The values ​​of ph_beta_offset_div2 and ph_tc_offset_div2 shall both be in the range of -12 to 12. If not present, the values ​​of ph_beta_offset_div2 and ph_tc_offset_div2 are inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively.

[0209] ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 specify the offset (divided by 2) of the β and tC deblocking parameters applied to the Cb component of the slice associated with PH. The values ​​of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 shall both be in the range of -12 to 12. If not present, the values ​​of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred to be equal to pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2, respectively. ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 specify the offset (divided by 2) of the beta and tc deblocking parameters applied to the Cr component of the slice associated with PH. The values ​​of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 shall both be in the range of -12 to 12. If not present, the values ​​of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred to be equal to pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2, respectively.

[0210] ph_extension_length specifies the length of the PH extension data in bytes, not including the bits used for signaling the ph_extension_length itself. The value of ph_extension_length is in the range 0 to 256. If not present, the value of ph_extension_length is inferred to be equal to 0. ph_extension_data_byte can have any value. Decoders conforming to this specification version must ignore the value of ph_extension_data_byte. The value does not affect the decoder's conformance to the features specified in this specification version.

[0211] 3.4 SH Syntax and Semantics In the recent VVC draft text, the SH syntax and semantics are as follows:

[0212] [Table 25] [Table 26] [Table 27] [Table 28] [Table 29] [Table 30]

[0213] The variable CuQpDeltaVal, which specifies the difference between the luma quantization parameter of the coding unit containing cu_qp_delta_abs and its predicted value, is set equal to 0. The quantization parameter Qp' of the coding unit containing cu_chroma_qp_offset_flag is set equal to 0. Cb ,Qp' Cr and Qp' CbCr The variable CuQpOffset specifies the value used to determine each value of Cb ,CuQpOffset Cr and CuQpOffset CbCr are all set equal to 0.

[0214] picture_header_in_slice_header_flag equal to 1 indicates that a PH syntax structure is present in the slice header. If picture_header_in_slice_header_flag is 0, a PH syntax structure is not present in the slice header. It is a bitstream conformance requirement that the value of picture_header_in_slice_header_flag shall be the same for all coded slices in a CLVS. It is a bitstream conformance requirement that if picture_header_in_slice_header_flag is equal to 1 for one coded slice, there shall be no VCL NAL units with nal_unit_type equal to PH_NUT in the CLVS. If picture_header_in_slice_header_flag is equal to 0, all coded slices in the current picture shall have picture_header_in_slice_header_flag equal to 0 and the current PU shall have a PHNAL unit.

[0215] slice_subpic_id specifies the subpicture ID of the subpicture that contains the slice. If slice_subpic_id is present, the value of the variable CurrSubpicIdx is derived such that SubpicIdVal[CurrSubpicIdx] is equal to slice_subpic_id. Otherwise (slice_subpic_id is not present), CurrSubpicIdx is derived to be equal to 0. The length of slice_subpic_id is sps_subpic_id_len_minus1+1 bits.

[0216] slice_address specifies the slice address of the slice. If not present, the value of slice_address is inferred to be equal to 0. When rect_slice_flag is 1 and NumSlicesInSubpic[CurrSubpicIdx] is 1, the value of slice_address is inferred to be 0.

[0217] If rect_slice_flag is equal to 0, the following applies: - The slice address is the raster scan tile index. - slice_address is Ceil(Log2(NumTilesInPic)) bits in length. - The value of slice_address should be in the range from 0 to NumTilesInPic-1. Otherwise (rect_slice_flag is equal to 1), the following applies: - The slice address is the sub-picture level slice index of the slice. - The length of slice_address is Ceil(Log2(NumSlicesInSubpic[CurrSubpicIdx])) bits. - The value of slice_address must be in the range of 0 to NumSlicesInSubpic[CurrSubpicIdx]-1.

[0218] The requirements for bitstream conformance are that the following constraints apply: - If rect_slice_flag is equal to 0 or subpic_info_present_flag is equal to 0, the value of slice_address must not be equal to the value of slice_address of any other coded slice NAL unit in the same coded picture. Otherwise, the pair of slice_subpic_id and slice_address values ​​must not be equal to the pair of slice_subpic_id and slice_address values ​​of any other coded slice NAL unit in the same coded picture. - The shape of a picture slice must be such that each CTU, when decoded, has its entire left boundary and its entire top boundary that contain the boundary of one picture or the boundary of the previously decoded CTU(s).

[0219] sh_extra_bit[i] may be equal to 1 or 0. Decoders conforming to this specification version must ignore the value of sh_extra_bit[i]. Its value does not affect the decoder's conformance to the features specified in this specification version.

[0220] num_tiles_in_slice_minus1+1, if present, specifies the number of tiles in the slice. The value of num_tiles_in_slice_minus1 should be in the range from 0 to NumTilesInPic-1. The variable NumCtusInCurrSlice, which specifies the number of CTUs in the current slice, and the list CtbAddrInCurrSlice[i], which specifies the picture raster scan address of the ith CTB in the slice, where i ranges from 0 to NumCTUsInCurrSlice-1, are derived as follows: if(rect_slice_flag){ picLevelSliceIdx=slice_address for(j=0;j <CurrSubpicIdx;j++) picLevelSliceIdx+=NumSlicesInSubpic[j] NumCtusInCurrSlice=NumCtusInSlice[picLevelSliceIdx] for(i=0;i <NumCtusInCurrSlice;i++) CtbAddrInCurrSlice[i]=CtbAddrInSlice[picLevelSliceIdx][i] }else{ NumCtusInCurrSlice=0 for(tileIdx=slice_address;tileIdx<=slice_address+num_tiles_in_slice_minus1;tileIdx++){ tileX=tileIdx%NumTileColumns tileY=tileIdx / NumTileColumns for(ctbY=tileRowBd[tileY];ctbY <tileRowBd[tileY+1];ctbY++){ for(ctbX=tileColBd[tileX];ctbX <tileColBd[tileX+1];ctbX++){ CtbAddrInCurrSlice[NumCtusInCurrSlice]=ctbY*PicWidthInCtb+ctbX NumCtusInCurrSlice++ }} } } (117)

[0221] The variables SubpicLeftBoundaryPos, SubpicTopBoundaryPos, SubpicRightBoundaryPos, and SubpicBotBoundaryPos are derived as follows: if(subpic_treated_as_pic_flag[CurrSubpicIdx]){ SubpicLeftBoundaryPos=subpic_ctu_top_left_x[CurrSubpicIdx]*CtbSizeY SubpicRightBoundaryPos=Min(pic_width_max_in_luma_samples-1, (subpic_ctu_top_left_x[CurrSubpicIdx]+ subpic_width_minus1[CurrSubpicIdx]+1)*CtbSizeY-1) SubpicTopBoundaryPos=subpic_ctu_top_left_y[CurrSubpicIdx]*CtbSizeY SubpicBotBoundaryPos=Min(pic_height_max_in_luma_samples-1, (subpic_ctu_top_left_y[CurrSubpicIdx]+ subpic_height_minus1[CurrSubpicIdx]+1)*CtbSizeY-1) } (118)

[0222] slice_type specifies the coding type of the slice according to Table 9.

[0223] [Table 31]

[0224] If not present, the value of slice_type is inferred to be equal to 2. If ph_intra_slice_allowed_flag is equal to 0, the value of slice_type shall be equal to 0 or 1. If nal_unit_type is in the range IDR_W_RADL~CRA_NUT and vps_independent_layer_flag[GeneralLayerIdx[nuh_layer_id]] is equal to 1, slice_type shall be equal to 2.

[0225] The variables MinQtLog2SizeY, MinQtLog2SizeC, MinQtSizeY, MinQtSizeC, MaxBtSizeY, MaxBtSizeC, MinBtSizeY, MaxTtSizeY, MaxTtSizeC, MinTtSizeY, MaxMttDepthY and MaxMttDepthC are derived as follows: - If slice_type is equal to 2(I), the following applies: MinQtLog2SizeY=MinCbLog2SizeY+ph_log2_diff_min_qt_min_cb_intra_slice_luma (119) MinQtLog2SizeC=MinCbLog2SizeY+ph_log2_diff_min_qt_min_cb_intra_slice_chroma (120) MaxBtSizeY=1<<(MinQtLog2SizeY+ph_log2_diff_max_bt_min_qt_intra_slice_luma) (121) MaxBtSizeC=1<<(MinQtLog2SizeC+ph_log2_diff_max_bt_min_qt_intra_slice_chroma) (122) MaxTtSizeY=1<<(MinQtLog2SizeY+ph_log2_diff_max_tt_min_qt_intra_slice_luma) (123) MaxTtSizeC=1<<(MinQtLog2SizeC+ph_log2_diff_max_tt_min_qt_intra_slice_chroma) (124) MaxMttDepthY=ph_max_mtt_hierarchy_depth_intra_slice_luma (125) MaxMttDepthC=ph_max_mtt_hierarchy_depth_intra_slice_chroma (126) CuQpDeltaSubdiv=ph_cu_qp_delta_subdiv_intra_slice (127) CuChromaQpOffsetSubdiv=ph_cu_chroma_qp_offset_subdiv_intra_slice (128) - Otherwise (slice_type equals 0 (B) or 1 (P)), the following applies: MinQtLog2SizeY=MinCbLog2SizeY+ph_log2_diff_min_qt_min_cb_inter_slice (129) MinQtLog2SizeC=MinCbLog2SizeY+ph_log2_diff_min_qt_min_cb_inter_slice (130) MaxBtSizeY=1<<(MinQtLog2SizeY+ph_log2_diff_max_bt_min_qt_inter_slice) (131) MaxBtSizeC=1<<(MinQtLog2SizeC+ph_log2_diff_max_bt_min_qt_inter_slice) (132) MaxTtSizeY=1<<(MinQtLog2SizeY+ph_log2_diff_max_tt_min_qt_inter_slice) (133) MaxTtSizeC=1<<(MinQtLog2SizeC+ph_log2_diff_max_tt_min_qt_inter_slice) (134) MaxMttDepthY=ph_max_mtt_hierarchy_depth_inter_slice (135) MaxMttDepthC=ph_max_mtt_hierarchy_depth_inter_slice (136) CuQpDeltaSubdiv=ph_cu_qp_delta_subdiv_inter_slice (137) CuChromaQpOffsetSubdiv=ph_cu_chroma_qp_offset_subdiv_inter_slice (138) - The following applies: MinQtSizeY=1< <MinQtLog2SizeY (139) MinQtSizeC=1< <MinQtLog2SizeC (140) MinBtSizeY=1< <MinCbLog2SizeY (141) MinTtSizeY=1< <MinCbLog2SizeY (142)

[0226] slice_alf_enabled_flag equal to 1 specifies that the adaptive loop filter is enabled and may be applied to the Y, Cb, or Cr color components in the slice. slice_alf_enabled_flag equal to 0 specifies that the adaptive loop filter is disabled for all color components in the slice. If not present, the value of slice_alf_enabled_flag is inferred to be ph_alf_enabled_flag.

[0227] slice_num_alf_aps_ids_luma specifies the number of ALFAPS that the slice references. If slice_alf_enabled_flag is equal to 1 and slice_num_alf_aps_ids_luma is not present, the value of slice_num_alf_aps_ids_luma is inferred to be equal to the value of ph_num_alf_aps_ids_luma.

[0228] slice_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALFAPS referenced by the luma component of the slice. The TemporalId of an APSNAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_luma[i] is not present, the value of slice_alf_aps_id_luma[i] is inferred to be equal to the value of ph_alf_aps_id_luma[i]. The value of alf_luma_filter_signal_flag of an APSNAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_luma[i] shall be equal to 1.

[0229] slice_alf_chroma_idc equal to 0 indicates that the adaptive loop filter is not applied to the Cb and Cr color components. slice_alf_chroma_idc=1 indicates that the adaptive loop filter is applied to the Cb color component. slice_alf_chroma_idc=2 indicates that the adaptive loop filter is applied to the Cr color component. slice_alf_chroma_idc=3 indicates that the adaptive loop filter is applied to the Cb and Cr color components. If slice_alf_chroma_idc is not present, it is inferred to be equal to ph_alf_chroma_idc.

[0230] slice_alf_aps_id_chroma specifies the adaptation_parameter_set_id of the ALF APS to which the chroma component of the slice refers. The TemporalId of an APS NAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_chroma shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_chroma is not present, the value of slice_alf_aps_id_chroma is inferred to be equal to the value of ph_alf_aps_id_chroma. The value of alf_chroma_filter_signal_flag shall be equal to 1 for APS NAL units whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_chroma.

[0231] slice_cc_alf_cb_enabled_flag equal to 0 specifies that the cross-component filter is not applied to the Cb color components. slice_cc_alf_cb_enabled_flag equal to 1 specifies that the cross-component filter is enabled and may be applied to the Cb color components. If slice_cc_alf_cb_enabled_flag is not present, it is inferred to be equal to ph_cc_alf_cb_enabled_flag. slice_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id referenced by the Cb color component of the slice.

[0232] The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cb_aps_id shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_cc_alf_cb_enabled_flag equals 1 and slice_cc_alf_cb_aps_id is not present, the value of slice_cc_alf_cb_aps_id is inferred to be equal to the value of ph_cc_alf_cb_aps_id. The value of alf_cc_cb_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cb_aps_id.

[0233] slice_cc_alf_cr_enabled_flag equal to 0 specifies that the cross-component filter is not applied to the Cr color component. slice_cc_alf_cb_enabled_flag equal to 1 specifies that the cross-component adaptive loop filter is enabled and may be applied to the Cr color component. If slice_cc_alf_cr_enabled_flag is not present, it is inferred to be equal to ph_cc_alf_cr_enabled_flag. slice_cc_alf_cr_aps_id specifies the adaptation_parameter_set_id to which the Cr color component of the slice refers. The TemporalId of an APS NAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is slice_cc_alf_cr_aps_id shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_cc_alf_cr_enabled_flag is equal to 1 and slice_cc_alf_cr_aps_id is not present, the value of slice_cc_alf_cr_aps_id is inferred to be equal to the value of ph_cc_alf_cr_aps_id. The value of alf_cc_cr_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cr_aps_id.

[0234] colour_plane_id identifies the colour plane associated with the current slice if separate_colour_plane_flag is equal to 1. The value of colour_plane_id shall be in the range 0 to 2, where colour_plane_id values ​​0, 1 and 2 correspond to the Y, Cb and Cr planes, respectively. The colour_plane_id value 3 is reserved for future use by ITU-T|ISO / IEC. NOTE 1 – There are no dependencies between the decoding processes of different color planes of a picture.

[0235] A num_ref_idx_active_override_flag equal to 1 specifies that the syntax element num_ref_idx_active_minus1[0] is present in P slices and B slices, and that the syntax element num_ref_idx_active_minus1[1] is present in B slices. A num_ref_idx_active_override_flag equal to 0 specifies that the syntax elements num_ref_idx_active_minus1[0] and num_ref_idx_active_minus1[1] are not present. If not present, the value of num_ref_idx_active_override_flag is inferred to be equal to 1. num_ref_idx_active_minus1[i] is used to derive the variable NumRefIdxActive[i], as defined in Equation 143. The value of num_ref_idx_active_minus1[i] should be in the range of 0 to 14, inclusive.

[0236] If i is equal to 0 or 1, when the current slice is a B slice, if num_ref_idx_active_override_flag is equal to 1 and num_ref_idx_active_minus1[i] is not present, it is inferred that num_ref_idx_active_minus1[i] is equal to 0. When the current slice is a P slice, if num_ref_idx_active_override_flag is equal to 1 and num_ref_idx_active_minus1[0] is not present, it is inferred that num_ref_idx_active_minus1[0] is equal to 0.

[0237] The variable NumRefIdxActive[i] is derived as follows: for(i=0;i<2;i++){ if(slice_type==B||(slice_type==P&&i==0)){ if(num_ref_idx_active_override_flag) NumRefIdxActive[i]=num_ref_idx_active_minus1[i]+1 else { if(num_ref_entries[i][RplsIdx[i]]>=num_ref_idx_default_active_minus1[i]+1) NumRefIdxActive[i]=num_ref_idx_default_active_minus1[i]+1 else NumRefIdxActive[i]=num_ref_entries[i][RplsIdx[i]] } }else / *slice_type==I||(slice_type==P&&i==1)* / NumRefIdxActive[i]=0 } (143)

[0238] The value of NumRefIdxActive[i]-1 specifies the maximum reference index of reference picture list i that can be used to decode a slice. If the value of NumRefIdxActive[i] is equal to 0, the slice can be decoded without using any reference index of reference picture list i. When the current slice is a P slice, the value of NumRefIdxActive[0] shall be greater than 0. If the current slice is a B slice, both NumRefIdxActive[0] and NumRefIdxActive[1] shall be greater than 0.

[0239] cabac_init_flag specifies how to determine the initialization table to be used in the context variable initialization process. If cabac_init_flag is not present, it is inferred to be equal to 0.

[0240] slice_collocated_from_I0_flag equal to 1 specifies that the co-located pictures used for temporal motion vector prediction are derived from reference picture list 0. slice_collocated_from_I0_flag equal to 0 specifies that the co-located pictures used for temporal motion vector prediction are derived from reference picture list 1.

[0241] If slice_type is B or P, ph_temporal_mvp_enabled_flag is equal to 1, and slice_collocated_from_l0_flag is not present, the following applies: - If rpl_info_in_ph_flag is equal to 1, slice_collocated_from_l0_flag is inferred to be equal to ph_collocated_from_l0_flag. - Otherwise (if rpl_info_in_ph_flag is equal to 0 and slice_type is equal to P), the value of slice_collocated_from_l0_flag is inferred to be equal to 1.

[0242] slice_collocated_ref_idx specifies the reference index of the co-located picture used for temporal motion vector prediction. If slice_type is equal to P, or slice_type is equal to B and slice_collocated_from_l0_flag is equal to 1, slice_collocated_ref_idx refers to an entry in reference picture list 0, and the numeric value of slice_collocated_ref_idx shall be in the range of 0 to NumRefIdxActive[0]-1. If slice_type is equal to B and slice_collocated_from_l0_flag is equal to 0, the value of slice_collocated_ref_idx refers to an entry in reference picture list 1, and slice_collocated_ref_idx shall be in the range of 0 to NumRefIdxActive[1]-1.

[0243] If slice_collocated_ref_idx is not present, the following applies: - If rpl_info_in_ph_flag is equal to 1, the value of slice_collocated_ref_idx is inferred to be equal to ph_collocated_ref_idx. - Otherwise (rpl_info_in_ph_flag is equal to 0), the value of slice_collocated_ref_idx is inferred to be equal to 0.

[0244] It is a bitstream compatibility requirement that the picture referenced by slice_collocated_ref_idx shall be the same for all slices of a coded picture. It is a bitstream conformance requirement that the values ​​of pic_width_in_luma_samples and pic_height_in_luma_samples of the reference picture referenced by slice_collocated_ref_idx shall be the same as the values ​​of pic_width_in_luma_samples and pic_height_in_luma_samples of the current picture, respectively, and that RprConstraintsActive[slice_collocated_from_l0_flag?0:1][slice_collocated_ref_idx] shall be equal to 0.

[0245] slice_qp_delta is the Qp used for coding blocks in a slice. YSpecifies the initial value of CuQpDeltaVal at the coding unit layer until it is modified by the value of CuQpDeltaVal at the coding unit layer.

[0246] If qp_delta_info_in_ph_flag is equal to 0, the Qp of the slice Y Quantization parameter SliceQp Y The initial value of is derived as follows: SliceQp Y =26+init_qp_minus26+slice_qp_delta (144) SliceQp Y The value is in the range of -QpBdOffset to +63.

[0247] When any of the following conditions is true: - the value of wp_info_in_ph_flag is equal to 1, pps_weighted_pred_flag is equal to 1, and slice_type is equal to P. - the value of wp_info_in_ph_flag is equal to 1, pps_weighted_bipred_flag is equal to 1, and slice_type is equal to B. The following applies: - The value of NumRefIdxActive[0] shall be less than or equal to the value of NumWeightsL0. - For each reference picture index RefPicList[0][i], i in the range 0 to NumRefIdxActive[0]-1, the luma weight, Cb weight, and Cr weight applied to the reference picture index are applied to LumaWeightL0[i], ChromaWeightL0[0][i], and ChromaWeightL0[1][i], respectively.

[0248] If wp_info_in_ph_flag is equal to 1, pps_weighted_bipred_flag is equal to 1, and slice_type is equal to B, the following applies: - The value of NumRefIdxActive[1] shall be less than or equal to the value of NumWeightsL1. - For each reference picture index RefPicList[1][i], i in the range 0 to NumRefIdxActive[1]-1, the luma weight, Cb weight, and Cr weight applied to the reference picture index are applied to LumaWeightL1[i], ChromaWeightL1[0][i], and ChromaWeightL1[1][i], respectively.

[0249] slice_cb_qp_offset is Qp' cb Specifies the difference to add to the value of pps_cb_qp_offset when determining the value of the quantization parameter. The value of slice_cb_qp_offset shall be in the range of -12 to +12. If slice_cb_qp_offset is not present, it is inferred to be equal to 0. The value of pps_cb_qp_offset+slice_cb_qp_offset shall be in the range of -12 to +12. slice_cr_qp_offset is Qp' cr Specifies the difference to add to the value of pps_cr_qp_offset when determining the value of the quantization parameter. The value of slice_cr_qp_offset shall be in the range of -12 to +12. If slice_cr_qp_offset is not present, it is inferred to be equal to 0. The value of pps_cr_qp_offset+slice_cr_qp_offset shall be in the range of -12 to +12.

[0250] slice_joint_cbcr_qp_offset is Qp' CbCrSpecifies the difference to add to the value of pps_joint_cbcr_qp_offset when determining the value of slice_joint_cbcr_qp_offset. The value of slice_joint_cbcr_qp_offset shall be in the range of -12 to +12. If slice_joint_cbcr_qp_offset is not present, it is inferred to be equal to 0. The value of pps_joint_cbcr_qp_offset_value+slice_joint_cbcr_qp_offset shall be in the range of -12 to +12.

[0251] cu_chroma_qp_offset_enabled_flag equal to 1 specifies that cu_chroma_qp_offset_flag may be present in transform units and palette coding syntax. cu_chroma_qp_offset_enabled_flag equal to 0 specifies that cu_chroma_qp_offset_flag is not present in transform units or palette coding syntax. If not present, the value of cu_chroma_qp_offset_enabled_flag is inferred to be equal to 0.

[0252] slice_sao_luma_flag equal to 1 specifies that SAO is enabled for the luma component in the current slice. slice_sao_luma_flag equal to 0 specifies that SAO is disabled for the luma component in the current slice. If slice_sao_luma_flag is not present, it is inferred to be equal to ph_sao_luma_enabled_flag. slice_sao_chroma_flag equal to 1 specifies that SAO is enabled for the chroma component in the current slice. slice_sao_chroma_flag equal to 0 specifies that SAO is disabled for the chroma component in the current slice. If slice_sao_chroma_flag is not present, it is inferred to be equal to ph_sao_chroma_enabled_flag.

[0253] slice_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in the slice header. slice_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in the slice header. If not present, the value of slice_deblocking_filter_override_flag is inferred to be equal to ph_deblocking_filter_override_flag. slice_deblocking_filter_disabled_flag equal to 1 specifies that the operation of a deblocking filter is not applied to the current slice. slice_deblocking_filter_disabled_flag equal to 0 specifies that the operation of a deblocking filter is applied to the current slice. If slice_deblocking_filter_disabled_flag is not present, it is inferred to be equal to ph_deblocking_filter_disabled_flag.

[0254] slice_beta_offset_div2 and slice_tc_offset_div2 specify the β and tC deblocking parameter offsets (divided by 2) applied to the luma component of the current slice. The values ​​of slice_beta_offset_div2 and slice_tc_offset_div2 shall both be in the range of -12 to 12. If not present, the values ​​of slice_beta_offset_div2 and slice_tc_offset_div2 are inferred to be equal to ph_beta_offset_div2 and ph_tc_offset_div2, respectively. slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 specify the β and tC deblocking parameter offsets (divided by 2) applied to the Cb component of the current slice. The values ​​of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 shall both be in the range of -12 to 12. If not present, the values ​​of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 are inferred to be equal to ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2, respectively. slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 specify the beta and tC deblocking parameter offsets (divided by 2) applied to the Cr component of the current slice. The values ​​of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 shall both be in the range of -12 to 12. If not present, the values ​​of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 are inferred to be equal to ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2, respectively.

[0255] slice_ts_residual_coding_disabled_flag equal to 1 specifies that the residual_coding() syntax structure is used to parse the residual samples of the transform skip blocks for the current slice. slice_ts_residual_coding_disabled_flag equal to 0 specifies that the residual_ts_coding() syntax structure is used to parse the residual samples of the transform skip blocks for the current slice. If slice_ts_residual_coding_disabled_flag is not present, it is inferred to be equal to 0.

[0256] slice_lmcs_enabled_flag equal to 1 specifies that luma mapping with saturation scaling is enabled for the current slice. slice_lmcs_enabled_flag equal to 0 specifies that luma mapping with saturation scaling is disabled for the current slice. If slice_lmcs_enabled_flag is not present, it is inferred to be equal to 0.

[0257] slice_scaling_list_present_flag equal to 1 specifies that the scaling list data used for the current slice is derived based on the scaling list data contained in the reference scaling list APS with aps_params_type equal to SCALING_APS and adaptation_parameter_set_id equal to ph_scaling_list_aps_id. slice_scaling_list_present_flag equal to 0 specifies that the scaling list data used for the current picture is the derived default scaling list data specified in clause 7.4.3.21. If not present, the value of slice_scaling_list_present_flag is inferred to be 0.

[0258] The variable NumEntryPoints, which defines the number of entry points in the current slice, is derived as follows: NumEntryPoints=0 for(i=1;i <NumCtusInCurrSlice;i++){ ctbAddrX=CtbAddrInCurrSlice[i]%PicWidthInCtbsY ctbAddrY=CtbAddrInCurrSlice[i] / PicWidthInCtbsY prevCtbAddrX=CtbAddrInCurrSlice[i-1]%PicWidthInCtbsY prevCtbAddrY=CtbAddrInCurrSlice[i-1] / PicWidthInCtbsY if(CtbToTileRowBd[ctbAddrY]!=CtbToTileRowBd[prevCtbAddrY]|| CtbToTileColBd[ctbAddrX]!=CtbToTileColBd[prevCtbAddrX]|| (ctbAddrY!=prevCtbAddrY&&sps_wpp_entry_point_offsets_present_flag)) NumEntryPoints++ }

[0259] offset_len_minus1+1 specifies the length in bits of the entry_point_offset_minus1[i] syntax element. The value of offset_len_minus1 shall be in the range 0 to 31.

[0260] entry_point_offset_minus1[i]+1 specifies the offset of the i-th entry point in bytes, represented as offset_len_minus1+1 bits. The slice data following the slice header consists of NumEntryPoints+1 subsets, with subset index values ​​ranging from 0 to NumEntryPoints. The first byte of slice data is byte 0. If present, an emulation prevention byte appearing in the slice data portion of a coded slice NAL unit is counted as part of the slice data for subset identification. Subset 0 consists of bytes 0 to entry_point_offset_minus1[0] of the coded slice data, and subset k (where k ranges from 1 to NumEntryPoints-1) consists of bytes firstByte[k] to lastByte[k] of the coded slice data, where firstByte[k] and lastByte[k] are defined below.

[0261]

number

[0262] The last subset (subset index equals NumEntryPoints) consists of the remaining bytes of the coded slice data.

[0263] If sps_entropy_coding_sync_enabled_flag is equal to 0 and the slice contains one or more complete tiles, each subset shall consist of all coded bits of all CTUs in the slice that are within the same tile, and the number of subsets (i.e., the value of NumEntryPoints+1) shall be equal to the number of tiles in the slice. If sps_entropy_coding_sync_enabled_flag is equal to 0 and the slice contains a subset of CTU rows from a single tile, NumEntryPoints shall be equal to 0 and the number of subsets shall be equal to 1. The subset shall consist of all coded bits of all CTUs in the slice. If sps_entropy_coding_sync_enabled_flag is equal to 1, each subset, where k is in the range from 0 to NumEntryPoints, shall consist of the coded bits of all CTUs in a CTU row within a tile, and the number of subsets (i.e., the value of NumEntryPoints+1) shall be equal to the total number of tile-specific CTU rows in the slice.

[0264] slice_header_extension_length specifies the length of the slice header extension data in bytes, not including the bits used for signaling the slice_header_extension_length itself. The value of slice_header_extension_length should be in the range from 0 to 256. If not present, the value of slice_header_extension_length is inferred to be equal to 0. slice_header_extension_data_byte[i] may have any value. Decoders conforming to this specification version must ignore the value of all slice_header_extension_data_byte[i] syntax elements. The value does not affect the decoder's conformance to the features specified in this specification version.

[0265] 3.5 Saturation QP Mapping Table In 7.3.2.3 of JVET-Q2001-vC, the SPS includes a structure called the chroma QP table as follows:

[0266] [Table 32]

[0267] These have the following semantics and QP table derivation: sps_joint_cbcr_enabled_flag equal to 0 specifies that joint coding of chroma residual is disabled. sps_joint_cbcr_enabled_flag equal to 1 specifies that joint coding of chroma residual is enabled. If not present, the value of sps_joint_cbcr_enabled_flag is inferred to be equal to 0. same_qp_table_for_chroma equal to 1 specifies that only one chroma QP mapping table is signaled, and this table applies to Cb and Cr residuals, and also to the joint Cb-Cr residual if sps_joint_cbcr_enabled_flag is equal to 1. same_qp_table_for_chroma equal to 0 specifies that if sps_joint_cbcr_enabled_flag is equal to 1, then two chroma QP mapping tables, one for Cb and Cr and an additional one for joint Cb-Cr, are signaled in the SPS. If same_qp_table_for_chroma is not present in the bitstream, the value of same_qp_table_for_chroma equal to 1 is inferred.

[0268] qp_table_start_minus26[i]+26 specifies the starting luma and chroma QP used to describe the i-th chroma QP mapping table. The value of qp_table_start_minus26[i] shall be in the range of -26-QpBdOffset to 36. If qp_table_start_minus26[i] is not present in the bitstream, the value of qp_table_start_minus26[i] is inferred to be equal to 0.

[0269] num_points_in_qp_table_minus1[i]+1 specifies the number of points used to describe the i-th chroma QP mapping table. The value of num_points_in_qp_table_minus1[i] shall be in the range of 0 to 63+QpBdOffset. If num_points_in_qp_table_minus1[0] is not present in the bitstream, the value of num_points_in_qp_table_minus1[0] is inferred to be equal to 0.

[0270] delta_qp_in_val_minus1[i][j] specifies the delta value used to derive the input coordinate of the jth pivot point of the ith chroma QP mapping table. If delta_qp_in_val_minus1[0][j] is not present in the bitstream, the value of delta_qp_in_val_minus1[0][j] is inferred to be equal to 0.

[0271] delta_qp_diff_val[i][j] Specifies the delta value used to derive the output coordinate of the j-th pivot point of the ith chroma QP mapping table.

[0272] The i-th chroma QP mapping table ChromaQpTable[i], where i=0...numQpTables-1, is derived as follows: qpInVal[i][0]=qp_table_start_minus26[i]+26 qpOutVal[i][0]=qpInVal[i][0] for(j=0;j<=num_points_in_qp_table_minus1[i];j++){ qpInVal[i][j+1]=qpInVal[i][j]+delta_qp_in_val_minus1[i][j]+1 qpOutVal[i][j+1]=qpOutVal[i][j]+(delta_qp_in_val_minus1[i][j]^delta_qp_diff_val[i][j]) } ChromaQpTable[i][qpInVal[i][0]]=qpOutVal[i][0] for(k=qpInVal[i][0]-1;k>=-QpBdOffset;k--) ChromaQpTable[i][k]=Clip3(-QpBdOffset,63,ChromaQpTable[i][k+1]-1) for(j=0;j<=num_points_in_qp_table_minus1[i];j++){ sh=(delta_qp_in_val_minus1[i][j]+1)>>1 for(k=qpInVal[i][j]+1,m=1;k<=qpInval[i][j+1];k++,m++) ChromaQpTable[i][k]=ChromaQpTable[i][qpInVal[i][j]]+ ((qpOutVal[i][j+1]-qpOutVal[i][j])*m+sh) / (delta_qp_in_val_minus1[i][j]+1) } for(k=qpInVal[i][num_points_in_qp_table_minus1[i]+1]+1;k<=63;k++) ChromaQpTable[i][k]=Clip3(-QpBdOffset,63,ChromaQpTable[i][k-1]+1)

[0273] If same_qp_table_for_chroma is equal to 1, ChromaQpTable[1][k] and ChromaQpTable[2][k] are set equal to ChromaQpTable[0][k], for k in the range of -QpBdOffset to 63.

[0274] Bitstream conformance requires that the values ​​of qpInVal[i][j] and qpOutVal[i][j] be in the range of -QpBdOffset to 63, with i in the range of 0 to numQpTables-1, and j in the range of 0 to num_points_in_qp_table_minus1[i]+1.

[0275] In the above description, QpBdOffset is derived as follows. bit_depth_minus8 specifies the bit depth of the samples in the luma and chroma array BitDepth and the value of the chroma quantization parameter range offset QpBdOffset as follows: BitDepth=8+bit_depth_minus8 QpBdOffset=6*bit_depth_minus8 bit_depth_minus8 is in the range 0 to 8.

[0276] 4. Technical problem solved by the disclosed technical solution The existing design of the latest VVC draft specification for APS, deblocking, subpicture, and QP delta has the following problems:

[0277] [ka]

[0278] Such constraints on the semantics of APS syntax elements result in a semantic dependency of the APS on the SPS, which should not occur due to the absence of a PPS ID or SPS ID in the APS syntax; an APS may be applied to pictures (or slices of a picture) that reference different SPSs and may be associated with different values ​​of ChromaArrayType.

[0279] [ka]

[0280] b. Currently, when LMCS APS is signaled, chroma residual scaling related syntax elements are always signaled in the LMCS APS syntax structure, regardless of whether ChromaArrayType is equal to 0 (i.e., no chroma component is present in CLVS), resulting in unnecessary signaling of chroma related syntax elements.

[0281] 2) The deblocking control mechanisms in recent VVC texts are described as being very complex, non-trivial, difficult to understand, and consequently prone to errors. Below are some example problems that have been observed: a. According to the current text, even if the deblocking filter is disabled in the PPS, the deblocking filter can be enabled in the PH or SH. For example, first signaling pps_deblocking_filter_disabled_flag equal to 1 and signaling deblocking_filter_override_enabled_flag equal to 1 indicates that the deblocking filter is disabled in the PPS and allows the deblocking filter enable / disable control to be overridden in the PH or SH. Next, signaling dbf_info_in_ph_flag and signaling the PH syntax element ph_deblocking_filter_disabled_flag equal to 0 ultimately enables the deblocking filter for the slice associated with the PH. In such a case, deblocking is ultimately enabled in the PH despite being disabled at a higher level (e.g., the PPS). This design logic is specific to VVC text and is completely different from the design logic of other coding tools (e.g., ALF, SAO, LMCS, TMVP, WP, etc.), and when a coding tool is disabled in a higher layer (e.g., SPS, PPS, etc.), it is completely disabled in a lower layer (e.g., PH, SH, etc.).

[0282] [ka]

[0283] c. Also, the current text specifies that if the PPS syntax elements deblocking_filter_override_enabled_flag and pps_deblocking_filter_disabled_flag are both equal to 1, deblocking is disabled in the PPS and deblocking filter control is intended to override in the PH or SH. However, the subsequent PH syntax elements ph_deblocking_filter_override_flag and ph_deblocking_filter_disabled_flag may still be signaled to be 1, and the resulting override process would not change anything (e.g., deblocking would remain disabled in the PH / SH) but would just use unnecessary bits for meaningless signaling. d. Furthermore, according to the current text, if the SH syntax element slice_deblocking_filter_override_flag is not present, it is inferred to be equal to ph_deblocking_filter_override_flag. However, in addition to implicit or explicit signaling in the PPS, deblocking parameters can only be signaled in either PH or SH according to dbf_info_in_ph_flag, but not both. Therefore, when dbf_info_in_ph_flag is true, it is intended to allow the override deblocking filter parameters in the PH to be signaled. In this case, if the PH override flag is true and the SH override flag is not signaled but is inferred to be equal to the PH override flag, additional deblocking filter parameters are still signaled in the SH, which contradicts the intention. e. Also, there is no way to control on / off of deblocking at the SPS level, and this may be added and the related syntax elements in PPS / PH / SH may be updated accordingly.

[0284] 3) Currently, if the PPS syntax element single_slice_per_subpic_flag is not present, it is inferred to be equal to 0. single_slice_per_subpic_flag is not present in two cases: i) no_pic_partition_flag is equal to 1, and ii) no_pic_partition_flag is equal to 0 and rect_slice_flag is equal to 0. In case i), if no_pic_partition_flag is equal to 1, no picture partitioning is applied to each picture that references a PPS, thereby specifying that there is only one slice per picture, and consequently, only one slice per subpicture. Therefore, single_slice_per_subpic_flag should be inferred to be equal to 1 in this case. In case ii), rect_slice_flag is equal to 0, so no inferred value of single_slice_per_subpic_flag is needed.

[0285] 4) Currently, luma qp delta at either picture or slice level is always forced to be signaled to either PH or SH, but not both, whereas slice-level chroma QP offset is selectively signaled in SH. Such a design is somehow inconsistent.

[0286] [ka]

[0287] 5) With the current design of the chroma Qp mapping table, it is not easy to represent the case where chroma Qp is equal to luminance Qp.

[0288] 6) Currently, subpic_transted_as_pic_flag[i] is inferred to be equal to the value of sps_independent_subpics_flag. However, the current spec allows enabling horizontal wraparound only if subpic_treated_as_pic_flag[i] is equal to 0, and wraparound motion compensation is designed for 360 video content. Therefore, if a picture contains only one subpicture (especially if a complete 360 ​​video sequence contains only one subpicture), the inferred value of subpic_treated_as_pic_flag[i] can be inferred to be equal to 0 or a constant value that enables wraparound motion compensation.

[0289] 7) Currently, the semantics of pps_deblocking_filter_disabled_flag is incorrect and incomplete. For example, when pps_deblocking_filter_disabled_flag is equal to 1, deblocking may be enabled or disabled for slices that refer to this PPS, but these conditions are not mentioned in the semantics. The same applies to the semantics part of pps_deblocking_filter_disabled_flag equal to 0. a. Furthermore, when the PPS syntax element pps_deblocking_filter_disabled_flag is equal to 1 while the PH / SH syntax element ph / slice_deblocking_filter_override_flag is signaled equal to 1, ph / slice_deblocking_filter_disabled_flag is still allowed to be explicitly signaled equal to 1. This flag value combination is said to disable deblocking at the PPS level and allow override at the picture or slice, then to indicate that override is about to occur at the PH / SH level, and then a bit is signaled within the same header (PH / SH) to determine that no override is actually occurring, and deblocking remains disabled at the picture / slice level. This is argued to have the dual undesirable effect of not only using a bit unnecessarily but also using it to cause confusion. Therefore, we propose to further improve the semantics of the deblocking control syntax element, eliminating the ability to indicate override and immediately sending the next bit in the same PH or SH to indicate a change of mind.

[0290] 8) The first coded slice in decoding order of an IRAP or GDR picture may point to a suffix APS NAL unit and may delay the random access response.

[0291] 9) In VVC, updating the content of APS NAL units within a PU is not allowed, which may limit some applications.

[0292] 10) It has been identified that the current VVC draft text has some issues / bugs (e.g. related to APS syntax) which should be fixed. a. The absolute values ​​of the ALF filter coefficients (alf_luma_coeff_abs and alf_chroma_coeff_abs[altIdx][j] in VVC text) are in the range [0,128]. Therefore, 9-bit coefficients are needed just to store the values ​​128 and -128.

[0293] 11) In the text, the total number of ALF APSs allowed is limited to 8, and each ALF APS takes about 512 bytes, so 8 of those take 4k bytes. Considering the significant memory impact, and since the amount of memory an APS uses depends on its content, it was suggested to consider the constraint on the total amount of memory used (or the number of filters in an APS - one APS has a maximum of 25 luma and 8 chroma filters), rather than the number of APSs.

[0294] 12) Currently, the APS ID (i.e., the syntax element adaptation_parameter_set_id) is coded as u(5), and when aps_params_type is equal to ALF_APS or SCALING_APS, the value of adaptation_parameter_set_id must be in the range of 0 to 7, and when aps_params_type is equal to LMCS_APS, the value of adaptation_parameter_set_id must be in the range of 0 to 3. In other words, it is sufficient to use 3 bits instead of 5 bits for the APSID.

[0295] 13) Currently, general constraint flags in the general_constraint_info() syntax structure are parsed in a different order. They are more structured when grouped as inter-related and intra-related syntax elements.

[0296] 14) If inter-slices are allowed for a picture, an indication of the allowed slice types in the picture (e.g., ph_intra_slice_allowed_flag) is always signaled. However, if a picture contains only one slice, the allowed intra-slice flag does not need to be signaled if inter-slices are allowed.

[0297] 5. Exemplary Embodiments and Solutions In order to solve the above-mentioned problems and other problems, the following method is disclosed. The present invention should be regarded as an example for explaining a general concept, and should not be interpreted in a narrow sense. Furthermore, the present invention may be applied individually or in any combination. In the following description, an SH may be associated with one PH, i.e., an SH is associated with one slice, and this slice is in the picture associated with this PH. An SH may be associated with one PPS, i.e., an SH is associated with one slice, and this slice is in the picture associated with this PPS. An PH may be associated with a PPS, i.e., an PH is associated with a picture associated with the PPS. In the following description, an SPS may be associated with a PPS, i.e., a PPS may refer to an SPS.

[0298] [ka]

[0299] 1. Regarding the constraints on APS syntax elements to solve the first problem, one or more of the following approaches are disclosed.

[0300] In one example, constrain the value of scaling_list_chroma_present_flag according to the ChromaArrayType derived from the PH syntax element. i. For example, whether the value of scaling_list_chroma_present_flag is constrained may depend on whether ph_scaling_list_aps_id is present, as in the first embodiment. 1) In one example, if ph_scaling_list_aps_id is present, the value of scaling_list_chroma_present_flag of an APS NAL unit having aps_params_type equal to SCALING_APS and adaptation_parameter_set_id equal to ph_scaling_list_aps_id is required to be equal to ChromaArrayType==0?0:1. ii. Alternatively, scaling_list_chroma_present_flag is constrained based on the ChromaArrayType derived by the PH syntax element, but independently of the presence of ph_scaling_list_aps_id, eg, as in the first embodiment. 1) In one example, the value of scaling_list_chroma_present_flag of an APS NAL unit with aps_params_type equal to SCALING_APS must be equal to ChromaArrayType==0?0:1.

[0301] b. In one example, constrain the value of lmcs_delta_abs_crs based on the ChromaArrayType derived by the PH syntax element. i. For example, whether the value of lmcs_delta_abs_crs is constrained may depend on whether ph_lmcs_aps_id is present, as in the first embodiment. 1) For example, if ph_lmcs_aps_id is present, the value of lmcs_delta_abs_crs of an APS NAL unit with aps_params_type equal to LMCS_APS and adaptation_parameter_set_id equal to ph_lmcs_aps_id is required to be 0 if ChromaArrayType is equal to 0, and greater than 0 otherwise. 2) Alternatively, if ph_lmcs_aps_id is present, when ChromaArrayType is equal to 0, the lmcs_delta_abs_crs value of an APSNAL unit with aps_params_type equal to LMCS_APS and adaptation_parameter_set_id equal to ph_lmcs_aps_id shall be equal to 0. ii. Alternatively, lmcs_delta_abs_crs is constrained based on the ChromaArrayType derived by the PH syntax element, but regardless of the presence of ph_lmcs_aps_id, e.g., as in the first embodiment. 1) For example, the value of lmcs_delta_abs_crs of an APS NAL unit equal to ph_lmcs_aps_id is equal to 0 if ChromaArrayType is equal to 0, and is greater than 0 otherwise. 2) For example, if ChromaArrayType is equal to 0, the value of lmcs_delta_abs_crs in an APS NAL unit equal to ph_lmcs_aps_id is equal to 0.

[0302] c. In one example, the values ​​of ALF APS syntax elements (eg, alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, alf_cc_cr_filter_signal_flag, etc.) are constrained according to the ChromaArrayType that the PH and / or SH syntax elements derive from. i. For example, whether the values ​​of alf_chroma_filter_signal_flag and / or alf_cc_cb_filter_signal_flag and / or alf_cc_cr_filter_signal_flag are constrained may be determined by whether ph_alf_aps_id_luma[i] or slice_alf_aps_id_luma[i] are present and / or whether ChromaArrayType is equal to 0, as in, for example, the first embodiment. 1) For example, if ph_alf_aps_id_luma[i] exists and ChromaArrayType is equal to 0, The values ​​of alf_chroma_filter_flag, alf_cc_cb_filter_flag, and alf_cc_cr_filter_flag of an APS NAL unit with ALF_APS equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i] MUST all be equal to 0. 2) Also, if slice_alf_aps_id_luma[i] exists and ChromaArrayType is equal to 0, The values ​​of alf_chroma_filter_flag, alf_cc_cb_filter_flag, and alf_cc_cr_filter_flag of an APS NAL unit with ALF_APS equal to ALF_APS and adaptation_parameter_set_id equal to slice_alf_aps_id_luma[i] MUST all be equal to 0. ii. Alternatively, alf_chroma_filter_signal_flag and / or alf_cc_cb_filter_signal_flag and / or alf_cc_cr_filter_signal_flag are constrained based on the ChromaArrayType derived by the PH syntax element or the SH syntax element, regardless of the presence of ph_alf_aps_id_luma[i] and / or slice_alf_aps_id_luma[i], e.g., as an example of the first implementation. 1) For example, if ChromaArrayType is equal to 0, the values ​​of alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, and alf_cc_cr_filter_signal_flag of APS NAL units with aps_params_type equal to ALF_APS are required to all be equal to 0. 2) Additionally, if ChromaArrayType is equal to 0, the values ​​of alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, and alf_cc_cr_filter_signal_flag of APS NAL units with aps_params_type equal to ALF_APS are required to all be equal to 0. iii. Alternatively, alf_chroma_filter_signal_flag and / or alf_cc_cb_filter_signal_flag and / or alf_cc_cr_filter_signal_flag are constrained based on the ChromaArrayType derived by the chroma APS ID related PH or SH syntax element, for example as in the first embodiment. 1) For example, alf_chroma_filter_signal_flag is constrained by the ChromaArrayType derived by the PH syntax element ph_alf_aps_id_chroma and / or the SH syntax element slice_alf_aps_id_chroma. 2) For example, alf_cc_cb_filter_signal_flag is constrained according to the ChromaArrayType derived by the PH syntax element ph_cc_alf_cb_aps_id and the SH syntax element slice_cc_alf_cb_aps_id. 3) For example, alf_cc_cr_filter_signal_flag is constrained according to the ChromaArrayType derived by the PH syntax element ph_cr_alf_cb_aps_id and the SH syntax element slice_cr_alf_cb_aps_id.

[0303] d. In one example, the semantics of APS syntax elements in the ALF and / or SCALING LIST and / or LMCS data syntax structures may be independent of whether it is 4:0:0 video coding and / or separate color plane coding. i. For example, the semantics of APS syntax elements (e.g., alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, alf_cc_cr_filter_signal_flag, etc.) in the ALF data syntax structure may not depend on the variables / syntax derived by SPS / PH / SH syntax elements (e.g., ChromaArrayType) as in, for example, the first embodiment. ii. Additionally, alternatively, the semantics of APS syntax elements (e.g., scaling_list_chroma_present_flag, and others) in the SCALING LIST data syntax structure may not depend on the variables / syntax derived by SPS / PH / SH syntax elements (e.g., ChromaArrayType), as in, for example, the first embodiment.

[0304] e. Furthermore, whether the TemporId of an ALF / SCALING / LMCS APS NAL unit is constrained may depend on whether a corresponding APS ID exists, for example, similar to the first embodiment. i. For example, whether the temporalId of an ALF APS NAL unit is constrained may depend on whether ph_alf_aps_id_luma[i] and / or ph_alf_aps_id_chroma and / or ph_cc_alf_cb_aps_id and / or ph_cc_alf_cr_aps_id are present. ii. For example, whether the temporalId of an LMCS APS NAL unit is constrained may depend on whether ph_lmcs_aps_id is present. iii. For example, whether the temporalId of a SCALING APS NAL unit is constrained may depend on whether ph_scaling_list_aps_id is present.

[0305] f. Furthermore, whether the values ​​of alf_luma_filter_signal_flag, alf_chroma_filter_signal_flag and / or alf_cc_cb_filter_signal_flag and / or alf_cc_cr_filter_signal_flag are equal to 1 may depend on whether a corresponding APS ID exists, as in the first embodiment, for example. i. For example, whether alf_luma_filter_signal_flag is equal to 1 may be determined by whether ph_alf_aps_id_luma[i] and / or slice_alf_aps_id_luma[i] are present. ii. For example, whether alf_chroma_filter_signal_flag is equal to 1 may depend on whether ph_alf_aps_id_chroma and / or slice_alf_aps_id_chroma are present. iii. For example, whether alf_cc_cb_filter_signal_flag is equal to 1 may depend on whether ph_cc_alf_cb_aps_id and / or slice_cc_alf_cb_aps_id are present. iv. For example, whether alf_cc_cr_filter_signal_flag is equal to 1 may depend on whether ph_cc_alf_cr_aps_id and / or slice_cc_alf_cr_aps_id are present.

[0306] g. Additionally, alternatively, whether chroma ALF APS ID syntax elements (e.g., slice_alf_aps_id_chroma, slice_cc_alf_cb_aps_id, slice_cr_alf_cb_aps_id, and others) within SH are inferred may depend on the value of ChromaArrayType, for example, as in the first set of embodiments. i. For example, if ChromaArrayType is not equal to 0, the values ​​of the chroma ALF APS ID syntax elements (e.g., slice_alf_aps_id_chroma, slice_cc_alf_cb_aps_id, slice_cr_alf_cb_aps_id, etc.) in SH may be inferred.

[0307] h. In one example, the constraints on the APS syntax element based on the ChromaArrayType may be derived by the PH syntax element or the SH syntax element. i. Alternatively, constraints on one or more syntax elements of the APS, such as indications of the presence of saturation information (e.g., whether a saturation filter is signaled, whether a saturation scaling list is signaled, whether the LMCS residual scaling factor is equal to 0), may be defined in the semantics of the PH and / or SH syntax elements. a) Alternatively, the PH and / or SH syntax elements may refer to an APS. b) Alternatively, constraints on the same syntax element in different APS types may be different, i.e. using one-way (e.g., if a condition is true, the constraint applies) or two-way constraints (e.g., if a condition is true, the first constraint applies, otherwise the second constraint applies). ii. In one example, the APS to which a syntax element is constrained is determined by the index signaled in the PH or SH (ph_num_alf_aps_ids_luma, ph_alf_aps_id_chroma, ph_lmcs_aps_id, ph_scaling_list_aps_id, etc.). iii. In one example, the ChromaArrayType may be derived from information signaled in the SPS (e.g., chroma_format_idc and separate_color_plane_flag), determined by an index signaled in the PPS (e.g., pps_seq_parameter_set_id), and further determined by an index signaled in the PH or SH (e.g., ph_pic_parameter_set_id). iv. In one example, the constraint should be checked after parsing the APS and PH or SH. v. In one example, a syntax element (e.g., called aps_chroma_present_flag) may be signaled in an APS syntax structure (e.g., adaptation_parameter_set_rbsp()) to specify whether chroma-related APS syntax elements are signaled. a) In one example, the syntax elements may be defined as in the sixth embodiment. b) Alternatively, a syntax element (e.g., called aps_chroma_present_flag) may be used to control the presence of other syntax elements in the APS and / or how other syntax elements are signaled and / or how inferred values ​​of other syntax elements are derived. c) For example, if aps_chroma_present_flag is equal to a certain value (e.g., 1), it specifies that chroma-related APS syntax elements may be present in LMCS / SCALING / ALF APS data. d) For example, if aps_chroma_present_flag is equal to a certain value (e.g., 0), it specifies that no chroma-related APS syntax elements are present in the LMCS / SCALING / ALF APS data. e) For example, if aps_chroma_params_present_flag is equal to 1, it specifies that the APS NAL unit may include chroma information. If aps_chroma_params_present_flag is equal to 0, it specifies that the APS NAL unit does not include chroma information. f) For example, if aps_chroma_present_flag is equal to a constant value (e.g., 0 or 1), chroma-related APS elements in the ALF APS syntax structure (e.g., alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, alf_cc_cr_filter_signal_flag in alf_data()) may not be signaled. g) For example, if aps_chroma_present_flag is equal to a certain value (such as 0 or 1), chroma-related APS elements of the LMCS APS syntax structure (e.g., lmcs_delta_abs_crs and / or lmcs_delta_sign_crs_flag in lmcs_data()) may not be signaled. h) For example, if aps_chroma_present_flag is equal to a certain value (such as 0 or 1), chroma-related APS elements in the SCALING APS syntax structure (e.g., scaling_list_copy_mode_flag[id], scaling_list_pred_id_delta[id], scaling_list_dc_coef[id-14], scaling_list_delta_coef[id][i] in scaling_data()) may not be signaled, where id is a number. a. For example, id is equal to a value in the range 0 to X (e.g., X=27). b. For example, id is not equal to X (e.g., X=27). c. For example, id%M is not equal to N (e.g., M=3, N=2). i) For example, if a saturation-related APS syntax element is not present, it is inferred to be equal to a constant value (e.g., 0 or 1). vi. In one example, if the presence of chroma-related APS syntax elements is allowed (e.g., aps_chroma_present_flag is equal to 1), then at least one of alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, and alf_cc_cr_filter_signal_flag is required to be equal to 1. vii. Alternatively, if chroma-related APS syntax elements are allowed to be present (eg, aps_chroma_present_flag equals 1), the signaling of syntax element X may depend on the value of the syntax elements in Y's set. a) For example, X is alf_chroma_filter_signal_flag and Y includes alf_cc_cb_filter_signal_flag and alf_cc_cr_filter_signal_flag. b) For example, X is alf_cc_cb_filter_signal_flag and Y includes alf_chroma_filter_signal_flag and alf_cc_cr_filter_signal_flag. c) For example, X is alf_cc_cr_filter_signal_flag and Y includes alf_chroma_filter_signal_flag and alf_cc_cb_filter_signal_flag. d) For example, if the value of an element in Y is equal to 0, the signaling of A is skipped. e) For example, if a value of X is absent, then this value of X is inferred to be equal to a constant value (e.g., 0 or 1). f) For example, the value of X is inferred to be equal to whether the presence of chroma-related APS syntax elements is allowed (e.g., set to the value of aps_chroma_present_flag). viii. The syntax element aps_chroma_present_flag may also be constrained by ChromaArrayType. a) For example, if ChromaArrayType is equal to 0, then aps_chroma_present_flag shall be equal to 0. b) For example, if ChromaArrayType is greater than 0, then aps_chroma_present_flag shall be equal to 1. ix. Additionally, constraints based on ChromaArrayType may be derived by PH or SH syntax elements. a) In one example, constraints based on ChromaArrayType may be defined similarly to those in the sixth embodiment. b) For example, the syntax element aps_chroma_present_flag may be constrained depending on the ChromaArrayType and the type of APS (e.g., ALF APS, SCALING APS, or LMCS APS). c) Alternatively, the value of ChromaArrayType may be constrained depending on the syntax element aps_chroma_present_flag and / or the type of APS. d) In one example, the value of aps_chroma_present_flag of an APS NAL unit having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph / slice_alf_aps_id_luma[i] is required to be equal to 0 if chromaArrayType is equal to 0. a. Additionally, alternatively, when chromaArrayType is greater than 0, the value of aps_chroma_present_flag of APS NAL units having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph / slice_alf_aps_id_chroma (and / or ph_cc_alf_cb_aps_id and / or ph_cc_alf_cr_aps_id) is required to be equal to 1. e) In one example, the value of aps_chroma_present_flag of an APS NAL unit with aps_params_type equal to SCALING_APS and adaptation_parameter_set_id equal to ph_scaling_list_aps_id is required to be equal to 0 if chromaArrayType is 0. a. Additionally, and alternatively, the value of aps_chroma_present_flag of an APS NAL unit having aps_params_type equal to SCALING_APS and adaptation_parameter_set_id equal to ph_scaling_list_aps_id shall be equal to 1 if chromaArrayType is greater than 0. f) In one example, the value of aps_chroma_present_flag of an APS NAL unit with aps_params_type equal to LMCS_APS and adaptation_parameter_set_id equal to ph_lmcs_aps_id is required to be equal to 0 if chromaArrayType is 0.

[0308] x. Additionally, alternatively, the value of aps_chroma_present_flag of an APS NAL unit with aps_params_type equal to LMCS_APS and adaptation_parameter_set_id equal to ph_lmcs_aps_id is required to be equal to 1 if chromaArrayType is greater than 0. Furthermore, the constraint based on ChromaArrayType is independent of the presence of an APS ID in the PH / SH and can be derived by the PH component or the SH component. a) In one example, the value of aps_chroma_present_flag of an APS NAL unit with aps_params_type equal to SCALING_APS and / or ALF_APS and / or LMCS APS is required to be equal to 0 if chromaArrayType is 0. b) Additionally, alternatively, the value of aps_chroma_present_flag of APS NAL units having aps_params_type equal to SCALING_APS APS and / or ALF_APS and / or LMCS APS is required to be equal to 1 if chromaArrayType is greater than 0. xi.

[0309] 2. For signaling of deblocking control to solve the second problem, for example, similar to the second embodiment, one or more of the following approaches are disclosed.

[0310] a. In one example, an N-bit (eg, N=2) deblocking mode indicator (eg, named deblocking_filter_mode_idc) is signaled. i. In one example, the syntax element deblocking_filter_mode_idc is u(2) coded. a) Alternatively, the parsing process of deblocking_filter_mode_idc is an unsigned integer of N (eg, N=2) bits. ii. In one example, the syntax element deblock_filter_mode_idc is signaled in the PPS. iii. In one example, the syntax element deblocking_filter_mode_idc is used to specify four modes: a) deblocking is completely disabled and not used for any slices, b) deblocking is used for all slices with β and tC offsets of zero value, c) deblocking is used for all slices with β and tC offsets signaled in the PPS, and d) deblocking is further controlled at either picture or slice level.

[0311] b. The syntax flag ph / slice_deblocking_filter_used_flag is signaled in PH or SH and specifies whether deblocking is used for the current picture / slice.

[0312] c. The syntax flag ph / slice_deblocking_parameters_override_flag is signaled in either PH or SH and specifies whether the β and tC offsets are overridden by the values ​​signaled in PH / SH. i. Also, the value of slice_deblocking_parameters_override_flag is inferred to be equal to 0 if not present.

[0313] d. In one example, syntax elements that specify deblocking control (eg, enable flag, disable flag, control flag, deblocking mode indicator, deblocking filter beta / tc parameters, etc.) may be signaled in the SPS. i. In one example, one or more syntax elements may be signaled in the SPS that specify whether deblocking is enabled in a video unit (eg, CLVS). ii. Also, when deblocking is disabled in SPS, the syntax element for PPS / PH / SH level deblocking on / off control in PPS / PH / SH is required to be equal to a specific value that specifies that deblocking is completely disabled and not used for all slices. iii. In one example, a deblocking filter control present flag may be signaled in the SPS. iv. For example, an N-bit (eg, N=2) deblocking mode indicator (eg, named deblocking_filter_mode_idc) may be signaled in the SPS. v. For example, the beta / tc deblocking parameters may be signaled in the SPS. vi. Whether deblocking is enabled, for example with a zero-valued beta / tc deblocking parameter, may depend on the SPS syntax element. vii. For example, deblocking can be applied at the SPS / PPS / PH / SH level and use the beta / tc deblocking parameters signaled in the SPS. viii. For example, deblocking may be applied at the SPS / PPS / PH / SH level and use zero-valued deblocking parameters signaled in the SPS.

[0314] 3. For the inference of the PPS syntax element single_slice_per_subpic_flag to solve the third problem, one or more of the following approaches are disclosed:

[0315] a. In one example, if no_pic_partition_flag is equal to 1, then single_slice_per_subpic_flag is inferred to be equal to 1, and the semantics of single_slice_per_subpic_flag is changed to, for example,

[0316] [ka]

[0317] 4. Regarding picture or slice QP delta signaling to solve the fourth problem, one or more of the following approaches are disclosed.

[0318] In one example, a picture or slice level chroma QP offset is always signaled in either PH or SH. i. For example, if the video content has a chroma component (e.g., ChromaArrayType is not equal to 0), then the chroma QP offsets at the picture or slice level may always be signaled, regardless of the current flag signaled in the PPS (e.g., pps_slice_chroma_qp_offsets_present_flag). ii. Alternatively, if the video content has a chroma component (e.g., ChromaArrayType is not equal to 0), the slice_cb_qp_offset and slice_cr_qp_offset syntax elements MAY always be present in the associated slice header, regardless of the PPS present flag (e.g., pps_slice_chroma_qp_offsets_present_flag). iii. Additionally, the presence flag (eg, pps_slice_chroma_qp_offsets_present_flag) specifying the presence of the slice_cb_qp_offset and slice_cr_qp_offset syntax elements may not be signaled.

[0319] b. In one example, pps_cu_qp_delta_enabled_flag may be used to specify the presence of cu_qp_delta_abs and cu_qp_delta_sign_flag in both transform unit syntax and palette coding syntax, and the semantics of pps_cu_qp_delta_enabled_flag is changed as follows:

[0320] [ka]

[0321] c. In one example, the luma QP delta may be signaled in both PH and SH. i. For example, the luma QP delta present flag may be signaled in the PPS and / or PH and / or SH. ii. For example, whether luma QP delta is signaled in PH / SH depends on the current flags in PPS and / or PH / SH. iii. For example, add the values ​​of PH luminance QPdelta and SH luminance QPdelta to obtain SliceQp Y It may also be used to calculate luminance quantization parameters such as:

[0322] d. In one example, the chroma QP offset may be signaled in both PH and SH. i. For example, the chroma QP offset present flag may be signaled in the PPS and / or the PH and / or the SH. ii. For example, whether chroma QP offset is signaled in PH / SH depends on the current flags in PPS and / or PH / SH. iii. For example, the PH chroma QP offset and SH chroma QP offset values ​​may be added together and used to derive the chroma quantization parameters for the Cb and Cr components.

[0323] 5. Regarding the chroma Qp mapping table, one or more of the following approaches are disclosed:

[0324] a. In one example, in the derivation process of the chroma QP table, an XOR operator is performed between (delta_qp_in_val_minus1[i][j]+1) and delta_qp_diff_val[i][j], for example, similar to the third embodiment.

[0325] b. In SPS, it is proposed to set a flag sps_multiple_sets_of_chroma_qp_table_present_flag. i. If sps_multiple_sets_of_chroma_qp_table_present_flag is equal to 0, only one set of chroma Qp mapping tables is allowed to be signaled. ii. If sps_multiple_sets_of_chroma_qp_table_present_flag is equal to 1, signaling multiple sets of chroma Qp mapping tables is allowed.

[0326] c. For sequences without B / P slices, signaling multiple sets of chroma Qp mapping tables may not be allowed.

[0327] 6. One or more of the following approaches are disclosed for sps_independent_subpics_flag and subpic_treated_as_pic_flag[i] to solve the sixth problem.

[0328] In one example, the presence of sps_independent_subpics_flag depends on whether the number of subpictures is greater than one. i. For example, sps_independent_subpics_flag is signaled only if the number of subpictures is greater than 1 (eg, (sps_num_subpics_minus1>0)). ii. For example, if the number of subpictures is equal to 1 (e.g., (sps_num_subpics_minus1==0), then the signaling of sps_independent_subpics_flag is skipped.

[0329] b. Also, if sps_independent_subpics_flag is not present, it is inferred to be equal to a constant value (e.g., 0 or 1).

[0330] c. In one example, if subpic_treated_as_pic_flag[i] is not present, it is inferred to be equal to a constant value (eg, 0 or 1).

[0331] d. In one example, if subpic_treated_as_pic_flag[i] is not present, it is inferred to be equal to a particular value that wraparound motion compensation is possible (or available). i. Also, if subpic_treated_as_pic_flag[i] is not present, it is inferred to be equal to a constant value that indicates horizontal wraparound motion compensation is possible (or available).

[0332] e. In one example, the inferred value of subpic_treated_as_pic_flag[i] may depend on whether the picture contains only one subpicture and / or whether the subpicture has the same width as this picture. i. In one example, if the width of the subpicture is the same as the picture, subpic_treated_as_pic_flag[i] may be inferred to be X (eg, X=0).

[0333] f. In one example, if sps_independent_subpics_flag is not present, the value of sps_indentent_subpics_flag may depend on other syntax elements or variables. i. For example, this inference value may depend on whether subpicture information is present (eg, whether subpic_info_present_flag is 0 or 1). ii. For example, if subpic_info_present_flag is 0 and sps_independent_subpics_flag is not present, it is inferred to be equal to a predetermined value (eg, 0 or 1). iii. For example, if subpic_info_present_flag is 1 and sps_independent_subpics_flag is not present, it is inferred to be equal to a predetermined value (eg, 0 or 1).

[0334] g. In one example, when subpic_treated_as_pic_flag[i] is not present, the value that subpic_treated_as_pic_flag[i] is inferred to may depend on the presence of subpicture information (e.g., subpic_info_present_flag) and / or the number of subpictures in the CL VS (e.g., sps_num_subpics_minus1) and / or sps_independent_subpics_flag. i. In one example, if subpic_info_present_flag is equal to 0 and subpic_treated_as_pic_flag[i] is not present, the value of subpic_treated_as_pic_flag[i] is inferred to be equal to a constant value (e.g., 0). ii. In one example, if subpic_info_present_flag is equal to 1 and subpic_treated_as_pic_flag[i] is not present, the value of subpic_treated_as_pic_flag[i] is inferred to be equal to a constant value (eg, 1). iii. In one example, if subpic_info_present_flag is equal to 1, sps_num_subpics_minus1 is equal to 0, and subpic_treated_as_pic_flag[i] is not present, then the value of subpic_treated_as_pic_flag[i] is inferred to be equal to a constant value (e.g., 0 or 1). iv. In one example, if subpic_info_present_flag is equal to 1, sps_num_subpics_minus1 is greater than 0, sps_independent_subpics_flag is equal to 1, and subpic_treated_as_pic_flag[i] is not present, then the value of subpic_treated_as_pic_flag[i] is inferred to be equal to a constant value (e.g., 0 or 1).

[0335] 7. How padding or clipping is performed on boundaries during the inter prediction process may depend on a combined check of the boundary type, wraparound padding or clipping indication (e.g., pps_ref_wraparound_enabled_flag, sps_ref_wraparound_enabled_flag, etc.) and indication of treating subpicture boundaries as picture boundaries (e.g., subpic_treated_as_pic_flag[i]).

[0336] a. For example, if one boundary is a picture boundary, then the wrap-around padding indication is true and wrap-around padding (or wrap-around clipping) may be applied without considering treating the sub-picture boundary as a picture boundary. i. In one example, this boundary must be a vertical boundary.

[0337] b. For example, if two vertical boundaries are both picture boundaries, then the wrap-around padding indication is true and wrap-around padding (or wrap-around clipping) may be applied without regard to the indication to treat sub-picture boundaries as picture boundaries.

[0338] c. In one example, the wraparound padding (or wraparound clipping) above may refer to horizontal wraparound padding / clipping.

[0339] 8. In one example, different indications for wrap-around padding or clipping may be signaled for different sub-pictures.

[0340] 9. In one example, different offsets for wrap-around padding or clipping may be signaled for different sub-pictures.

[0341] 10. In PH / SH, a variable X is used to indicate whether B slices are allowed / used in a picture / slice, and the variable is derived using one of the following methods: a) (rpl_info_in_ph_flag&&num_ref_entries[0][RplsIdx[0]]>0&&num_ref_entries[1][RplsIdx[1]]>0); b) (rpl_info_in_ph_flag&&num_ref_entries[1][RplsIdx[1]]>0); c) (rpl_info_in_ph_flag&&num_ref_entries[1][RplsIdx[1]]>1); d) (rpl_info_in_ph_flag&&num_ref_entries[1][RplsIdx[1]]>0); e) based on NumRefIdxActive in the VVC text (e.g., NumRefIdxActive for List 1 is greater than K (e.g., K=0)); f) Based on the number of allowed reference pictures for list 1.

[0342] 1) Alternatively, the signaling and / or semantics and / or inference of one or more syntax elements signaled in the PH may be changed based on the variable. i. In one example, one or more syntax elements are intended to enable coding tools that require multiple prediction signals, such as bi-directional prediction or mixed intra-inter coding, or prediction with linear / non-linear weighting from multiple prediction blocks. ii. In one example, the one or more syntax elements may include, but are not limited to: a) ph_collocated_from_I0_flag b) mvd_I1_zero_flag c) ph_disable_bdof_flag d) ph_disable_dmvr_flag e) num_I1_weights In one example, one or more syntax elements may be signaled only if the variable indicates that the picture may contain one or more B slices; otherwise, the signaling is skipped and the value of the syntax element is inferred.

[0343] [ka]

[0344] iv. In one example, if X is equal to 0 (or false), then mvd_l1_zero_flag is not signaled and its value is inferred to be 1. v. In one example, the inference of one or more syntax elements depends on the value of the first syntax element.

[0345] [ka]

[0346] c) In one example, if ph_temporal_mvp_enabled_flag and rpl_info_in_ph_flag are both equal to 1, and X is equal to 0 (or false), the value of ph_collocated_from_l0_flag is inferred to be equal to 1. d) In one example, if X is equal to 0 (or false), num_l1_weights is not signaled and its value is inferred to be 0, and as a result, weighted prediction parameters for reference picture list 1 are not signaled in the PH or SHs of the picture.

[0347] 11. It is proposed that the signaling of the indication of whether to split a picture into tiles / slices / sub-pictures (e.g., no_pic_partition_flag in the PPS) may be conditioned on the number of CTBs in the picture. 2) In one example, if the number of CTUs in a picture is equal to 1 (or less than 2), the no_pic_partition_flag is not signaled. 3) Alternatively, if the number of CTUs in a picture is equal to 1 (or less than 2), then no_pic_partition_flag is constrained to be equal to 0.

[0348] 12. With regard to improvements to the syntax and semantics of deblocking to solve the seventh problem, similar to the fourth embodiment, one or more of the following approaches are disclosed:

[0349] a. Whether the operation of the deblocking filter is disabled (or enabled) for a slice that references a PPS depends on both the deblocking syntax signaled in the PPS (e.g., pps_deblocking_filter_disabled_flag) and the deblocking syntax elements signaled at the picture or slice level. i. In one example, pps_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is disabled for the slice that references the PPS, unless otherwise indicated at the picture or slice level. ii. In one example, pps_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is enabled for the slice that references the PPS, unless otherwise indicated at the picture or slice level.

[0350] b. If slice_deblocking_filter_override_flag is not present, it is inferred to be equal to 0.

[0351] c. If the deblocking filter is disabled in the PPS and if you try to override the deblocking filter in the PH / SH, skip signaling the deblocking ON / OFF control flag in the PH / SH. i. In one example, whether a deblocking on / off control flag (e.g., ph_deblocking_filter_disabled_flag) is signaled in the PH may depend on whether deblocking is disabled in the PPS (e.g., whether the value of pps_deblocking_filter_disabled_flag is equal to 1) and / or whether an override flag in the SH (e.g., ph_deblocking_filter_override_flag is 1 or not). a) For example, if pps_deblocking_filter_disabled_flag and ph_deblocking_filter_override_flag are equal to 1, the signaling of ph_deblocking_filter_disabled_flag may be skipped. b) Alternatively, when deblocking_filter_override_enabled_flag, pps_deblocking_filter_disabled_flag and ph_deblocking_filter_override_flag are equal to 1, the notification of the signal ph_deblocking_filter_disabled_flag may be skipped. ii. Also, if ph_deblocking_filter_disabled_flag is not present, the following may be inferred: a) If deblocking_filter_override_enabled_flag, pps_deblocking_filter_disabled_flag and ph_deblocking_filter_override_flag are all equal to 1, the value of ph_deblocking_filter_disabled_flag is inferred to be equal to 0. b) Otherwise, the value of ph_deblocking_filter_disabled_flag is inferred to be equal to pps_deblocking_filter_disabled_flag. iii. Also, if ph_deblocking_filter_disabled_flag is not present, the following may be inferred: a) If pps_deblocking_filter_disabled_flag and ph_deblocking_filter_override_flag are all equal to 1, the value of ph_deblocking_filter_disabled_flag is inferred to be equal to 0. b) Otherwise, the value of ph_deblocking_filter_disabled_flag is inferred to be equal to pps_deblocking_filter_disabled_flag. iv. In one example, whether to signal a deblocking on / off control flag (e.g., slice_deblocking_filter_disabled_flag) in the SH may depend on whether deblocking is disabled in the PPS (e.g., whether the value of pps_deblocking_filter_disabled_flag is equal to 1) and / or an override flag (e.g., whether slice_deblocking_filter_override_flag is equal to 1) in the SH. a) In one example, if deblocking_filter_override_enabled_flag, pps_deblocking_filter_disabled_flag and slice_deblocking_filter_override_flag are equal to 1, signaling of slice_deblocking_filter_disabled_flag may be skipped. b) Alternatively, when pps_deblocking_filter_disabled_flag and slice_deblocking_filter_override_flag are 1, signaling of slice_deblocking_filter_disabled_flag may be skipped. v. Furthermore, if slice_deblocking_filter_disabled_flag is not present, the following can be inferred: a) If deblocking_filter_override_enabled_flag, pps_deblocking_filter_disabled_flag and slice_deblocking_filter_override_flag are all equal to 1, the value of slice_deblocking_filter_disabled_flag is inferred to be 0. b) Otherwise, the value of slice_deblocking_filter_disabled_flag is inferred to be equal to pps_deblocking_filter_disabled_flag. vi. Furthermore, if slice_deblocking_filter_disabled_flag is not present, the following can be inferred: a) If pps_deblocking_filter_disabled_flag and slice_deblocking_filter_override_flag are all equal to 1, the value of slice_deblocking_filter_disabled_flag is inferred to be equal to 0. b) Otherwise, the value of slice_deblocking_filter_disabled_flag is inferred to be equal to pps_deblocking_filter_disabled_flag.

[0352] 13. If sps_ibc_enabled_flag is equal to 1 and the block size is not smaller than 64x64, it is suggested to skip cu_skip_flag.

[0353] An example is shown in the fifth embodiment.

[0354] 14. A first syntax element (SE) may be added to the ALF APS to indicate whether chroma filtering information (e.g., chroma ALF, CC-ALF) is present, and the signaling of other syntax elements may be based on the value of the first SE.

[0355] In one example, if the first SE (eg, aps_chroma_present_flag in embodiment #6) indicates that chroma filtering information is not present, notification of luma filter information (eg, alf_luma_filter_signal_flag) is skipped. i. Otherwise, the luma filter information indication (eg, alf_luma_filter_signal_flag) is inferred to be true.

[0356] b. In one example, if the first SE (e.g., aps_chroma_present_flag in embodiment #6) indicates that chroma filtering information is present, the constraint that at least one of the chroma filter information indications (e.g., alf_chroma_filter_signal_flag, alf_cc_cb_filter_signal_flag, alf_cc_cr_filter_signal_flag) is true shall be satisfied.

[0357] 15. In the above example, the indication of the presence information of CC-ALF filtering can be replaced from two syntax elements (eg, alf_cc_cb_filter_signal_flag, alf_cc_cr_filter_signal_flag) by a syntax element (which may be a non-binary value, eg, alf_cc_filter_idc).

[0358] 16. In a conforming bitstream, the first coded slice in decoding order of an IRAP or GDR picture is required not to reference a suffix APS NAL unit.

[0359] a. For example, if the first coded slice in decoding order of a coded picture, firstSlice, has nal_unit_type equal to IDR_W_RADL, IDR_N_LP, CRA_NUT, GDR_NUT, then firstSlice shall not reference the suffixAPS NAL unit.

[0360] 17. The constraint on not allowing updates to the content of APS NAL units within a PU may exclude certain APS NAL units.

[0361] a. For example, a conforming bitstream requires that all APS NAL units with a particular value of adaptation_parameter_set_id and a particular value of aps_params_type within a PU have the same content, regardless of whether they are prefix or suffix APS NAL units, except for the suffix APS NAL unit associated with the last VCL NAL unit of the PU in decoding order.

[0362] b. Alternatively, a conforming bitstream requires that all APS NAL units within a PU with specific values ​​of nal_unit_type, adaptation_parameter_set_id, and a specific value of aps_params_type have the same content, except for the suffix APS NAL unit associated with the last VCL NAL unit in decoding order within the PU.

[0363] 18. In one example, "APS NAL unit content" refers to the bits in the APS RBSP, excluding adaptation_parameter_set_id and aps_params_type.

[0364] In one example, if SUFFIX APS NAL units are present in a PU, they shall not advance the last VCL NAL unit of the PU.

[0365] 19. It is required in a conforming bitstream that the last VCL NAL unit of a PU not be advanced if a SUFFIX APS NAL unit is present in the PU.

[0366] 20. Two APS NAL units with a specific value of adaptation_parameter_set_id and a specific value of aps_params_type within a PU are required in a conforming bitstream to have the same content if there are no VCL NAL units between the two APS NAL units, regardless of whether they are prefix or suffix APS NAL units.

[0367] [ka]

[0368] a. The method of signaling the APS ID (eg, adaptation_parameter_set_id) depends on the type of APS. i. In one example, for ALF APS, the APS ID may be coded by ue(v) or the K-th EG coding. ii. In one example, for LMCS and the scaling list APS, the APS ID may be coded by u(a) and u(b) respectively, where a is not equal to b. iii. In one example, for LMCS and the scaling list APS, the APS ID may be coded by ue(v) or the K-th EG coding.

[0369] b. In one example, the APS ID (e.g., adaptation_parameter_set_id) is coded by u(X), for example, X = 3. i. For example, the syntax of adaptation_parameter_set_id is changed as follows.

[0370]

Table 33

[0371] i. In one example, X may depend on the maximum allowable number of APSs for all types of APS. a. In one example, X is set to (X - (1 << log2(X)) == 0? log2(X) : (log2(X) + 1)).

[0372] c. It is proposed to set the maximum allowable signal absolute value of the ALF filter coefficients to be equal to (1 << K) - M (M is not equal to 0, for example, K = 7, M = 1). i. In one example, the range of the ALF filter-related syntax elements (e.g., alf_luma_coeff_abs[sfIdx][j], alf_chroma_coeff_abs[altIdx][j] in the alf_data() syntax structure) is within the range from 0 to Y, where Y is equal to 127.

[0373] [ka]

[0374] [ka]

[0375] d. In one example, the semantics of CCALF-related syntax elements (e.g., alf_cc_cb_mapped_coeff_abs[k][j], alf_cc_cr_mapped_coeff_abs[k][j] in the alf_data() syntax structure) are specified with value ranges to constrain the values ​​of the corresponding syntax elements to be within the valid range. i. For example, the values ​​of CCALF-related syntax elements (e.g., alf_cc_cb_mapped_coeff_abs[k][j], alf_cc_cr_mapped_coeff_abs[k][j]) must be in the range of X to Y, such as X=1, Y=8, etc.

[0376] [ka]

[0377] [ka]

[0378] e. In one example, instead of coding alf_cc_cb_mapped_coeff_abs[k][j] in the alf_data() syntax structure, the absolute value -1 (denoted as alf_cc_cb_mapped_coeff_abs_minus1[k][j]) may be coded, and the absolute value of the CC-ALF filter coefficient is derived as follows: (1-2*alf_cc_cb_coeff_sign[k][j])*2 alf_cc_cb_mapped_coeff_abs_minus1[k][j]+1. i. Alternatively, the signal-transmitted alf_cc_cb_mapped_coeff_abs_minus1[k][j] is within the range of [0, (1<<K)-1], where K is a positive integer (e.g., K = 3).

[0379] f. In one example, instead of coding alf_cc_cr_mapped_coeff_abs[k][j] in the alf_data() syntax structure, the absolute value -1 (denoted by alf_cc_cr_mapped_coeff_abs_minus1[k][j]) may be coded, and the absolute value of the CC-ALF filter coefficient is derived as follows. (1 - 2*alf_cc_cr_coeff_sign[k][j]) * 2 alf_cc_cr_mapped_coeff_abs_minus1[k][j]+1. i. Alternatively, the signal-transmitted alf_cc_cr_mapped_coeff_abs_minus1[k][j] is within the range of [0, (1<<K)-1], where K is a positive integer (e.g., K = 3).

[0380]

Chemical formula

[0381]

Chemical formula

[0382] a. In one example, constraints are defined to limit the total number of ALF APSs. i. For example, the total number of ALF APSs is not equal to the total number of SCALING APSs. ii. For example, the total number of ALF APSs may depend on the number of ALF filters (e.g., ALF luminance filter, ALF chrominance filter, CCALF Cb filter, CCALF Cr filter). iii. For example, in the standard, constraints are defined to limit the total number of ALF APSs to be equal to X (e.g., X = 328).

[0383] [ka]

[0384] b. In one example, constraints are defined to limit the total number of ALF luma filters, and / or ALF chroma filters, and / or CCALF filters. i. For example, a constraint is specified to limit the total number of ALF luma filters in all ALF APSs to be equal to X1 (eg, X=200). ii. For example, a constraint is defined to limit the total number of ALF chroma filters in all ALF APSs to be equal to X2 (eg, X=64). iii. For example, a constraint is defined to limit the total number of CCALF filters in all ALF APS to be equal to X3 (e.g., X=64). a) Alternatively, a constraint is defined to limit the total number of CCALF Cb filters in all ALF APS to be equal to Y1 (eg, Y1=32). b) A constraint is also defined to limit the total number of CCALF Cr filters in all ALF APS to be equal to Y2 (eg, Y2=32).

[0385] [ka]

[0386] vi. For example, a range is defined to constrain the value of ph / slice_num_alf_aps_ids_luma to be within the range of K1 to K2.

[0387] [ka]

[0388] [ka]

[0389] c. In one example, a range is defined to constrain the value of the ALF APS ID to be within the range of K1 to K2. i. For example, the range of ALF APS IDs (ph_alf_aps_id_luma[i], ph_alf_aps_id_chroma, ph_cc_alf_cb_aps_id, ph_cr_alf_cb_aps_id) signaled in the PH / SH may be constrained to be within the range K1 to K2.

[0390] [ka]

[0391] [ka]

[0392] [ka]

[0393] [ka]

[0394] [ka]

[0395] d. In one example, the binarization of the ALF APS ID (e.g., ph(slice)_alf_aps_id_luma[i], ph(slice)_alf_aps_id_chroma, ph(slice)_cc_alf_cb_aps_id, ph(slice)_cc_alf_cr_aps_id in the PH / SH syntax structure) may be ue(v) coded, for example, as in the eighth embodiment.

[0396] e. In one example, the binarization of the number of ALF APS (eg, ph(slice)_num_alf_aps_id_luma in the PH / SH syntax) may be ue(v) coded, for example, as in the eighth embodiment.

[0397] f. In one example, the binarization of the APS ID (eg, adaptation_parameter_set_id in the APS syntax structure) may depend on the type of APS, as in the eighth embodiment, for example. i. For example, if aps_params_type is equal to ALF_APS, adaptation_parameter_set_id is u(X1) coded, where X1=9. ii. For example, if aps_params_type is equal to LMCS_APS, adaptation_parameter_set_id is u(X2) coded, where X2=2. iii. For example, if aps_params_type is equal to SCALING_APS, adaptation_parameter_set_id is u(X3) coded, where X3=3.

[0398] g. In one example, whether the binarization of the APS ID (eg, adaptation_parameter_set_id in the APS syntax structure) is ue(v) coded may depend on the type of APS, for example, as in the ninth embodiment. i. For example, if aps_params_type is equal to ALF_APS, adaptation_parameter_set_id is ue(v) coded.

[0399] h. In one example, the binarization of the APS ID (eg, adaptation_parameter_set_id in the APS syntax structure) is ue(v) coded, for example, as in the tenth embodiment.

[0400] 23. It is required that all APS NALs of a particular type in a PU (eg, ALF APS, or LMCS APS, or SCALING APS) must be signaled before the last VCL NAL in the PU.

[0401] 24. It is required that all APS NALs of a particular type within a PU (eg, ALF APS, LMCS APS, or SCALING APS) must be signaled before the first VCL NAL within the PU.

[0402] 25. The number of a first set of APS NALs of a particular type (such as ALF APS, LMCS APS, or SCALING APS) used or referenced by a VCL NAL (as referenced by an APS index in a picture header or slice header) within a PU is required to be less than or equal to X (where X is an integer such as 8), although APS NALs in this first set may or may not be present within this PU.

[0403] In one example, X is signaled from the encoder to the decoder.

[0404] 26. The number of a first set of APS NALs of a particular type (such as ALF APS, LMCS APS, or SCALING APS) used or referenced by any VCL NAL (as referenced by an APS index in a picture header or slice header) in a PU (the APS NALs in this first set may or may not be in this PU) plus the number of a second set of APS NALs of a particular type (such as ALF APS, LMCS APS, or SCALING APS) not used or referenced by any VCL NAL (as referenced by an APS index in a picture header or slice header) in a PU (the APS NALs in this second set are in this PU) is required to be less than or equal to X (X is an integer such as 8).

[0405] In one example, X is signaled from the encoder to the decoder.

[0406] 27. If the reference picture with index=0 in Reference List 0 is a long-term reference picture, then at least one of the co-located picture reference pictures used for TMVP is required to be a long-term reference picture.

[0407] 28. If the reference picture with index=0 in Reference List 0 is a short-term reference picture, then at least one reference picture of the co-located pictures used for TMVP is required to be a short-term reference picture.

[0408] 29. If adaptive color transformation (ACT) is used within a block, the use of coding tool X can be prohibited.

[0409] a. You can also prohibit the use of ACT when using coding tool X within a block.

[0410] b. Coding tool X can be (abbreviation defined in JVET-Q2001). i. LFNST ii. MTS iii. Skip conversion iv. Dual Tree Coding v. Local Dual Tree Coding vi. Signature data not displayed vii. Dependent Quantization viii. LMCS

[0411] 30. In one example, a first syntax element (SE) indicating whether to signal a motion vector difference (MVD) for a reference picture list (RPL)-1 may depend on a second SE indicating whether reference picture list information is signaled in a picture header (PH) and the number of reference pictures in RPL-1 (e.g., the number of reference pictures is greater than 0) if RPL information is present in the PH.

[0412] a. In one example, the first SE may be mvd_l1_zero_flag as specified in JVET-Q2001.

[0413] b. In one example, the second SE may be rpl_info_in_ph_flag as specified in JVET-Q2001.

[0414] c. In one example, the number of reference pictures in RPL-1 may be set equal to num_ref_entries[1][RplsIdx[1]] as specified in JVET-Q2001.

[0415] d. The signaling of the first SE may depend on the following conditions: if(!rpl_info_in_ph_flag||num_ref_entries[1][RplsIdx[1]]>0) Alternatively, if this condition is true, a signal may be sent to the SE. ii. Alternatively, if this condition is false (e.g., rpl_info_in_ph_flag is true and num_ref_entries[1][RplsIdx[1]] is equal to 0), then the SE is not signaled and is not inferred.

[0416] e. If the first SE is not signaled, it is inferred to be value X. i. For example, X is equal to 0. ii. For example, X is equal to 1. iii. For example, X equals SE / variable. iv. For example, the derivation of X is based on or conditioned by one or more SEs / variables.

[0417] f. An example is shown in the eleventh embodiment.

[0418] An example is shown in the twelfth embodiment.

[0419] 31. In one example, whether to signal a first syntax element (SE) indicating whether to disable decoder motion vector refinement (DMVR) may depend on whether reference picture list (RPL) information is signaled in the picture header (PH) and, if RPL information is present in the PH, the number of reference pictures in RPL-1), and / or whether sps_dmvr_pic_present_flag is equal to 1.

[0420] a. In one example, the first SE may be ph_disable_dmvr_flag as specified in JVET-Q2001.

[0421] b. In one example, the second SE may be rpl_info_in_ph_flag as specified in JVET-Q2001.

[0422] c. In one example, the number of reference pictures in RPL-1 may be set equal to num_ref_entries[1][RplsIdx[1]] as specified in JVET-Q2001.

[0423] d. The signaling of the first SE may depend on the following conditions: if(sps_dmvr_pic_present_flag&&(!rpl_info_in_ph_flag||(num_ref_entries[1][RplsIdx[1]]>0))) i. Alternatively, if the condition is true, the SE may be signaled. ii. Alternatively or additionally, if the condition is false (e.g., if rpl_info_in_ph_flag is true and num_ref_entries[1][RplsIdx[1]] is equal to 0, or if sps_dmvr_pic_present_flag is false), the SE is not signaled and inferred.

[0424] e. If the first SE is not signaled, it is inferred to be value X. i. For example, X is equal to 0. ii. For example, X is equal to 1. iii. For example, X equals SE / variable. iv. For example, the derivation of X is based on or conditioned by one or more SEs / variables. a) In one example, if ph_disable_dmvr_flag is not present, the following applies: - If rpl_info_in_ph_flag is equal to 1 and num_ref_entries[1][RplsIdx[1]] is equal to 0, then ph_disable_dmvr_flag is inferred to be 1. - Otherwise (rpl_info_in_ph_flag is equal to 0 or num_ref_entries[1][RplsIdx[1]] is greater than 0), ph_disable_dmvr_flag is inferred to be (1-sps_dmvr_enabled_flag). b) For example, If ph_disable_dmvr_flag is not present, the following applies: - If sps_dmvr_enabled_flag is equal to 0, the value of ph_disable_dmvr_flag is inferred to be equal to 1. - Otherwise, the following applies: - If rpl_info_in_ph_flag is equal to 1 and num_ref_entries[1][RplsIdx[1]] is equal to 0, then ph_disable_dmvr_flag is inferred to be 1. - Otherwise, ph_disable_dmvr_flag is inferred to be 0. c) For example, If ph_disable_dmvr_flag is not present, the following applies: - If sps_dmvr_enabled_flag is equal to 0, the value of ph_disable_dmvr_flag is inferred to be equal to 1. - Otherwise, ph_disable_dmvr_flag is inferred as (rpl_info_in_ph_flag==1&&num_ref_entries[1][RplsIdx[1]==0)?1:0 d) For example, If ph_disable_dmvr_flag is not present, sps_dmvr_enabled_flag?((rpl_info_in_ph_flag==1&&num_ref_entries[1][RplsIdx[1]]==0)?1:0):1 is inferred. e) For example, If ph_disable_dmvr_flag is not present, it is inferred that (sps_dmvr_enabled_flag==0||((rpl_info_in_ph_flag==1&&num_ref_entries[1][RplsIdx[1]==0)?1:0.

[0425] f. An example is shown in the eleventh embodiment.

[0426] An example is shown in the twelfth embodiment.

[0427] 32. In one example, whether to signal a first syntax element (SE) indicating whether to disable bidirectional optical flow (BDOF) may depend on a second SE indicating whether reference picture list (RPL) information is signaled in the picture header (PH), and the number of reference pictures if RPL information is present in RPL-1 (e.g., the number of reference pictures is greater than 0), and / or sps_bdof_pic_present_flag, in which case the number of reference pictures is greater than 1.

[0428] a. In one example, the first SE may be the ph_disable_bdof_flag specified in JVET-Q2001.

[0429] b. In one example, the second SE may be rpl_info_in_ph_flag as specified in JVET-Q2001.

[0430] c. In one example, the number of reference pictures in RPL-1 may be set equal to num_ref_entries[1][RplsIdx[1]] as specified in JVET-Q2001.

[0431] d. The signaling of the first SE may depend on the following conditions: if(sps_bdof_pic_present_flag&&(!rpl_info_in_ph_flag||(num_ref_entries[1][RplsIdx[1]]>0))) Alternatively, if this condition is true, a signal may be sent to the SE. ii. Alternatively, if this condition is false (e.g., rpl_info_in_ph_flag is true and num_ref_entries[1][RplsIdx[1]] is equal to 0, or sps_bdof_pic_present_flag is false), then the SE is not signaled.

[0432] e. If the first SE is not signaled, it is inferred to be value X. i. For example, X is equal to 0. ii. For example, X is equal to 1. iii. For example, X equals SE / variable. iv. For example, the derivation of X is based on or conditioned by one or more SEs / variables. a) For example, If ph_disable_bdof_flag is not present, the following applies: - If sps_bdof_enabled_flag is equal to 0, the value of ph_disable_bdof_flag is inferred to be equal to 1. - Otherwise, the following applies: If rpl_info_in_ph_flag is equal to 1 and num_ref_entries[1][RplsIdx[1]] is equal to 0, then ph_disable_bdof_flag is inferred to be 1. o Otherwise, ph_disable_bdof_flag is inferred to be 0. b) For example, If ph_disable_bdof_flag is not present, the following applies: - If sps_bdof_enabled_flag is equal to 0, the value of ph_disable_bdof_flag is inferred to be equal to 1. - Otherwise, ph_disable_bdof_flag is inferred to be (rpl_info_in_ph_flag==1&&num_ref_entries[1][RplsIdx[1]]==0)?1:0. c) For example, If ph_disable_bdof_flag is not present, it is inferred to be equal to sps_bdof_enabled_flag?((rpl_info_in_ph_flag==1&&num_ref_entries[1][RplsIdx[1]]==0)?1:0):1. d) For example, If ph_disable_bdof_flag is not present, it is inferred to be equal to (sps_bdof_enabled_flag==0||((rpl_info_in_ph_flag==1&&num_ref_entries[1][RplsIdx[1]]==0)?1:0. e) In one example, if ph_disable_bdof_flag is not present, the following applies: - If rpl_info_in_ph_flag is 1 and num_ref_entries[1][RplsIdx[1]] is equal to 0, then ph_disable_bdof_flag is inferred to be 1. - Otherwise (rpl_info_in_ph_flag is equal to 0 or num_ref_entries[1][RplsIdx[1]] is greater than 0), ph_disable_bdof_flag is inferred to be (1-sps_bdof_enabled_flag).

[0433] f. An example is shown in the eleventh embodiment.

[0434] An example is shown in the twelfth embodiment.

[0435] 33. In one example, whether to signal a first syntax element (SE) indicating whether a co-located picture used for temporal motion vector prediction is derived from reference picture list 0 may depend on a second SE indicating whether to signal reference picture list (RPL) information in the picture header (PH), and the number of reference pictures in RPL-1 if RPL information is present in the PH (e.g., the number of reference pictures is greater than 0), and whether TMVP is enabled for the picture (e.g., ph_temporal_mvp_enabled_flag).

[0436] a. In one example, the first SE may be the ph_collocated_from_l0_flag specified in JVET-Q2001.

[0437] b. In one example, the second SE may be rpl_info_in_ph_flag as specified in JVET-Q2001.

[0438] c. In one example, the number of reference pictures in RPL-1 may be set equal to num_ref_entries[1][RplsIdx[1]] as specified in JVET-Q2001.

[0439] d. In one example, the first SE may be signaled if the following condition is true: if(ph_temporal_mvp_enabled_flag&&(!rpl_info_in_ph_flag|| num_ref_entries[1][RplsIdx[1]]>0) i. Alternatively, if this condition is true, the first SE may be signaled. ii. Alternatively, if this condition is false (e.g., if rpl_info_in_ph_flag is true and num_ref_entries[1][RplsIdx[1]] is equal to 0, or if ph_temporal_mvp_enabled_flag is false), then the SE is not signaled and is not inferred.

[0440] e. In one example, the first SE may be signaled if the following condition is true: if(ph_temporal_mvp_enabled_flag&&rpl_info_in_ph_flag&&num_ref_entries[1][RplsIdx[1]]>0) i. Alternatively, if this condition is true, the first SE may be signaled. ii. Alternatively, if this condition is false (e.g., if rpl_info_in_ph_flag is true and num_ref_entries[1][RplsIdx[1]] is equal to 0, or if ph_temporal_mvp_enabled_flag is false), then the SE is not signaled and is not inferred.

[0441] f. If the first SE is not signaled, it is inferred to be value X. i. For example, X is equal to 0. ii. For example, X is equal to 1. iii. For example, X equals SE / variable. iv. For example, the derivation of X is based on or conditioned by one or more SEs / variables.

[0442] An example is shown in the eleventh embodiment.

[0443] h. An example is shown in the twelfth embodiment.

[0444] 34. Whether to signal pred_weight_table() may depend on a second SE indicating whether weighted prediction (WP) information is signaled in the PH, and whether reference picture list (RPL) information is signaled in the picture header (PH), the number of reference pictures in RPL-1 if RPL information is present in the PH (e.g., the number of reference pictures is greater than 0), and pps_weighted_pred_flag and / or pps_weighted_bipred_flag.

[0445] [ka]

[0446] Alternatively, if this condition is true, pred_weight_table() may be signaled with PH. ii. Alternatively, and additionally, if the condition is false (e.g., pps_weighted_bipred_flag, wp_info_in_ph_flag, and rpl_info_in_ph_flag are true and num_ref_entries[1][RplsIdx[1]] is equal to 0, or ph_temporal_mvp_enabled_flag is false), pred_weight_table() does not signal.

[0447] 35. Whether to signal num_l1_weights in pred_weight_table() depends on whether weighted prediction (WP) information is signaled in PH, and It may depend on the second SE indicating whether reference picture list (RPL) information is signaled in the PH, the number of reference pictures in RPL1 (e.g., greater than 0) if RPL information is in the picture header (PH), and pps_weighted_bipred_flag.

[0448] [ka]

[0449] ii. Alternatively, if this condition is true, num_l1_weights may be signaled in PH. iii. Alternatively, and further, if this condition is false (e.g., if any one of pps_weighted_bipred_flag, wp_info_in_ph_flag, and num_ref_entries[1][RplsIdx[1]] is equal to 0), then num_l1_weights is not signaled or inferred (e.g., is 0).

[0450] [ka]

[0451] b) Alternatively, if this condition is false, then num_l1_weights is not signaled, its value is not inferred, and the derivation of the variable NumWeightsL1 may depend on one or more of whether WP information is signaled in PH (e.g., wp_info_in_ph_flag), whether RPL is signaled in PH (e.g., rpl_info_in_ph_flag), and whether the number of reference entries in RPL-1 is equal to 0, as follows:

[0452] [ka]

[0453] b. An example is shown in the eleventh embodiment.

[0454] c. An example is shown in the twelfth embodiment.

[0455] 36. In one example, the APS ID (i.e., syntax element adaptation_parameter_set_id) is coded as u(3) instead of u(5).

[0456] In one example, the current 5-bit adaptation_parameter_set_id is further split into two syntax elements: aps_reserved_zero_2bits coded as u(2) and adaptation_parameter_set_id coded as u(3). In this way, if there is a need in the future to identify more types of APS and more than 3 bits are required for the APS ID, the 2 reserved bits can be utilized to maintain backward compatibility with previous versions of VVC. i. In one example, furthermore, the semantics of these two syntax elements are as follows: aps_reserved_zero_2bits shall be equal to 0 in bitstreams conforming to this version of the specification. Values ​​greater than 0 for aps_reserved_zero_2bits are reserved for future use by ITU-T|ISO / IEC. adaptation_parameter_set_id provides an identifier to the APS for reference by other syntax elements.

[0457] b. In one example, the current 5-bit adapting_parameter_set_id is further split into two syntax elements: aps_reserved_zero_bit coded as u(1), followed by adaptation_parameter_set_id coded as u(3), and another bit is used for other things, such as flags specifying the presence of chroma-related syntax elements in the APS. This allows for future APS type specification that requires more than three bits for the APS ID to utilize the reserved bit in a manner that is backwards compatible with previous versions of VVC. i. In one example, the semantics of these two syntax elements are as follows: aps_reserved_zero_bit shall be equal to 0 in bitstreams conforming to this version of the specification. A value of 1 for aps_reserved_zero_bit is reserved for future use by ITU-T and ISO / IEC. adaptation_parameter_set_id provides an identifier for the APS for reference by other syntax elements.

[0458] 37. What is the general constraint flag parsing order for solving problem 13?

[0459] In one example, the categorized syntax elements are grouped according to rules in a general constraint information general_constraint_info() syntax structure. The general constraint information syntax structure includes a set of syntax elements that indicate whether to impose one or more specific constraints on the video bitstream, for example, in terms of constraining the values ​​of SPS / PPS / PH / SH syntax elements to disable coding tools or features in the video bitstream. i. For example, rules are defined as inter-related syntax elements and intra-related syntax elements. ii. For example, the rules define coding tool related syntax elements and feature related syntax elements.

[0460] 38. Whether to signal an indication to allow intra slices within a picture (e.g., ph_intra_slice_allowed_flag) may depend on whether inter slices are allowed (e.g., ph_inter_slice_allowed_flag) and whether one or more partitions (multiple slices / tiles) exist.

[0461] [ka]

[0462] [ka]

[0463] 6.1. First embodiment This is an embodiment of item 1 summarized in section 5 above.

[0464] 6.1.1.1. Implementation of 1.ai ph_scaling_list_aps_id specifies the adaptation_parameter_set_id of the scaling list APS. The TemporalId of an APS NAL unit with aps_params_type equal to SCALING_APS and adaptation_parameter_set_id equal to ph_scaling_list_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0465] [ka]

[0466] If scaling_list_chroma_present_flag is equal to 1, it specifies that the chroma scaling list is present in scaling_list_data(). If scaling_list_chroma_present_flag is equal to 0, it specifies that the chroma scaling list is not present in scaling_list_data(). [It is a bitstream conformance requirement that scaling_list_chroma_present_flag must be equal to 0 if ChromaArrayType is equal to 0, and equal to 1 if ChromaArrayType is not equal to 0.]

[0467] 6.1.2. Implementation of 1.a.ii ph_scaling_list_aps_id specifies the adaptation_parameter_set_id of the scaling list APS. The TemporalId of an APS NAL unit with aps_params_type equal to SCALING_APS and adaptation_parameter_set_id equal to ph_scaling_list_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0468] [ka]

[0469] scaling_list_chroma_present_flag equal to 1 specifies the presence of a chroma scaling list in scaling_list_data(). scaling_list_chroma_present_flag equal to 0 specifies the absence of a chroma scaling list in scaling_list_data(). [[It is a bitstream conformance requirement that scaling_list_chroma_present_flag equal to 0 if ChromaArrayType equals 0, and equal to 1 if ChromaArrayType is not equal to 0.]]

[0470] 6.1.3. Implementation of 1.bi ph_lmcs_aps_id specifies the adaptation_parameter_set_id of the LMCS APS referenced by the slice associated with the PH. The TemporalId of an APS NAL unit whose aps_params_type is equal to LMCS_APS and whose adaptation_parameter_set_id is ph_lmcs_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0471] [ka]

[0472] 6.1.4. Implementation of 1.b.ii ph_lmcs_aps_id specifies the adaptation_parameter_set_id of the LMCS APS referenced by the slice associated with the PH. The TemporalId of an APS NAL unit whose aps_params_type is equal to LMCS_APS and whose adaptation_parameter_set_id is ph_lmcs_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0473] [ka]

[0474] 6.1.5. Implementation of 1.ci The semantics of the PH syntax elements are modified as follows: ph_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luminance component of the slice associated with PH. The value of alf_luma_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i]. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the picture associated with the PH.

[0475] [ka]

[0476] The semantics of SH syntax elements are modified as follows: … slice_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luma component of the slice. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_luma[i] is not present, the value of slice_alf_aps_id_luma[i] is inferred to be equal to the value of ph_alf_aps_id_luma[i]. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the coded slice NAL unit. The value of alf_luma_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_alf_aps_id_luma[i].

[0477] [ka]

[0478] Then, the semantics of APS syntax elements in the ALF data syntax structure are modified as follows: … alf_chroma_filter_signal_flag equal to 1 specifies that the chroma filter is signaled. alf_chroma_filter_signal_flag equal to 0 specifies that the chroma filter is not signaled. [[If ChromaArrayType is equal to 0, then alf_chroma_filter_signal_flag shall be equal to 0.]] … alf_cc_cb_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cb color component is signaled. alf_cc_cb_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cb color component is not signaled. [[If ChromaArrayType is equal to 0, then alf_cc_cb_filter_signal_flag shall be equal to 0.]] When alf_cc_cr_filter_signal_flag is equal to 1, it specifies that the cross-component filter for the Cr color component is signaled. When alf_cc_cr_filter_signal_flag is equal to 0, it specifies that the cross-component filter for the Cr color component is not signaled. [[If ChromaArrayType is equal to 0, alf_cc_cr_filter_signal_flag shall be equal to 0.]]

[0479] 6.1.6. Implementation of 1.c.ii The semantics of the PH syntax elements are modified as follows:

[0480] ph_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luminance component of the slice associated with PH. The value of alf_luma_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i]. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the picture associated with the PH.

[0481] [ka]

[0482] ph_alf_chroma_idc equal to 0 indicates that the adaptive loop filter is not applied to the Cb and Cr color components. ph_alf_chroma_idc equal to 1 indicates that the adaptive loop filter is applied to the Cb color component. ph_alf_chroma_idc equal to 2 indicates that the adaptive loop filter is applied to the Cr color component. ph_alf_chroma_idc equal to 3 indicates that the adaptive loop filter is applied to the Cb and Cr color components. If ph_alf_chroma_idc is not present, it is inferred to be equal to 0. …

[0483] The semantics of SH syntax elements are modified as follows: … slice_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luma component of the slice. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_luma[i] is not present, the value of slice_alf_aps_id_luma[i] is inferred to be equal to the value of ph_alf_aps_id_luma[i]. The TemporalId of an APSNAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the coded slice NAL unit.

[0484] The value of alf_luma_filter_signal_flag of an APSNAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_luma[i] shall be equal to 1.

[0485] [ka]

[0486] Then, the semantics of APS syntax elements in the ALF data syntax structure are modified as follows: … alf_chroma_filter_signal_flag equal to 1 specifies that the chroma filter is signaled. alf_chroma_filter_signal_flag equal to 0 specifies that the chroma filter is not signaled. [[If ChromaArrayType is equal to 0, then alf_chroma_filter_signal_flag shall be equal to 0.]] … alf_cc_cb_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cb color component is signaled. If alf_cc_cb_filter_signal_flag equal to 0, it specifies that the cross-component filter for the Cb color component is not signaled. [[If ChromaArrayType is equal to 0, then alf_cc_cb_filter_signal_flag shall be equal to 0.]] alf_cc_cr_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cr color component is signaled. alf_cc_cr_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cr color component is not signaled. [[If ChromaArrayType is equal to 0, alf_cc_cr_filter_signal_flag shall be equal to 0.]]

[0487] 6.1.7. Implementation of 1.c.iii The semantics of the PH syntax elements are modified as follows: … ph_alf_aps_id_chroma specifies the adaptation_parameter_set_id of the ALF APS referenced by the chroma component of the slice associated with the PH. The value of alf_chroma_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_chroma.

[0488] [ka]

[0489] ph_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id of the ALF APS referenced by the Cb color component of the slice associated with the PH. The value of alf_cc_cb_filter_signal_flag shall be equal to 1 for APS NAL units whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to ph_cc_alf_cb_aps_id.

[0490] [ka]

[0491] ph_cc_alf_cr_aps_id specifies the adaptation_parameter_set_id of the ALF APS referenced by the Cr color component of the slice associated with the PH. The value of alf_cc_cr_filter_signal_flag shall be equal to 1 for APS NAL units whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to ph_cc_alf_cr_aps_id.

[0492] [ka]

[0493] The semantics of SH syntax elements are modified as follows: … slice_alf_aps_id_chroma specifies the adaptation_parameter_set_id of the ALF APS to which the chroma component of the slice refers. The TemporalId of an APS NAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_chroma shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_chroma is not present, the value of slice_alf_aps_id_chroma is inferred to be equal to the value of ph_alf_aps_id_chroma.

[0494] The value of alf_chroma_filter_signal_flag shall be equal to 1 for APS NAL units whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_chroma.

[0495] [ka]

[0496] slice_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id referenced by the Cb color component of the slice. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cb_aps_id shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_cc_alf_cb_enabled_flag equals 1 and slice_cc_alf_cb_aps_id is not present, the value of slice_cc_alf_cb_aps_id is inferred to be equal to the value of ph_cc_alf_cb_aps_id. The value of alf_cc_cb_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cb_aps_id.

[0497] [ka]

[0498] slice_cc_alf_cr_aps_id specifies the adaptation_parameter_set_id to which the Cr color component of the slice refers. The TemporalId of an APS NAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is slice_cc_alf_cr_aps_id shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_cc_alf_cr_enabled_flag is equal to 1 and slice_cc_alf_cr_aps_id is not present, the value of slice_cc_alf_cr_aps_id is inferred to be equal to the value of ph_cc_alf_cr_aps_id.

[0499] The value of alf_cc_cr_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cr_aps_id.

[0500] [ka]

[0501] The semantics of the APS syntax elements are then modified as follows: … alf_chroma_filter_signal_flag equal to 1 indicates that the chroma filter is signaled. alf_chroma_filter_signal_flag equal to 0 indicates that the chroma filter is not signaled. [[If ChromaArrayType is equal to 0, then alf_chroma_filter_signal_flag shall be equal to 0.]] …

[0502] alf_cc_cb_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cb color component is signaled. alf_cc_cb_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cb color component is not signaled. [[If ChromaArrayType is equal to 0, then alf_cc_cb_filter_signal_flag shall be equal to 0.]]

[0503] alf_cc_cr_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cr color component is signaled. alf_cc_cr_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cr color component is not signaled. [[If ChromaArrayType is equal to 0, then alf_cc_cr_filter_signal_flag shall be equal to 0.]] …

[0504] 6.1.8. Implementation of 1.di The semantics of APS syntax elements in the ALF data syntax structure are modified as follows: … alf_chroma_filter_signal_flag equal to 1 indicates that the chroma filter is signaled. alf_chroma_filter_signal_flag equal to 0 indicates that the chroma filter is not signaled. [[If ChromaArrayType is equal to 0, then alf_chroma_filter_signal_flag shall be equal to 0.]] … alf_cc_cb_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cb color component is signaled. alf_cc_cb_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cb color component is not signaled. [[If ChromaArrayType is equal to 0, then alf_cc_cb_filter_signal_flag shall be equal to 0.]] alf_cc_cr_filter_signal_flag equal to 1 specifies that the cross-component filter for the Cr color component is signaled. alf_cc_cr_filter_signal_flag equal to 0 specifies that the cross-component filter for the Cr color component is not signaled. [[If ChromaArrayType is equal to 0, then alf_cc_cr_filter_signal_flag shall be equal to 0.]] …

[0505] 6.1.9. Implementation of 1.d.ii The semantics of the APS syntax elements in the SCALING LIST data syntax structure are modified as follows: … scaling_list_chroma_present_flag equal to 1 specifies the presence of a chroma scaling list in scaling_list_data(). scaling_list_chroma_present_flag equal to 0 specifies the absence of a chroma scaling list in scaling_list_data(). It is a bitstream conformance requirement that [[scaling_list_chroma_present_flag MUST be 0 if ChromaArrayType is equal to 0, or 1 if ChromaArrayType is not equal to 0...]]

[0506] 6.1.10. Implementations of 1.e and 1.f ph_scaling_list_aps_id specifies the adaptation_parameter_set_id of the scaling list APS.

[0507] [ka]

[0508] ph_lmcs_aps_id specifies the adaptation_parameter_set_id of the LMCS APS referenced by the slice associated with the PH.

[0509] [ka]

[0510] ph_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luminance component of the slice associated with PH.

[0511] [ka]

[0512] ph_alf_chroma_idc equal to 0 indicates that the adaptive loop filter is not applied to the Cb and Cr color components. ph_alf_chroma_idc equal to 1 indicates that the adaptive loop filter is applied to the Cb color component. ph_alf_chroma_idc equal to 2 indicates that the adaptive loop filter is applied to the Cr color component. ph_alf_chroma_idc equal to 3 indicates that the adaptive loop filter is applied to the Cb and Cr color components. If ph_alf_chroma_idc is not present, it is inferred to be equal to 0.

[0513] ph_alf_aps_id_chroma specifies the adaptation_parameter_set_id of the ALF APS referenced by the chroma component of the slice associated with the PH.

[0514] [ka]

[0515] ph_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id of the ALF APS referenced by the Cb color component of the slice associated with the PH.

[0516] [ka]

[0517] ph_cc_alf_cr_aps_id specifies the adaptation_parameter_set_id of the ALF APS referenced by the Cr color component of the slice associated with the PH.

[0518] [ka]

[0519] slice_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luma component of the slice. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_luma[i] is not present, the value of slice_alf_aps_id_luma[i] is inferred to be equal to the value of ph_alf_aps_id_luma[i].

[0520] [ka]

[0521] slice_alf_aps_id_chroma specifies the adaptation_parameter_set_id of the ALF APS to which the chroma component of the slice refers. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_chroma is not present, the value of slice_alf_aps_id_chroma is inferred to be equal to the value of ph_alf_aps_id_chroma.

[0522] [ka]

[0523] slice_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id referenced by the Cb color component of the slice. If slice_cc_alf_cb_enabled_flag is equal to 1 and slice_cc_alf_cb_aps_id is not present, the value of slice_cc_alf_cb_aps_id is inferred to be equal to the value of ph_cc_alf_cb_aps_id.

[0524] [ka]

[0525] slice_cc_alf_cr_aps_id specifies the adaptation_parameter_set_id referenced by the Cr color component of the slice. If slice_cc_alf_cr_enabled_flag is equal to 1 and slice_cc_alf_cr_aps_id is not present, the value of slice_cc_alf_cr_aps_id is inferred to be equal to the value of ph_cc_alf_cr_aps_id.

[0526] [ka]

[0527] 6.1.11.1.g Embodiment The semantics of SH syntax elements are modified as follows:

[0528] [ka]

[0529] slice_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id referenced by the Cb color component of the slice.

[0530] [ka]

[0531] [ka]

[0532] 6.2. Second embodiment This is a collection of embodiments of item 2 (2.a to 2.c) summarized in Chapter 5 above. The syntax structure pic_parameter_set_rbsp() is changed as follows:

[0533] [Table 34]

[0534] [ka]

[0535] [[deblocking_filter_control_present_flag equal to 1 specifies the presence of a deblocking filter control syntax element in the PPS. deblocking_filter_control_present_flag equal to 0 specifies the absence of a deblocking filter control syntax element in the PPS.

[0536] deblocking_filter_override_enabled_flag equal to 1 specifies the presence of ph_deblocking_filter_override_flag in the PH referencing the PPS or specifies the presence of slice_deblocking_filter_override_flag in the slice header referencing the PPS. deblocking_filter_override_enabled_flag equal to 0 specifies the absence of ph_deblocking_filter_override_flag in the PH referencing the PPS or specifies the absence of slice_deblocking_filter_override_flag in the slice header referencing the PPS. If not present, the value of deblocking_filter_override_enabled_flag equal to 0 is inferred.

[0537] pps_deblocking_filter_disabled_flag equal to 1 specifies that the deblocking filter operation is not applied to slices that refer to PPSs for which slice_deblocking_filter_disabled_flag is not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the deblocking filter operation is applied to slices that refer to PPSs for which slice_deblocking_filter_disabled_flag is not present. If not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0.

[0538] dbf_info_in_ph_flag equal to 1 specifies that deblocking filter information is present in PH syntax structures and not present in slice headers that reference PPSs that do not contain PH syntax structures. dbf_info_in_ph_flag equal to 0 specifies that deblocking filter information is not present in PH syntax structures and may be present in slice headers that reference PPSs that do not contain PH syntax structures. [[If not present, the value of dbf_info_in_ph_flag is inferred to be equal to 0.]] ...

[0539] Then the syntax structure picture_header_structure() is changed as follows:

[0540] [Table 35]

[0541] [ka]

[0542] [ka]

[0543] [[ph_deblocking_filter_disabled_flag equal to 1 specifies that the operation of a deblocking filter is not applied to the slice associated with the PH. ph_deblocking_filter_disabled_flag equal to 0 specifies that the operation of a deblocking filter is applied to the slice associated with the PH. If ph_deblocking_filter_disabled_flag is not present, it is inferred to be equal to pps_deblocking_filter_disabled_flag.]] ...

[0544] Then the syntax structure slice_header() is changed as follows:

[0545] [Table 36]

[0546] [ka]

[0547] [ka]

[0548] [[slice_deblocking_filter_disabled_flag equal to 1 specifies that the deblocking filter operation is not applied to the current slice. slice_deblocking_filter_disabled_flag equal to 0 specifies that the deblocking filter operation is applied to the current slice. If slice_deblocking_filter_disabled_flag is not present, it is inferred to be equal to ph_deblocking_filter_disabled_flag.]] ...

[0549] Then, the decoding process of the deblocking filter process is changed as follows.

[0550] 8.8.3 Deblocking Filtering

[0551] 8.8.3.1 General Deblocking filtering is applied to all coding sub-block edges and transform block edges of a picture, except for the following types of edges: - edges on the border of the picture, - Edges that coincide with the boundary of the subpicture with subpicture index subpicIdx and loop_filter_across_subpic_enabled_flag[subpicIdx] equal to 0. - If VirtualBoundariesPresentFlag is 1, the edges that match the virtual boundaries of the picture - If loop_filter_across_tiles_enabled_flag is 0, edges that match tile boundaries - If loop_filter_across_slices_enabled_flag is 0, edges that meet slice boundaries [ka]

[0552] - Edges that do not correspond to the 4x4 sample grid boundaries of the luminance component - Edges that do not correspond to the 8x8 sample grid boundaries of the chroma component - An edge in the luminance component, if both sides of the edge have intra_bdpcm_luma_flag equal to 1, - An edge within the chroma component, if both sides of the edge have intra_bdpcm_chroma_flag equal to 1, - The edges of a chroma block that are not edges of the associated transform unit

[0553] The type of edge is either vertical or horizontal and is represented by the variable edgeType, as specified in Table 42.

[0554] [Table 37]

[0555] [ka]

[0556] The variable treeType is set equal to DUAL_TREE_LUMA. - the variable treeType, as specified in subclause 8.8.3.2, and the array recPicture set equal to the reconstructed picture before deblocking, i.e., EDGE_VER. L and the variable edgeType as input, perform unidirectional deblocking filtering, and generate the modified reconstructed picture after deblocking, i.e., the array recPicture L The output is used to filter vertical edges. - the variable treeType, as specified in subclause 8.8.3.2, and the array recPicture set equal to the modified reconstructed picture after deblocking, i.e., EDGE_HOR. L and the variable edgeType as input, perform unidirectional deblocking filtering, and generate the modified reconstructed picture after deblocking, i.e., the array recPicture L The horizontal edges are filtered using the output. - If ChromaArrayType is not equal to 0, the following applies: - Set the variable treeType equal to DUAL_TREE_CHROMA. - the variable treeType, the reconstructed picture before deblocking, i.e., the array recPicture, as specified in subclause 8.8.3.2 cb ,recPicture cr , and a variable edgeType set equal to EDGE_VER, to filter vertical edges and return the deblocked, modified reconstructed picture, i.e., the array recPicture. cb ,recPicture cr is reconstructed as the output. - the variable treeType, the modified reconstructed picture before deblocking, i.e., the array recPicture, as specified in subclause 8.8.3.2 cb ,recPicture cr, and the variable edgeType set equal to EDGE_HOR, to filter the horizontal edges and return the deblocked, modified reconstructed picture, i.e., the array recPicture. cb ,recPicture cr is reconstructed as the output.

[0557] 6.3. Third embodiment Changes shown in bold italics are based on JVET-Q2001-vE. The i-th chroma QP mapping table ChromaQpTable[i], where i=0...numQpTables-1, is derived as follows:

[0558] qpInVal[i][0]=qp_table_start_minus26[i]+26 qpOutVal[i][0]=qpInVal[i][0]

[0559] [ka] ChromaQpTable[i][qpInVal[i][0]]=qpOutVal[i][0] for(k=qpInVal[i][0]-1;k>=-QpBdOffset;k--) ChromaQpTable[i][k]=Clip3(-QpBdOffset,63,ChromaQpTable[i][k+1]-1) for(j=0;j<=num_points_in_qp_table_minus1[i];j++){ sh=(delta_qp_in_val_minus1[i][j]+1)>>1 for(k=qpInVal[i][j]+1,m=1;k<=qpInval[i][j+1];k++,m++) ChromaQpTable[i][k]=ChromaQpTable[i][qpInVal[i][j]]+ ((qpOutVal[i][j+1]-qpOutVal[i][j])*m+sh) / (delta_qp_in_val_minus1[i][j]+1) } for(k=qpInVal[i][num_points_in_qp_table_minus1[i]+1]+1;k<=63;k++) ChromaQpTable[i][k]=Clip3(-QpBdOffset,63,ChromaQpTable[i][k-1]+1)

[0560] If same_qp_table_for_chroma is equal to 1, ChromaQpTable[1][k] and ChromaQpTable[2][k] are set equal to ChromaQpTable[0][k], for k in the range of -QpBdOffset to 63.

[0561] Bitstream conformance requires that the values ​​of qpInVal[i][j] and qpOutVal[i][j] be in the range of -QpBdOffset to 63, with i in the range of 0 to numQpTables-1, and j in the range of 0 to num_points_in_qp_table_minus1[i]+1.

[0562] 6.4. Fourth embodiment PPS semantics (based on the text of JVET-R0159-v2, excluding the SPS flag). ...

[0563] [ka]

[0564] deblocking_filter_override_enabled_flag equal to 1 specifies the presence of ph_deblocking_filter_override_flag in the PH referencing the PPS or specifies the presence of slice_deblocking_filter_override_flag in the slice header referencing the PPS. deblocking_filter_override_enabled_flag equal to 0 specifies the absence of ph_deblocking_filter_override_flag in the PH referencing the PPS or specifies the absence of slice_deblocking_filter_override_flag in the slice header referencing the PPS. If not present, the value of deblocking_filter_override_enabled_flag equal to 0 is inferred.

[0565] [[pps_deblocking_filter_disabled_flag equal to 1 specifies that the deblocking filter operation is not applied to slices that refer to PPSs for which slice_deblocking_filter_disabled_flag and ph_deblockig_filter_disabled_flag are not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the deblocking filter operation is applied to slices that refer to PPSs for which slice_deblocking_filter_disabled_flag and ph_deblockig_disabled_flag are not present. If not present, the value of pps_deblocking_filter_disabled_flag equal to 0 is inferred. or

[0566] pps_deblocking_filter_disabled_flag equal to 1 specifies that deblocking filter operation is not applied to slices that reference the PPS if deblocking_filter_override_enabled_flag is equal to 0. pps_deblocking_filter_disabled_flag equal to 0 specifies that deblocking filter operation is applied to slices that reference the PPS if deblocking_filter_override_enabled_flag is 0. If not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0.

[0567] [ka]

[0568] The syntax structure picture_header_structure() is modified as follows:

[0569] [Table 38]

[0570] … ph_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in PH. ph_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in PH. If not present, the value of ph_deblocking_filter_override_flag is inferred to be equal to 0.

[0571] ph_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is not applied to the slice associated with PH, and there is no slice_deblocking_filter_disabled_flag. [Note: If ph_deblocking_filter_disabled_flag is present, then slice_deblocking_filter_disabled_flag is not present in the SH of any slice of the image, and therefore is removed. ]]] ph_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is applied to the slice associated with PH, and there is no slice_deblocking_filter_disabled_flag. [[Note: If ph_deblocking_filter_disabled_flag is present, then slice_deblocking_filter_disabled_flag is not present in the SH of any slice of the image, and therefore is removed. ]]]

[0572] [ka]

[0573] Then the syntax structure slice_header() is changed as follows:

[0574] [Table 39]

[0575] [ka]

[0576] slice_deblocking_filter_disabled_flag equal to 1 specifies that the operation of a deblocking filter is not applied to the current slice. slice_deblocking_filter_disabled_flag equal to 0 specifies that the operation of a deblocking filter is applied to the current slice.

[0577] If slice_deblocking_filter_disabled_flag is not present, the following is inferred:

[0578] [ka]

[0579] 6.5. Fifth embodiment Changes in bold italics are based on JVET-P2001-vE.

[0580] [Table 40] [Table 41]

[0581] 6.6. Sixth embodiment

[0582] 7.3.2.5 Adaptation Parameter Set RBSP Syntax

[0583] [Table 42]

[0584] [ka]

[0585] 7.3.2.19 Adaptive Loop Filter Data Syntax

[0586] [Table 43]

[0587] 7.3.2.20 Luminance Mapping with Saturation Scaling (LMCS)

[0588] [Table 44]

[0589] 7.3.2.21 Scaling List Data Syntax

[0590] [Table 45] [Table 46]

[0591] Then the PH semantics is modified as follows: …

[0592] ph_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luminance component of the slice associated with PH.

[0593] The value of alf_luma_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i]. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the picture associated with the PH.

[0594] [ka]

[0595] ph_lmcs_aps_id specifies the adaptation_parameter_set_id of the LMCSAPS referenced by the slice associated with the PH. The TemporalId of an APSNAL unit whose aps_params_type is equal to LMCS_APS and whose adaptation_parameter_set_id is ph_lmcs_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0596] [ka]

[0597] ph_scaling_list_aps_id specifies the adaptation_parameter_set_id of the scaling list APS. The TemporalId of an APSNAL unit whose aps_params_type is equal to SCALING_APS and whose adaptation_parameter_set_id is ph_scaling_list_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0598] [ka]

[0599] Then the PH semantics is modified as follows: slice_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS to which the luma component of the slice refers. The TemporalId of an APS NAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_luma[i] is not present, the value of slice_alf_aps_id_luma[i] is inferred to be equal to the value of ph_alf_aps_id_luma[i]. The value of alf_luma_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_alf_aps_id_luma[i].

[0600] [ka]

[0601] Then the ALF data semantics is modified as follows: ..

[0602] alf_luma_filter_signal_flag equal to 1 indicates that the luma filter set is signaled. alf_luma_filter_signal_flag equal to 0 indicates that the luma filter set is not signaled.

[0603] [ka]

[0604] [ka]

[0605] [ka]

[0606] Then the SCALING data semantics is modified as follows: … [scaling_list_chroma_present_flag equal to 1 specifies that the chroma scaling list is present in scaling_list_data(). scaling_list_chroma_present_flag equal to 0 specifies that the chroma scaling list is not present in scaling_list_data(). scaling_list_chroma_present_flag shall be equal to 0 if ChromaArrayType is equal to 0, and shall be equal to 1 if ChromaArrayType is not equal to 0.]] is a bitstream conformance requirement. …

[0607] 6.7. Seventh embodiment

[0608] 7.3.2.6 Adaptation Parameter Set RBSP Syntax

[0609] [Table 47]

[0610] [ka]

[0611] 7.3.2.19 Adaptive Loop Filter Data Syntax

[0612] [Table 48]

[0613] 7.3.2.20 Luminance Mapping with Saturation Scaling (LMCS)

[0614] [Table 49]

[0615] 7.3.2.21 Scaling List Data Syntax

[0616] [Table 50] [Table 51]

[0617] [ka]

[0618] Then the PH semantics is modified as follows: … ph_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luminance component of the slice associated with PH.

[0619] The value of alf_luma_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i]. The TemporalId of an APS NAL unit with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to ph_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the picture associated with the PH.

[0620] [ka]

[0621] ph_lmcs_aps_id specifies the adaptation_parameter_set_id of the LMCS APS referenced by the slice associated with the PH. The TemporalId of an APS NAL unit whose aps_params_type is equal to LMCS_APS and whose adaptation_parameter_set_id is ph_lmcs_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0622] [ka]

[0623] ph_scaling_list_aps_id specifies the adaptation_parameter_set_id of the scaling list APS. The TemporalId of an APS NAL unit whose aps_params_type is equal to SCALING_APS and whose adaptation_parameter_set_id is ph_scaling_list_aps_id shall be less than or equal to the TemporalId of the picture associated with the PH.

[0624] [ka]

[0625] Then the PH semantics is modified as follows: slice_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS referenced by the luma component of the slice. The TemporalId of an AP SAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the coded slice NAL unit. If slice_alf_enabled_flag is equal to 1 and slice_alf_aps_id_luma[i] is not present, the value of slice_alf_aps_id_luma[i] is inferred to be equal to the value of ph_alf_aps_id_luma[i].

[0626] The value of alf_luma_filter_signal_flag of an APSNAL unit whose aps_params_type is equal to ALF_APS and whose adaptation_parameter_set_id is equal to slice_alf_aps_id_luma[i] shall be equal to 1.

[0627] [ka]

[0628] Then the ALF data semantics is modified as follows: .. alf_luma_filter_signal_flag equal to 1 indicates that the luma filter set is signaled. alf_luma_filter_signal_flag equal to 0 indicates that the luma filter set is not signaled.

[0629] [ka]

[0630] [ka]

[0631] [ka]

[0632] Then the SCALING data semantics is modified as follows: … [scaling_list_chroma_present_flag equal to 1 specifies that the chroma scaling list is present in scaling_list_data(). scaling_list_chroma_present_flag equal to 0 specifies that the chroma scaling list is not present in scaling_list_data(). scaling_list_chroma_present_flag shall be equal to 0 if ChromaArrayType is equal to 0, and shall be equal to 1 if ChromaArrayType is not equal to 0.]] is a bitstream conformance requirement. …

[0633] 6.8. Eighth embodiment

[0634] 7.3.2.5 Adaptation Parameter Set RBSP Syntax

[0635] [Table 52]

[0636] 7.3.2.7 Picture Header Structure Syntax

[0637] [Table 53] [Table 54]

[0638] 7.3.7.1 General Slice Segment Header Syntax

[0639] [Table 55] [Table 56]

[0640] 7.4.3.5 Adaptation Parameter Set Semantics Each APS RBSP shall be available to the decoding process before it is referenced, contained within at least one AU with a TemporalId less than or equal to the TemporalId of the coded slice NAL unit that references it, or provided through external means.

[0641] All APS NAL units with a particular value of adaptation_parameter_set_id and with a particular value of aps_params_type within a PU shall have the same content, regardless of whether they are prefix or suffix APS NAL units. The adaptation_parameter_set_id provides an identifier for the APS to which other syntax elements refer.

[0642] [ka]

[0643] If aps_params_type is equal to LMCS_APS, the value of adaptation_parameter_set_id shall be in the range of 0 to 3. Let apsLayerId be the value of nuh_layer_id of a particular APS NAL unit, and vclLayerId be the value of nuh_layer_id of a particular VCL NAL unit. A particular VCL NAL unit shall not reference a particular APS NAL unit unless apsLayerId is less than or equal to vclLayerId and the layer with nuh_layer_id equal to apsLayerId is included in at least one OLS that contains a layer with nuh_layer_id equal to vclLayerId.

[0644] aps_params_type specifies the type of APS parameters implemented in the APS, as shown in Table 6. …

[0645] [ka]

[0646] All APS NAL units with a particular value of aps_params_type share the same value space for adaptation_parameter_set_id, regardless of the value of nuh_layer_id. APS NAL units with different values ​​of aps_params_type use distinct value spaces for adaptation_parameter_set_id.

[0647] 7.4.3.7 Picture Header Structure Semantics

[0648] [ka]

[0649] 7.4.8.1 General slice header semantics

[0650] [ka]

[0651] [ka]

[0652] [ka]

[0653] [ka]

[0654] The value of alf_cc_cb_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cb_aps_id.

[0655] [ka]

[0656] The value of alf_cc_cr_filter_signal_flag shall be equal to 1 for APS NAL units with aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf_cr_aps_id.

[0657] 6.9. Ninth embodiment

[0658] 7.3.2.5 Adaptation Parameter Set RBSP Syntax

[0659] [Table 57]

[0660] 6.10. Tenth embodiment

[0661] [Table 58]

[0662] 6.11. Eleventh embodiment In one example, the PH syntax table is modified as follows:

[0663] [Table 59] [Table 60]

[0664] And the semantics changes to: …

[0665] [ka]

[0666] [ka]

[0667] ph_disable_bdof_flag equal to 1 specifies that bidirectional optical flow inter-prediction based inter bidirectional prediction is disabled in the slice associated with the PH. ph_disable_bdof_flag equal to 0 specifies that bidirectional optical flow inter-prediction based inter bidirectional prediction may or may not be enabled in the slice associated with the PH.

[0668] If ph_disable_bdof_flag is not present, the following applies:

[0669] [ka]

[0670] ph_disable_dmvr_flag equal to 1 specifies that decoder motion vector refinement-based inter bidirectional prediction is disabled in the slice associated with PH. ph_disable_dmvr_flag equal to 0 specifies that decoder motion vector refinement-based inter bidirectional prediction may or may not be enabled in the slice associated with PH.

[0671] [ka]

[0672] Then the syntax table pred_weight_table() is modified as follows:

[0673] [Table 61]

[0674] And the meaning of num_l1_weights is changed as follows: num_l1_weights specifies the number of weights signaled for entries in reference picture list 1 when pps_weighted_bipred_flag and wp_info_in_ph_flag are both equal to 1. The value of num_l1_weight shall be in the range 0 to Min(15,num_ref_entries[1][RplsIdx[1]]).

[0675] The variable NumWeightsL1 is derived as follows:

[0676] [ka]

[0677] 6.12. Twelfth embodiment In one example, the PH syntax table is modified as follows:

[0678] [Table 62] [Table 63]

[0679] And the semantics changes to: …

[0680] [ka]

[0681] [ka]

[0682] ph_disable_bdof_flag equal to 1 specifies that bidirectional optical flow inter-prediction based inter bidirectional prediction is disabled in the slice associated with the PH. ph_disable_bdof_flag equal to 0 specifies that bidirectional optical flow inter-prediction based inter bidirectional prediction may or may not be enabled in the slice associated with the PH.

[0683] If ph_disable_bdof_flag is not present, the following applies:

[0684] [ka]

[0685] ph_disable_dmvr_flag equal to 1 specifies that decoder motion vector refinement-based inter bidirectional prediction is disabled in the slice associated with PH. ph_disable_dmvr_flag equal to 0 specifies that decoder motion vector refinement-based inter bidirectional prediction may or may not be enabled in the slice associated with PH.

[0686] If ph_disable_dmvr_flag is not present, the following applies:

[0687] [ka]

[0688] Then the syntax table pred_weight_table() is modified as follows:

[0689] [Table 64]

[0690] And the meaning of num_l1_weights is changed as follows: num_l1_weights specifies the number of weights signaled for entries in reference picture list 1 when pps_weighted_bipred_flag and wp_info_in_ph_flag are both equal to 1. The value of num_l1_weight shall be in the range 0 to Min(15,num_ref_entries[1][RplsIdx[1]]).

[0691] The variable NumWeightsL1 is derived as follows:

[0692] [ka]

[0693] 6.13. Thirteenth Embodiment To address the above issues, we propose the following changes, with the additions highlighted in bold italics:

[0694] [Table 65]

[0695] [ka]

[0696] [ka]

[0697] 1 is a block diagram illustrating an example video processing system 1900 in which various techniques disclosed herein may be implemented. Various implementations may include some or all of the modules of system 1900. System 1900 may include an input 1902 for receiving video content. The video content may be received in a raw or uncompressed format, e.g., 8- or 10-bit multi-component pixel values, or in a compressed or encoded format. Input 1902 may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interfaces include wired interfaces such as Ethernet, passive optical networks (PONs), and wireless interfaces such as Wi-Fi or cellular interfaces.

[0698] System 1900 may include a coding component 1904 capable of implementing various coding or encoding methods described herein. Coding component 1904 may reduce the average bit rate of video from input 1902 to the output of coding component 1904, generating a coded representation of the video. Thus, this coding technique may be referred to as a video compression or video transcoding technique. The output of coding component 1904 may be stored or transmitted via a connected communication, as represented by component 1906. The bitstream (or coded) representation of the video received at input 1902, stored, or communicated, may be used by component 1908 to generate pixel values ​​or displayable video that are transmitted to display interface 1910. The process of generating user-viewable video from the bitstream representation is sometimes referred to as video unpacking. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be understood that the coding tools or operations are performed by an encoder and corresponding decoding tools or operations that reverse the results of the coding are performed by a decoder.

[0699] Examples of peripheral bus interfaces or display interfaces may include Universal Serial Bus (USB) or High-Definition Multimedia Interface (HDMI), or DisplayPort, etc. Examples of storage interfaces include Serial Advanced Technology Attachment (SATA), PCI, IDE interfaces, etc. The techniques described herein may be implemented in various electronic devices such as mobile phones, laptops, smartphones, or other devices capable of digital data processing and / or video display.

[0700] 2 is a block diagram of a video processing device 3600. The device 3600 may be used to implement one or more of the methods described herein. The device 3600 may be implemented in a smartphone, tablet, computer, Internet of Things (IoT) receiver, etc. The device 3600 may include one or more processing units 3602, one or more memories 3604, and video processing hardware 3606. The one or more processors 3602 may be configured to implement one or more of the methods described herein. The memory(s) 3604 may be used to store data and code used to implement the methods and techniques described herein. The video processing hardware 3606 may be used to implement the techniques described herein in a hardware circuit.

[0701] FIG. 4 is a block diagram illustrating an example video coding system 100 that may utilize techniques of this disclosure.

[0702] 4, video coding system 100 may include source device 110 and destination device 120. Source device 110 generates coded video data, which may also be referred to as a video encoding device. Destination device 120 may decode the coded video data generated by source device 110 and may be referred to as a video decoding device.

[0703] Source device 110 may include a video source 112, a video encoder 114, and an input / output (I / O) interface .

[0704] The video source 112 may include a source such as a video capture device, an interface for receiving video data from a video content provider, and / or a computer graphics system for generating video data, or a combination of these sources. The video data may include one or more pictures. The video encoder 114 encodes the video data from the video source 112 and generates a bitstream. The bitstream may include a sequence of bits forming a coded representation of the video data. The bitstream may include coded pictures and associated data. A coded picture is a coded representation of a picture. The associated data may include sequence parameter sets, picture parameter sets, and other syntax structures. The I / O interface 116 may include a modulator / demodulator (modem) and / or transmitter. The coded video data may be transmitted directly to the destination device 120 via the I / O interface 116 over the network 130a. The coded video data may be stored on a recording medium / server 130b for access by the destination device 120.

[0705] Destination device 120 may include an I / O interface 126 , a video decoder 124 , and a display device 122 .

[0706] I / O interface 126 may include a receiver and / or a modem. I / O interface 126 may obtain encoded video data from source device 110 or storage medium / server 130b. Video decoder 124 may decode the encoded video data. Display device 122 may display the decoded video data to a user. Display device 122 may be integrated with destination device 120 or may be external to destination device 120 configured to interface with an external display device.

[0707] Video encoder 114 and video decoder 124 may operate according to video compression standards such as the High Efficiency Video Coding (HEVC) standard, the Versatile Video Coding (VVC) standard, and other current and / or future standards.

[0708] FIG. 5 is a block diagram illustrating an example of a video encoder 200, which may be the video encoder 114 in the system 100 shown in FIG.

[0709] Video encoder 200 may be configured to perform any or all of the techniques of this disclosure. In the embodiment of FIG. 5, video encoder 200 includes multiple functional modules. Techniques described in this disclosure may be shared among various modules of video encoder 200. In some examples, a processing unit may be configured to perform any or all of the techniques described in this disclosure.

[0710] The functional modules of the video encoder 200 may include a division unit 201, a prediction unit 202, which may include a mode selection unit 203, a motion estimation unit 204, a motion compensation unit 205, and an intra prediction unit 206, a residual generation unit 207, a transformation unit 208, a quantization unit 209, an inverse quantization unit 210, an inverse transform unit 211, a reconstruction unit 212, a buffer 213, and an entropy coding unit 214.

[0711] In other examples, video encoder 200 may include more, fewer, or different functional components. In one example, prediction unit 202 may include an intra block copy (IBC) unit. The IBC unit can perform prediction in an IBC mode in which at least one reference picture is the picture in which the current video block is located.

[0712] Furthermore, some modules, such as the motion estimation unit 204 and the motion compensation unit 205, may be highly integrated, but are represented separately in the example of FIG. 5 for illustrative purposes.

[0713] Division unit 201 may divide a picture into one or more video blocks. Video encoder 200 and video decoder 300 may support a variety of video block sizes.

[0714] The mode selection unit 203 may, for example, select one of intra or inter coding modes based on the error result, provide the resulting intra- or inter-coded block to the residual generation unit 207, generate and provide residual block data to the reconstruction unit 212, and reconstruct the coded block for use as a reference picture. In some examples, the mode selection unit 203 may select a Combination of Intra and Inter Prediction (CIIP) mode that performs prediction based on an inter prediction signal and an intra prediction signal. In the case of inter prediction, the mode selection unit 203 may select a resolution of motion vectors (e.g., sub-pixel or integer pixel accuracy) for the block.

[0715] To perform inter prediction on the current video block, motion estimation unit 204 may generate motion information for the current video block by comparing the current video block with one or more reference frames from buffer 213. Motion compensation unit 205 may determine a prediction video block for the current video block based on the motion information and decoded samples of pictures from buffer 213 other than the picture associated with the current video block.

[0716] Motion estimation unit 204 and motion compensation unit 205 may, for example, perform different operations on the current video block depending on whether the current video block is an I-slice, a P-slice, or a B-slice.

[0717] In some examples, motion estimation unit 204 may perform unidirectional prediction on the current video block, and motion estimation unit 204 may search reference pictures in list 0 or list 1 for a reference video block for the current video block. Motion estimation unit 204 may then generate a reference index indicating the reference picture in list 0 or list 1, including the reference video block and a motion vector indicating a spatial displacement between the current video block and the reference video block. Motion estimation unit 204 may output the reference index, prediction direction indicator, and motion vector as motion information for the current video block. Motion compensation unit 205 may generate a prediction video block for the current block based on the reference video block indicated by the motion information of the current video block.

[0718] In another example, motion estimation unit 204 may bidirectionally predict the current video block, and motion estimation unit 204 may search for a reference video block for the current video block from among the reference pictures in list 0, and may also search for another reference video block for the current video block from among the reference pictures in list 1. Motion estimation unit 204 may then generate reference indexes indicating the reference pictures in lists 0 and 1 that contain the reference video blocks, and motion vectors indicating spatial displacements between the reference video blocks and the current video block. Motion estimation unit 204 may output the reference index and motion vector for the current video block as motion information for the current video block. Motion compensation unit 205 may generate a prediction video block for the current video block based on the reference video block indicated by the motion information of the current video block.

[0719] In some examples, the motion estimation unit 204 may output a full set of motion information for decoding processing in a decoder.

[0720] In some examples, motion estimation unit 204 may not output a full set of motion information for the current picture. Rather, motion estimation unit 204 may signal motion information for the current video block by reference to motion information of another video block. For example, motion estimation unit 204 may determine that the motion information of the current video block is sufficiently similar to the motion information of a neighboring video block.

[0721] In one example, motion estimation unit 204 may indicate, in a syntax structure associated with the current video block, a value that indicates to video decoder 300 that the current video block has the same motion information as another video block.

[0722] In another example, motion estimation unit 204 may identify another video block and a motion vector difference (MVD) in a syntax structure associated with the current video block. The motion vector difference indicates a difference between the motion vector of the current video block and the motion vector of the indicated video block. Video decoder 300 may use the motion vector of the indicated video block and the motion vector difference to determine the motion vector of the current video block.

[0723] As mentioned above, video encoder 200 may predictively signal motion vectors. Two examples of predictive signaling techniques that may be implemented by video encoder 200 include advanced motion vector prediction (AMVP) and merge mode signaling.

[0724] Intra prediction unit 206 may perform intra prediction on the current video block. If intra prediction unit 206 intra predicts the current video block, intra prediction unit 206 may generate predictive data for the current video block based on decoded samples of other video blocks in the same picture. The predictive data for the current video block may include a predicted video block and various syntax elements.

[0725] Residual generator 207 may generate residual data for the current video block by subtracting (e.g., as indicated by a minus sign) the predicted video block of the current video block from the current video block. The residual data for the current video block may include residual video blocks that correspond to different sample components of the samples in the current video block.

[0726] In other examples, for example in skip mode, there may be no residual data for the current video block, and residual generator 207 may not perform the subtraction operation.

[0727] Transform processor 208 may generate one or more transform coefficient video blocks for the current video block by applying one or more transforms to the residual video block associated with the current video block.

[0728] After the transform processor 208 generates the transform coefficient video block associated with the current video block, the quantization unit 209 may quantize the transform coefficient video block associated with the current video block based on one or more quantization parameter (QP) values ​​associated with the current video block.

[0729] Inverse quantization unit 210 and inverse transform unit 211 may apply inverse quantization and inverse transform, respectively, to the transform coefficient video block to reconstruct a residual video block from the transform coefficient video block. Reconstruction unit 212 may add the reconstructed residual video block to corresponding samples from one or more prediction video blocks generated by prediction unit 202 to generate a reconstructed video block associated with the current block for storage in buffer 213.

[0730] After reconstructor 212 reconstructs the video block, a loop filtering operation may be performed to reduce video blocking artifacts in the video block.

[0731] Entropy encoding unit 214 may receive data from other functional components of video encoder 200. Once entropy encoding unit 214 receives the data, entropy encoding unit 214 may perform one or more entropy encoding operations to generate entropy-coded data and output a bitstream including the entropy-coded data.

[0732] FIG. 6 is a block diagram illustrating an example of a video decoder 300, which may be the video decoder 114 in the system 100 shown in FIG.

[0733] Video decoder 300 may be configured to perform any or all of the techniques of this disclosure. In the embodiment of FIG. 6, video decoder 300 includes multiple functional modules. Techniques described in this disclosure may be shared among various modules of video decoder 300. In some examples, a processing device may be configured to perform any or all of the techniques described in this disclosure.

[0734] 6 embodiment, video decoder 300 includes entropy decoding unit 301, motion compensation unit 302, intra prediction unit 303, inverse quantization unit 304, inverse transform unit 305, and reconstruction unit 306, as well as buffer 307. Video decoder 300 may, in some examples, perform a decoding path that is approximately the reverse of the encoding path described with respect to video encoder 200 (FIG. 5).

[0735] The entropy decoding unit 301 retrieves an encoded bitstream. The encoded bitstream may include entropy-coded video data (e.g., encoded blocks of video data). The entropy decoding unit 301 decodes the entropy-coded video data, and from the entropy-decoded video data, the motion compensation unit 302 may determine motion information including motion vectors, motion vector precision, reference picture list indexes, and other motion information. The motion compensation unit 302 may determine such information by, for example, implementing AMVP and merge mode.

[0736] The motion compensation unit 302 may generate motion-compensated blocks, possibly performing interpolation based on an interpolation filter. The syntax element may include an identifier for the interpolation filter to be used with sub-pixel precision.

[0737] Motion compensation unit 302 may calculate interpolated values ​​for sub-integer pixels of the reference block using interpolation filters such as those used by video encoder 200 during encoding of the video block. Motion compensation unit 302 may determine the interpolation filters used by video encoder 200 based on received syntax information and use the interpolation filters to generate the prediction block.

[0738] The motion compensation unit 302 may use syntax information to determine the size of the blocks used to code the frames and / or slices of the coded video sequence, partitioning information describing how each macroblock of a picture of the coded video sequence is divided, a mode indicating how each division is coded, one or more reference frames (and reference frame lists) for each inter-coded block, and some other information to decode the coded video sequence.

[0739] The intra prediction unit 303 may form a prediction block from spatially adjacent blocks, for example, using an intra prediction mode received in the bitstream. The inverse quantization unit 303 inverse quantizes (i.e., dequantizes) the quantized video block coefficients provided in the bitstream and decoded by the entropy decoding unit 301. The inverse transform unit 303 applies an inverse transform.

[0740] The reconstruction unit 306 may sum the residual block with the corresponding prediction block generated by the motion compensation unit 202 or the intra prediction unit 303 to form a decoded block. If desired, a deblocking filter may be applied to filter the decoded block to remove block artifacts. The decoded video block is stored in a buffer 307, which provides reference blocks for subsequent motion compensation / intra prediction and generates decoded video for display on a display device.

[0741] Next, preferred examples in some embodiments will be listed.

[0742] The following items illustrate exemplary embodiments of the techniques described in the previous section: The following items illustrate exemplary embodiments of the techniques described in the previous section (e.g., item 1).

[0743] 1. A video processing method (e.g., method 3000 shown in FIG. 3 ), comprising: converting (3002) video having one or more chroma components, the video including one or more video pictures each including one or more slices, to a coded representation of the video, the coded representation conforming to a format rule, the format rule specifying that a chroma array type field controls constraints on chroma transformation characteristics used during the conversion.

[0744] 2. The method according to item 1, wherein the conversion characteristics include a constraint on a field indicating the presence of one or more scaling lists for the one or more chroma components.

[0745] 3. The method of item 1, wherein the conversion characteristics include constraints on values ​​of a field indicating a code name used to signal luminance mapping with chroma scaling.

[0746] 4. The method of claim 1, wherein the transformation characteristics include constraints on values ​​of syntax elements that describe adaptation parameters for an adaptive loop filter set used during the transformation.

[0747] 5. The method described in item 1, wherein the formatting rules specify that the saturation array type field signaling a 4:0:0 format or a separate color coding format uses the same semantics as entries in one or more adaptation parameter sets.

[0748] 6. The method of item 5, wherein the one or more entries include a luminance mapping using an adaptive loop filter parameter, or a scaling list parameter, or a chroma scaling parameter.

[0749] 7. The method according to items 5 to 6, wherein the formatting rules further specify that the constraints on the one or more entries of the adaptation parameter set depend on whether an identifier of the adaptation parameter set is included in the bitstream.

[0750] The following items present exemplary embodiments of the techniques described in the previous section (eg, item 2).

[0751] 8. A video processing method comprising: converting between video comprising one or more video pictures comprising one or more video regions and a coded representation of said video, said coded representation conforming to format rules specifying that said coded representation includes a deblocking mode indicator for a video region indicating that a deblocking filter can be applied to said video region during said conversion.

[0752] 9. The method of claim 8, wherein the deblocking mode indicator is an N-bit field, where N is an integer greater than 1.

[0753] 10. The method according to any one of items 8 to 9, wherein the deblocking mode indicator of the video region is included in a picture parameter set.

[0754] 11. The method of claim 8, wherein the deblocking mode indicator corresponds to a flag included in a header of the video region that indicates that the deblocking filter is applicable to the video region.

[0755] 12. The method according to any of items 8 to 11, wherein the formatting rules define a flag that signals whether deblocking filter parameters signaled in the deblocking mode indicator override default parameters.

[0756] 13. The method according to any one of items 8 to 12, wherein the video region corresponds to a video picture or a video slice.

[0757] The following items present exemplary embodiments of the techniques described in the previous section (eg, item 3).

[0758] 14. A video processing method comprising converting one or more video pictures comprising one or more video slices and / or one or more video sub-pictures to and from a coded representation of said video, said coded representation conforming to a format rule specifying a flag indicating whether single slice per sub-picture mode is considered valid for a video picture when picture splitting is disabled for said video picture.

[0759] The following items present exemplary embodiments of the techniques described in the previous section (eg, item 4).

[0760] 15. A video processing method comprising converting between video comprising one or more video pictures comprising one or more video slices and a coded representation of said video, said coded representation conforming to a format rule specifying signaling of a picture or slice level chroma quantization parameter offset in a picture header or slice header.

[0761] 16. The method of claim 15, wherein the format rules specify that a slice-level chroma quantization parameter offset is to be included in the slice header.

[0762] The following items present exemplary embodiments of the techniques described in the previous section (eg, item 5).

[0763] 17. A method of processing video, comprising transforming between video including one or more video pictures including one or more video slices and a coded representation of the video, wherein the coded representation complies with format rules that specify that a chroma quantization parameter (QP) table applicable to transforming video blocks of the video is derived as an XOR operation between (delta_qp_in_val_minus1[i][j]+1) and delta_qp_diff_val[i][j], where delta_qp_in_val_minus1[i][j] specifies a delta value used to derive the input coordinate of the jth pivot point of the ith chroma mapping table, and delta_qp_diff_val[i][j] specifies a delta value used to derive the output coordinate of the jth pivot point of the ith chroma QP mapping table, and i and j are integers.

[0764] 18. The method according to any one of items 1 to 17, wherein the conversion comprises encoding the video into the coded representation.

[0765] 19. A method according to any one of items 1 to 17, wherein the conversion comprises decoding the coded representation to generate pixel values ​​of the image.

[0766] 20. A video decoding device comprising a processor configured to implement the method according to one or more of items 1 to 19.

[0767] 21. A video encoding device comprising a processor configured to implement the methods described in one or more of items 1 to 19.

[0768] 22. A computer program product having computer code stored therein, the code being executed by a processor, causing the processor to implement the method according to any one of items 1 to 19.

[0769] 23. A method, apparatus or system as described herein.

[0770] The second section presents exemplary embodiments of the techniques discussed in the previous section. The following items present exemplary embodiments of the techniques described in the previous chapter (e.g., item 31).

[0771] 1. A video processing method (e.g., method 700 of FIG. 7), comprising converting between video including one or more video pictures and a coded representation of the video, wherein the coded representation conforms to a format rule, wherein the format rule specifies that a first syntax element (SE) indicating whether motion vector difference (MVD) is signaled for a reference picture list (RPL) is conditionally included in the coded representation based on a number of reference pictures in the RPL, if the RPL information is present in the picture header, and a second SE indicating whether reference picture list information is signaled in a picture header.

[0772] 2. The method described in item 1, wherein the first SE is a flag indicating whether to disable motion vector differences in the coded representation.

[0773] 3. The method according to any one of items 1 to 2, wherein the second SE corresponds to a flag indicating whether the RPL information is included in the picture header.

[0774] The following items present exemplary embodiments of the techniques described in the previous section (eg, item 32).

[0775] 4. A video processing method comprising: converting between video including one or more video pictures and a coded representation of the video, wherein the coded representation conforms to a format rule, and the format rule specifies that a first syntax element (SE) indicating whether to disable a decoder motion vector refinement (DMVR) tool is conditionally included in the coded representation based on whether reference picture list (RPL) information is signaled in a picture header (PH), whether the second SE is included in the coded representation, the number of reference pictures of a previous RPL if the RPL information is present in the picture header (PH), and / or whether a flag indicating applicability of the DMVR tool included at a sequence parameter set level in the coded representation is equal to 1.

[0776] 5. The method of item 4, wherein the first SE corresponds to a flag indicating whether the DMVR tool is disabled at the picture header level.

[0777] 6. A method according to any one of items 4 to 5, wherein the second SE corresponds to a flag indicating whether the RPL information is included at the picture header level.

[0778] The following items present exemplary embodiments of the techniques described in the previous section (e.g., item 33).

[0779] 7. A video processing method comprising: converting between video including one or more video pictures and a coded representation of the video, wherein the coded representation conforms to a format rule, and the format rule specifies that a first syntax element (SE) indicating whether to disable a bidirectional optical flow (BDOF) tool is conditionally included in the coded representation based on whether reference picture list (RPL) information is signaled in a picture header (PH), whether the second SE is included in the coded representation, the number of reference pictures in RPL-1 if the RPL information is present in the picture header (PH), and / or a flag indicating applicability of the BDOF tool at a sequence parameter set level.

[0780] 8. The method according to item 7, wherein the first SE corresponds to a flag indicating applicability of the BDOF tool at the picture header level.

[0781] 9. The method according to any one of items 7 to 8, wherein the second SE corresponds to a flag indicating whether the RPL information is included at the picture header level.

[0782] The following items present exemplary embodiments of the techniques described in the previous section (e.g., item 34).

[0783] 10. A video processing method comprising: converting between video including one or more video pictures and a coded representation of the video, wherein the coded representation conforms to a format rule, the format rule specifying that a first syntax element (SE) indicating whether the co-located picture used for temporal motion vector prediction is derived from reference picture list 0 is conditionally included based on a second SE indicating whether reference picture list information is signaled in a picture header, the number of reference pictures in RPL-1 if the RPL information is present in the picture header, and whether temporal motion vector prediction (TMVP) tools are enabled for the current picture.

[0784] 11. The method of item 10, wherein the first SE corresponds to a flag indicating whether the co-located picture used for temporal motion vector prediction is derived from the first reference picture list.

[0785] 12. A method according to any one of items 10 to 11, wherein the second SE corresponds to a flag indicating whether the RPL information is included at the picture header level.

[0786] The following items present exemplary embodiments of the techniques described in the previous section (eg, items 35-38).

[0787] 13. A video processing method comprising: converting between video comprising one or more video pictures and a coded representation of the video, the coded representation conforming to a format rule, the format rule specifying whether a first syntax element (SE) indicating a table of prediction weights is included in the coded representation conditionally based on a second SE indicating whether weighted prediction (WP) information is signaled in a picture header (PH), whether reference picture list (RPL) information is signaled in the PH, the number of reference pictures in RPL-1 if the RPL information is present in the PH, and whether a flag indicating applicability of weighted prediction and / or weighted bidirectional prediction is included in a picture parameter set.

[0788] 14. The method of claim 13, wherein the formatting rules further specify that the first SE is signaled when a condition is true.

[0789] 15. A video processing method comprising: converting between video including one or more video pictures and a coded representation of said video, said coded representation conforming to format rules, said format rules specifying that whether intra slices are allowed to be used to represent a video picture in the coded representation depends on whether inter slices are allowed for said picture and whether there are multiple partitions.

[0790] 16. The method according to any one of items 1 to 15, wherein the formatting rules further specify that the adaptation parameter set is coded using syntax elements less than 5 bits wide.

[0791] 17. A method according to any one of items 1 to 16, wherein the formatting rules specify the coding or decoding order of a general constraint flag syntax structure included in the coded representation such that flags in the general constraint flag syntax structure are included in groups.

[0792] 18. The method according to any one of items 1 to 17, wherein the conversion comprises encoding the video into the coded representation.

[0793] 19. A method according to any one of items 1 to 17, wherein the conversion comprises decoding the coded representation to generate pixel values ​​of the image.

[0794] 20. A video decoding device comprising a processor configured to implement the method according to one or more of items 1 to 19.

[0795] 21. A video encoding device comprising a processor configured to implement the methods described in one or more of items 1 to 19.

[0796] 22. A computer program product having computer code stored therein, the code being executed by a processor, causing the processor to implement the method according to any one of items 1 to 19.

[0797] 23. A method, apparatus or system as described herein.

[0798] The third section presents exemplary embodiments of the techniques described in the previous chapter (eg, items 30-34, 37, and 38).

[0799] 1. A video processing method (e.g., method 800 shown in FIG. 8A), comprising: performing 802 a conversion between video including one or more pictures and a bitstream of the video in accordance with a format rule, the format rule specifying that a first syntax element indicating whether motion vector differences for a particular reference picture list (RPL) are indicated is conditionally included in the bitstream based on (i) a second syntax element indicating whether RPL information is included in the picture header, and / or (ii) the number of reference pictures for the particular RPL if RPL information is present in the picture header.

[0800] 2. The method according to item 1, wherein the first syntax element is a flag indicating whether a motion vector coding syntax structure of the particular RPL corresponding to reference picture list 1 is parsed or not parsed.

[0801] 3. The method according to item 1 or 2, wherein the second syntax element corresponds to a flag indicating whether the picture header includes the RPL information.

[0802] 4. A method according to any one of items 1 to 3, wherein the number of reference pictures in the particular RPL is set equal to the value of a variable indicating the number of entries in the RPL syntax structure for the particular RPL corresponding to reference picture list 1.

[0803] 5. The method according to any of items 1 to 4, wherein the formatting rules specify that whether to include the first syntax element depends on whether a condition if(!pps_rpl_info_in_ph_flag||num_ref_entries[1][RplsIdx[1]]>0) is satisfied, where pps_rpl_info_in_ph_flag is the second syntax element and num_ref_entries[1] is the number of reference pictures of the particular RPL for reference list 1.

[0804] 6. The method described in item 5, wherein the first syntax element is ph_mvd_l1_zero_flag.

[0805] 7. The method of item 5, wherein the formatting rules specify that the first syntax element i...

Claims

1. 1. A method for processing a video, comprising: converting a video, the video including one or more pictures, to a bitstream of the video according to a format rule, the method comprising: the format rule specifies that the first syntax element indicating whether a motion vector differential coding syntax structure for a particular reference picture list (RPL) is parsed is included in the bitstream when (i) a value of a second syntax element indicates that the motion vector differential coding syntax structure for a particular reference picture list (RPL) is not present in reference picture list (RPL) information in a picture header, or (ii) a value of a third syntax element indicates that a number of reference pictures in a particular RPL is greater than 0 if the RPL information is present in the picture header, and the value of the second syntax element indicates that the RPL information is present in the picture header, and the value of the third syntax element indicates that the number of reference pictures in the particular RPL is equal to 0; the formatting rules further specify that if the first syntax element is not included in the bitstream, then a value of the first syntax element is presumed to be equal to one; a value of the first syntax element equal to one specifies that the motion vector difference coding syntax structure for the particular RPL is not parsed. Video data processing method.

2. The particular RPL corresponds to reference picture list 1. The method of claim 1.

3. The format rule further specifies that a fourth syntax element indicating a number of weights signaled for an entry of the particular RPL is conditionally included in a weight prediction parameter syntax structure indicating a weight prediction parameter table of the bitstream based on: (iii) a fifth syntax element is included in a picture parameter set and indicates applicability of explicit weighted prediction (WP) for B slices that reference the picture parameter set; (iv) a sixth syntax element indicates whether WP information is included in the picture header; and (v) a value of the third syntax element indicates the number of the reference pictures in the particular RPL. The method of claim 1.

4. The formatting rules are: (1) the fifth syntax element has a first value specifying application of the explicit WP to the B slice referencing the picture parameter set, the first value being equal to 1; (2) the sixth syntax element has a second value specifying possible presence of WP information in the picture header and absence of the WP information in a slice header referencing the picture parameter set not included in the picture header, the second value being equal to 1; and (3) a value of the third syntax element indicating the number of reference pictures in the particular RPL is greater than 0. The method according to claim 3.

5. The formatting rules are: (1) the fifth syntax element has a first value specifying that the explicit WP is applied to the B slice that references the picture parameter set; (2) the sixth syntax element has a second value specifying the presence of WP information in the picture header and the absence of WP information in a slice header that references the picture parameter set that is not included in the picture header; and (3) the value of the third syntax element indicating the number of reference pictures in the specific RPL is greater than 0. The method according to claim 3.

6. The formatting rules specify that the value of a first variable NumWeightsL1 corresponding to the weight of the particular RPL is derived as follows: if(!pps_weighted_bipred_flag | | (pps_wp_info_in_ph_flag && num_ref_entries[1][RplsIdx[1]]==0)) NumWeightsL1=0 else if(pps_wp_info_in_ph_flag) NumWeightsL1=num_l1_weights else NumWeightsL1=NumRefIdxActive[1], pps_weighted_bipred_flag is the fifth syntax element, pps_wp_info_in_ph_flag is the sixth syntax element, num_ref_entries[1][RplsIdx[1]] is the third syntax element, num_l1_weights is the fourth syntax element, NumRefIdxActive[1] is a second variable indicating the number of active reference pictures in reference picture list 1 that are allowed to be used to code at least one slice; The method according to claim 3.

7. the formatting rules specify which general constraint syntax elements are to be grouped together in a general constraint information syntax structure that indicates one or more constraints to which the transformation applies; General constraint syntax elements in a particular group are signaled together without combination with general constraint syntax elements in other groups; The method of claim 1.

8. the formatting rules specify that interrelated syntax elements are grouped together; The interrelated syntax elements specify general constraint syntax elements for characteristics including at least one of reference picture resampling, resolution change in a video sequence of a coded layer, weighted prediction, reference wraparound, temporal motion vector prediction, sub-block based temporal motion vector prediction, adaptive motion vector prediction, bi-directional optical flow, symmetric motion vector difference, decoder side motion vector derivation, merge-based motion vector difference, affine motion prediction, prediction refinement with optical flow, bi-prediction with CU (coding unit) weights, hybrid inter-intra prediction (CIIP), or geometric prediction mode. The method of claim 7.

9. the formatting rules specify that interrelated syntax elements are grouped together; The interrelated syntax elements specify general constraint syntax elements for characteristics including at least one of a palette coding mode, an intra block copy mode, an intra sub-partition (ISP), a multi-reference line intra prediction, a matrix-based intra prediction, or a cross-component linear model. The method of claim 7.

10. the converting includes encoding the video into the bitstream. The method according to any one of claims 1 to 9.

11. the converting includes decoding the video from the bitstream. The method according to any one of claims 1 to 9.

12. 1. An apparatus for processing video data comprising a processor and a non-transitory memory having instructions thereon, When executed by the processor, the instructions cause the processor to: converting a video including one or more pictures to a bitstream of said video according to a format rule; The format rule specifies that the first syntax element indicating whether a motion vector differential coding syntax structure for a particular reference picture list (RPL) is parsed is included in the bitstream when (i) a value of a second syntax element indicates that the particular reference picture list (RPL) is not present in reference picture list (RPL) information in a picture header, or (ii) a value of a third syntax element indicates that a number of reference pictures in a particular RPL is greater than 0 if the RPL information is present in the picture header, and the value of the second syntax element indicates that the RPL information is present in the picture header, and the value of the third syntax element indicates that the number of reference pictures in the particular RPL is equal to 0, and the first syntax element indicates that the bitstream is excluded from the bitstream. the format rules further specify that if the first syntax element is not included in the bitstream, then a value of the first syntax element is presumed to be equal to one; a value of the first syntax element equal to one specifies that the motion vector difference coding syntax structure for the particular RPL is not parsed. Device.

13. A non-transitory computer-readable storage medium having stored thereon instructions that cause a processor to: converting a video including one or more pictures to a bitstream of said video according to a format rule; The format rule specifies that the first syntax element indicating whether a motion vector differential coding syntax structure for a particular reference picture list (RPL) is parsed is included in the bitstream when (i) a value of a second syntax element indicates that the particular reference picture list (RPL) is not present in reference picture list (RPL) information in a picture header, or (ii) a value of a third syntax element indicates that a number of reference pictures in a particular RPL is greater than 0 if the RPL information is present in the picture header, and the value of the second syntax element indicates that the RPL information is present in the picture header, and the value of the third syntax element indicates that the number of reference pictures in the particular RPL is equal to 0, and the first syntax element indicates that the bitstream is excluded from the bitstream. the format rules further specify that if the first syntax element is not included in the bitstream, then a value of the first syntax element is presumed to be equal to one; a value of the first syntax element equal to one specifies that the motion vector difference coding syntax structure for the particular RPL is not parsed. A non-transitory computer-readable storage medium.

14. 1. A method for storing a video bitstream, comprising the steps of: converting said video, said video including one or more pictures, to a bitstream of said video according to a format rule; storing the bitstream on a non-transitory computer readable recording medium; The format rule specifies that the first syntax element indicating whether a motion vector differential coding syntax structure for a particular reference picture list (RPL) is parsed is included in the bitstream when (i) a value of a second syntax element indicates that the particular reference picture list (RPL) is not present in reference picture list (RPL) information in a picture header, or (ii) a value of a third syntax element indicates that a number of reference pictures in a particular RPL is greater than 0 if the RPL information is present in the picture header, and the value of the second syntax element indicates that the RPL information is present in the picture header, and the value of the third syntax element indicates that the number of reference pictures in the particular RPL is equal to 0, and the first syntax element indicates that the bitstream is excluded from the bitstream. the format rules further specify that if the first syntax element is not included in the bitstream, then a value of the first syntax element is presumed to be equal to one; the value of the first syntax element being equal to one specifies that the motion vector differential coding syntax structure for the particular RPL is not parsed. method.

Citation Information

Cited By

  • Presence of adaptation parameter set units

    US12356017B2

  • Conditional signaling of video coding syntax elements

    US12382103B2

  • Deblocking signaling in video coding

    US12413784B2