MÉTODO E APARELHO PARA PROCESSAR DADOS DE VÍDEO, E, MEIOS DE ARMAZENAMENTO E DE GRAVAÇÃO LEGÍVEIS POR COMPUTADOR NÃO TRANSITÓRIOS
By optimizing IBC and palette modes in video encoding and decoding, the challenges of handling reference blocks outside the reconstructed area are addressed, enhancing efficiency and reducing complexity in video processing.
Patent Information
- Application Number
- BR112022020449
- Authority / Receiving Office
- BR · BR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-04-10
- Filing Date
- 2021-04-12
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2041-04-12
AI Technical Summary
Existing video encoding and decoding technologies face challenges in efficiently handling intra-block copy (IBC) and palette modes, particularly for screen content, due to issues like reference blocks being outside the reconstructed area or overlapping, leading to inefficiencies and complexity in bitstream conformance.
Implementing techniques such as IBC mode handling in VVC test model (VTM-4.0) and palette mode enhancements in HEVC-SCC, including improved merge candidate selection, palette predictor initialization, and adaptive filtering, to optimize video processing and reduce computational complexity.
Enhances video encoding and decoding efficiency by ensuring valid reference blocks and reducing redundancy, thereby improving the quality of decompressed video and reducing computational load.
Abstract
Description
123 METHOD AND APPARATUS FOR PROCESSING VIDEO DATA, AND NON-TRANSIENT COMPUTER-READABLE STORAGE AND RECORDING MEDIA Cross-reference to related orders
[001] This application is based on International Patent Application No. PCT / CN2021 / 086522, filed on April 12, 2021, which claims priority and the benefits of International Patent Application No. PCT / CN2020 / 084291, filed on April 10, 2020. All patent applications cited above are incorporated herein by reference in their entirety. Technical Field
[002] This document relates to video and image encoding and / or decoding technologies. Fundamentals of the Invention
[003] Digital video accounts for the largest use of bandwidth on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, the demand for bandwidth for digital video use is expected to continue to grow. Summary
[004] The techniques described can be used by video or image decoder or encoder modes for which reference figures are used in video encoding and / or decoding.
[005] In one example aspect, a video processing method is described. The method includes analyzing, for a conversion between a video region of a video and an encoded and / or decoded representation of the video region, the encoded and / or Petition 870220099113, dated 10 / 26 / 2022, page 7 / 14 / 123 decoded from the video region, the encoded and / or decoded representation according to a syntax rule that defines a relationship between a chroma block size and a color format of the video region and perform the conversion by performing the analysis according to the syntax rule.
[006] In another example aspect, another video processing method is described. The method involves determining, based on a property of a video and a chroma format of the video, an encoding and / or decoding mode of a node in the video encoding and / or decoding tree and performing a conversion between an encoded and / or decoded representation of the video and a video block of the encoding and / or decoding tree node using the determined encoding and / or decoding mode.
[007] In yet another example aspect, another video processing method is described. The method involves determining, based on a rule, whether a certain size of chroma blocks is allowed in a video region of a video and performing a conversion between the video region and an encoded and / or decoded representation of the video region based on the determination.
[008] In yet another example aspect, another video processing method is described. The method involves determining, based on a rule that allows the use of an encoding and / or decoding mode for a video condition, that an encoding and / or decoding mode is allowed for a video region and performing a conversion between an encoded and / or decoded representation of pixels in the video region and pixels of the video region based on the determination.
[009] In yet another example aspect, another video processing method is described. The method involves performing a conversion between a video block of a video and an encoded and / or decoded representation of the video block using an encoding and / or Petition 870220099106, dated 10 / 26 / 2022, page 8 / 161 / 123 video decoding, in which a syntax element that signals the encoding and / or decoding mode is selectively included in the encoded and / or decoded representation based on a rule.
[0010] In yet another example aspect, another video processing method is described. The method involves determining, due to a chroma block having a size smaller than a threshold size, that a type of transform used during a conversion between the chroma block and an encoded and / or decoded representation of the chroma block is different from a type of transform used for a corresponding conversion of the luma block, and performing the conversion based on that determination.
[0011] In yet another example aspect, another video processing method is described. The method includes determining whether a smallest chroma block rule is applied during a conversion between an encoded and / or decoded representation of a video region and pixel values of the video region, based on an encoding and / or decoding condition of the video region; and performing the conversion based on the determination.
[0012] In yet another example aspect, another video processing method is described. The method includes determining, for a conversion between an encoded and / or decoded representation of a video region in a 4:2:2 format and pixel values of the video region, a mode type to be used for the conversion based on whether a smallest block chroma rule is activated for the video region; and performing the conversion based on the determination.
[0013] In yet another example aspect, another video processing method is described. The method includes determining, for a conversion between an encoded and / or decoded representation of a video block and a video block of a video, whether block partitioning is allowed during the conversion, based on a type of mode used during Petition 870220099106, dated 10 / 26 / 2022, page 9 / 161 / 123 the conversion or a dimension of the video block; and perform the conversion using the determination.
[0014] In yet another example aspect, another video processing method is described. The method involves determining, for a conversion between an encoded and / or decoded representation of a video segment and the video segment, applying a special processing mode to a chroma block of size MxN, where M by N are integers; and performing the conversion based on the determination.
[0015] In another example aspect, another video processing method is described. The method involves performing a conversion between a video that includes a video region and a continuous bitstream of the video according to a rule; and wherein the rule specifies a relationship between activation of a palette mode and a type of encoding and / or decoding of the video region.
[0016] In another example aspect, another video processing method is described. The method involves performing a conversion between a video that includes a first video region and a second video region and a continuous bitstream of the video according to a rule; and wherein the rule specifies that a filtering strength (bs) of an unlock filter for chroma components of the video is set to 0 in the case where a first block is in an intra-block copy mode and a second block is in a palette mode.
[0017] In another example aspect, another video processing method is described. The method involves performing a conversion between a video and a continuous bitstream of the video according to a format rule, and where the format rule specifies that a variable related to an input bit intensity of the video is limited according to a profile of the continuous bitstream.
[0018] In another example aspect, another method of Petition 870220099106, dated 10 / 26 / 2022, page 10 / 161 / 123, describes video processing. The method involves performing a conversion between a video and a continuous bitstream of the video according to a format rule, wherein the format rule specifies that a variable indicating the minimum allowed quantization parameter is limited according to a profile of the continuous bitstream.
[0019] In yet another example aspect, the above-described method can be implemented by a video encoding device comprising a processor.
[0020] In yet another example aspect, the above-described method can be implemented by a video decoder device comprising a processor.
[0021] In yet another example, these methods can be incorporated in the form of processor-executable instructions and stored in a computer-readable program medium.
[0022] These, and other, aspects are further described in this document. Brief Description of the Drawings
[0023] Figure 1 shows an example of an intra-block copy encoding and / or decoding tool.
[0024] Figure 2 shows an example of a block encoded and / or decoded in palette mode.
[0025] Figure 3 shows an example of using a palette predictor to signal palette entries.
[0026] Figure 4 shows an example of horizontal and vertical cross-sectional scans.
[0027] Figure 5 shows examples of encoding and / or decoding palette indices.
[0028] Figure 6 shows an example of 67 intraprediction modes.
[0029] Figure 7 shows examples of neighbors to the left and above. Petition 870220099106, dated 10 / 26 / 2022, page 11 / 161 / 123 of the current block.
[0030] Figure 8 shows examples of ALF filter shapes (chroma: 5x5 rhombus, luma: 7x7 rhombus).
[0031] Figure 9 shows an example of a subsampled Laplacian calculation.
[0032] Figure 10 shows an example of a modified block classification in virtual boundaries.
[0033] Figure 11 is an example illustration of modified ALF filtering for the Luma component on virtual contours.
[0034] Figure 12 shows examples of four 3-pixel 1D patterns for pixel classification in EO.
[0035] Figure 13 shows that four bands are grouped and represented by their initial band position.
[0036] Figure 14 shows adjacent top and left blocks used in CIIP weight derivation.
[0037] Figure 15 shows the luma mapping architecture with chroma scaling.
[0038] Figure 16 shows examples of SCIPU.
[0039] Figures 17A and 17B show block diagrams of examples of a hardware platform used to implement techniques described in this document.
[0040] Figure 18 is a flowchart for an example video processing method.
[0041] Figure 19 shows examples of spatial merging candidate positions.
[0042] Figure 20 shows examples of candidate pairs considered for spatial merge candidate redundancy verification.
[0043] Figure 21 is a block diagram that illustrates an example of a video encoding and / or decoding system. Petition 870220099106, dated 10 / 26 / 2022, page 12 / 161 / 123
[0044] Figure 22 is a block diagram illustrating an encoder according to some embodiments of the technology described.
[0045] Figure 23 is a block diagram illustrating a decoder according to some embodiments of the technology described.
[0046] Figures 24A to 24D are flowcharts for example video processing methods according to some embodiments of the technology described. Detailed Description
[0047] This document provides several techniques that can be used by a continuous bitstream image or video decoder to improve the quality of decompressed or decoded digital video or images. For brevity, the term “video” is used here to include both a sequence of figures (traditionally called a video) and individual images. Furthermore, a video encoder can also implement these techniques during the encoding process in order to reconstruct decoded frames used for further encoding.
[0048] Section headings are used in this document for ease of understanding and do not limit the modalities and techniques to the corresponding sections. As such, the modalities of one section may be combined with the modalities of other sections. 1. Brief Summary
[0049] This document relates to video encoding and / or decoding technologies. Specifically, it relates to palette encoding and / or decoding using color-based representation in video encoding and / or decoding. It may apply to existing video encoding and / or decoding standards such as HEVC, or to future standards (Versatile Video Encoding and / or Decoding) to be finalized. It may also apply to future video encoding and / or decoding standards or codecs. Petition 870220099106, dated 10 / 26 / 2022, page 13 / 161 / 123 video. 2. Initial Discussion
[0050] Video encoding and / or decoding standards have evolved primarily through the development of the well-known ITU-T and ISO / IEC standards. ITU-T produced H.261 and H.263, ISO / IEC produced MPEG-1 and MPEG-4 Visual, and the two organizations jointly produced the H.262 / MPEG-2 Video and H.264 / MPEG-4 Advanced Video Coding and / or Decoding (AVC) and H.265 / HEVC standards. Since H.262, video encoding and / or decoding standards have been based on a hybrid video encoding and / or decoding framework in which time prediction plus transformed encoding and / or decoding are used. To explore future video encoding and / or decoding technologies beyond HEVC, the Joint Video Exploration Team (JVET) was founded by VCEG and MPEG jointly in 2015. Since then, many novel methods have been adopted by JVET and incorporated into the reference software named the Joint Exploration Model (JEM).In April 2018, the Joint Video Expert Team (JVET) between VCEG (Q6 / 16) and ISO / IEC JTC1 SC29 / WG11 (MPEG) was created to work on the VVC standard, aiming for a 50% reduction in bitrate compared to HEVC.
[0051] The most recent version of the VVC draft, namely Versatile Video Encoding and / or Decoding (Draft 4), can be found at: http: / / phenix.itsudparis.eu / jvet / doc_end_user / current_document.php?id=5755
[0052] The latest VVC reference software, named VTM, can be verified at: https: / / vcgit.hhi.fraunhofer.de / jvet / VVCSoftware_VTM / tags / VTM-5.0 2.1 Copying Intra Blocks Petition 870220099106, dated 10 / 26 / 2022, p. 14 / 161 / 123
[0053] Intra-block copy (IBC), also known as current-figure reference, was adopted in HEVC - Screen Content Encoding and / or Decoding Extensions (HEVC-SCC) and the current VVC test model (VTM-4.0). IBC extends the concept of motion compensation from inter-frame encoding and / or decoding to intra-frame encoding and / or decoding. As demonstrated in Figure 1, the current block is predicted by a reference block in the same figure when IBC is applied. The samples in the reference block must have already been reconstructed before the current block is encoded and / or decoded. Although IBC is not as efficient for most camera-captured sequences, it shows significant encoding and / or decoding gains for screen content. The reason is that there are many repeating patterns, such as icons and text characters, in a screen content figure.IBC can effectively remove redundancy between these repetition patterns. In HEVC-SCC, an intercoded and / or decoded encoding and / or decoding unit (CU) can apply IBC if it chooses the current figure as its reference figure. The MV is renamed as a block vector (BV) in this case, and a BV always has full pixel precision. To be compatible with the HEVC main profile, the current figure is marked as a “long-term” reference figure in the Decoded Figure Temporary Storage (DPB). It should be noted that, similarly, in multiview / 3D video encoding and / or decoding standards, the interview reference figure is also marked as a “long-term” reference figure.
[0054] Following a BV to check its reference block, the prediction can be generated by copying the reference block. The residual can be obtained by subtracting the reference pixels from the original signals. Then, transform and quantization can be applied as in other encoding and / or decoding modes. Petition 870220099106, dated 10 / 26 / 2022, page 15 / 161 / 123
[0055] Figure 1 is an illustration of intra block copying.
[0056] However, when a reference block is outside the figure, or overlaps with the current block, or is outside the reconstructed area, or is outside the valid area restricted by some constraints, some or all of the pixel values are undefined. Basically, there are two solutions to handle a problem like this. One is to disallow such a situation, for example, in continuous bitstream conformance. The other is to apply padding to those undefined pixel values. The following subsections describe the solutions in detail. 2.2 IBC in HEVC - Screen Content Encoding and / or Decoding Extensions
[0057] In HEVC Screen Content Encoding and / or Decoding extensions, when a block uses the current image as a reference, it must ensure that the entire reference block is within the available reconstructed area, as indicated in the following specification text: The variables offsetX and offsetY are derived as follows: offsetX = (ChromaArrayType = = 0) ? 0 : (mvCLX[0] & 0x7 ? 2 : 0) (8-104) offsetY = (ChromaArrayType = = 0) ? 0 : (mvCLX[1] & 0x7 ? : 0) (8-105) It is a requirement of continuous bitstream conformance that, when the reference figure is the current figure, the movement vector of luma mvLX must obey the following constraints: - When the derivation process for block availability of the z-scan order, as specified in clause 6.4.1, is invoked with (xCurr, yCurr) set equal to (xCb, yCB) and the neighboring luma location (xNbY, yNbY) set equal to (xPb + (mvLX[0] >> 2) offsetX, yPb + (mvLX[1] >> 2) - offsetY) as inputs, the output should be Petition 870220099106, dated 10 / 26 / 2022, page 16 / 161 / 123 equal to TRUE. - When the derivation process for block availability of scan order z, as specified in clause 6.4.1, is invoked with (xCurr, yCurr) set equal to (xCb, yCB) and the neighboring luma location (xNbY, yNbY) set equal to (xPb + (mvLX[0] >> 2) + nPbW - 1 + offsetX, yPb + (mvLX[1] >> 2) + nPbH - 1 + offsetY) as inputs, the output must be equal to TRUE.
[0058] - One or both of the following conditions must be true: - The value of (mvLX[0] >> 2) + nPbW + xB1 + offsetX is less than or equal to 0.
[0059] - The value of (mvLX[1] >> 2) + nPbH + yB1 + offsetY is less than or equal to 0.
[0060] - The following condition must be true: (xPb + (mvLX[0] >> 2) + nPbSw - 1 + offsetX) / CtBSizeY xCb / CtbSizeY <= yCb / CtbSizeY - (yPb + (mvLX[1] >> 2) + nPbSh - 1 + offsetY) / CtbSizeY (8-106) Therefore, the case where the reference block overlaps with the current block or the reference block is outside the figure will not occur. There is no need to fill the reference or prediction block. 2.3 IBC in VVC Test Model
[0061] In the current VVC test model, i.e., project VTM-4.0, the entire reference block must be with the current encoding and / or decoding unit tree (CTU) and not overlap with the current block. Thus, there is no need to fill the reference or forecast block. The IBC indicator is encoded and / or decoded as a forecast mode of the current CU. Thus, there are, in total, three forecast modes, MODE_INTRA, MODE_INTER and MODE_IBC for each CU. 2.3.1 IBC Mixing Mode Petition 870220099106, dated 10 / 26 / 2022, page 17 / 161 / 123
[0062] In IBC merge mode, an index pointing to an entry in the IBC merge candidate list is parsed from the continuous bit stream. The construction of the IBC merge list can be summarized according to the following sequence of steps: * Step 1: Derivation of spatial candidates * Step 2: Insertion of HMVP candidates * Step 3: Insertion of pairwise average candidates
[0063] In the derivation of spatial merge candidates, a maximum of four merge candidates are selected from the candidates located at the positions shown in Figure 19. The derivation order is A1, B1, B0, A0, and B2. Position B2 is considered only when no PU from position A1, B1, B0, A0 is available (for example, because it belongs to another slice or grid) or is not encoded and / or decoded using IBC mode. After the candidate at position A1 is added, the insertion of the remaining candidates is subject to a redundancy check that ensures that candidates with the same movement information are excluded from the list so that encoding and / or decoding efficiency is improved. To reduce computational complexity, not all possible candidate pairs are considered in the aforementioned redundancy check.Instead, only pairs linked with an arrow in Figure 20 are considered, and a candidate is only added to the list if the corresponding candidate used for redundancy checking does not have the same movement information.
[0064] After the insertion of spatial candidates, if the size of the IBC merge list is still less than the maximum size of the IBC merge list, IBC candidates from the HMVP table may be inserted. Redundancy checks are performed during the insertion of HMVP candidates.
[0065] Finally, the pairwise average candidates are entered into Petition 870220099106, dated 10 / 26 / 2022, p. 18 / 161 / 123 IBC merge list.
[0066] When a reference block identified by a merge candidate is outside the figure, or overlaps with the current block, or is outside the reconstructed area, or is outside the valid area restricted by some constraints, the merge candidate is called an invalid merge candidate.
[0067] It is understood that invalid merge candidates may be included in the IBC merge list. 2.3.2 AMVP IBC Mode
[0068] In IBC AMVP mode, an AMVP index pointing to an entry in the IBC AMVP list is parsed from the continuous bit stream. The construction of the IBC AMVP list can be summarized according to the following sequence of steps: * Step 1: Derivation of spatial candidates * Check A0, A1 until an available candidate is found. * Check B0, B1, B2 until an available candidate is found. * Step 2: Insertion of HMVP candidates * Step 3: Insertion of zero candidates
[0069] After the insertion of spatial candidates, if the size of the IBC AMVP list is still less than the maximum size of the IBC AMVP list, IBC candidates from the HMVP table may be inserted.
[0070] Finally, zero candidates are entered into the IBC AMVP list. 2.4 Palette Mode
[0071] The basic idea behind a palette mode is that the samples in the CU are represented by a small set of representative color values. This set is referred to as the palette. It is also possible to indicate a sample that is outside the palette by signaling an escape symbol followed by component values (possibly quantized). This Petition 870220099106, dated 10 / 26 / 2022, page 19 / 161 / 123, the sample type is called an escape sample. The palette mode is illustrated in Figure 2.
[0072] Figure 2 shows an example of a block encoded and / or decoded in palette mode. 2.5 Palette Mode in HEVC - Screen Content Encoding and / or Decoding Extensions (HEVC-SCC)
[0073] In palette mode in HEVC-SCC, a predictive method is used to encode the palette and index map. 2.5.1 Encoding and / or Decoding Palette Inputs
[0074] For encoding and / or decoding palette entries, a palette predictor is maintained. The maximum palette size, as well as the palette predictor, is signaled in the SPS. In HEVC-SCC, a palette_predictor_initializer_present_flag is introduced in the PPS. When this flag is 1, entries for palette predictor initialization are signaled in the continuous bit stream. The palette predictor is initialized at the beginning of each CTU row, each slice, and each grid. Depending on the value of the palette_predictor_initializer_present_flag, the palette predictor is reset to 0 or initialized using the palette predictor initializer entries signaled in the PPS. In HEVC-SCC, a palette predictor initializer of size 0 has been enabled to allow explicit disabling of palette predictor initialization at the PPS level.
[0075] For each entry in the palette predictor, a reuse indicator is signaled to indicate whether it is part of the current palette. This is illustrated in Figure 3. The reuse indicators are sent using zero-runlength encoding and / or decoding. After this, the number of new palette entries is signaled using zero-order exponential Golomb code. Finally, the component values for the new palette entries are signaled.
[0076] Figure 3 shows an example of using the palette predictor. Petition 870220099106, dated 10 / 26 / 2022, page 20 / 161 / 123 to signal palette entries. 2.5.2 Encoding and / or Decoding of Palette Indexes
[0077] Palette indices are encoded and / or decoded using horizontal and vertical transverse scans, as shown in Figure 4. The scan order is explicitly signaled in the continuous bit stream using the palette_transpose_flag. For the rest of the subsection, horizontal scanning is assumed.
[0078] Figure 4 shows examples of horizontal and vertical cross-sectional scans.
[0079] Palette indices are encoded and / or decoded using two main palette sample modes: 'INDEX' and 'COPY_ABOVE'. As explained previously, the escape symbol is also signaled as an 'INDEX' mode and assigned an index equal to the maximum palette size. The mode is signaled using an indicator, except for the top row or when the previous mode was 'COPY_ABOVE'. In 'COPY_ABOVE' mode, the palette index of the sample in the row above is copied. In 'INDEX' mode, the palette index is explicitly signaled. For both 'INDEX' and 'COPY_ABOVE' modes, a run value is signaled specifying the number of subsequent samples that are also encoded and / or decoded using the same mode. When the escape symbol is part of the run in 'INDEX' or 'COPY_ABOVE' mode, the escape component values are signaled for each escape symbol. The encoding and / or decoding of palette indices is illustrated in Figure 5.
[0080] This syntax order is achieved as follows. First, the number of index values for the CU is signaled. This is followed by signaling the actual index values for the entire CU using truncated binary encoding and / or decoding. Both the number of indices and the index values are encoded and / or decoded in mode Petition 870220099106, dated 10 / 26 / 2022, page 21 / 161 / 123 of bypass. This groups the bypass bins related to the index. Then, the palette sample mode (if necessary) and execution are signaled in an interleaved manner. Finally, the component escape values corresponding to the escape samples for the entire CU are grouped and encoded and / or decoded in bypass mode.
[0081] An additional syntax element, last_run_type_flag, is flagged after the index values are flagged. This syntax element, together with the index number, eliminates the need to flag the run value corresponding to the last execution in the block.
[0082] In HEVC-SCC, palette mode is also enabled for 4:2:2, 4:2:0, and monochrome chroma formats. The signaling of palette entries and palette indices is nearly identical for all chroma formats. In the case of non-monochrome formats, each palette entry consists of 3 components. For the monochrome format, each palette entry consists of a single component. For subsampled chroma directions, chroma samples are associated with luma sample indices that are divisible by 2. After reconstructing the palette indices for the CU, if a sample has only a single component associated with it, only the first component of the palette entry is used. The only difference in signaling is for the escape component values. For each escape sample, the number of signaled escape component values may be different, depending on the number of components associated with this sample.
[0083] In VVC, the dual encoding and / or decoding tree structure is used in the encoding and / or decoding of intra slices, therefore, the Luma component and two chroma components can have different palettes and palette indices. Furthermore, the two chroma components share the same palette and palette indices.
[0084] Figure 5 shows examples of encoding and / or decoding. Petition 870220099106, dated 10 / 26 / 2022, page 22 / 161 / 123 of the palette indexes. 2.6 Intra Mode of Encoding and / or Decoding in VVC
[0085] To capture the arbitrary edge directions presented in natural video, the number of intradirectional modes in VTM5 is extended from 33, as used in HEVC, to 65. The new non-HEVC directional modes are represented as red dashed arrows in Figure 6, and the planar and DC modes remain the same. These denser directional intraprediction modes apply to all block sizes and to both luma and chroma intraprediction.
[0086] In VTM5, several conventional angular intraprediction modes are adaptively replaced with wide-angle intraprediction modes for non-square blocks.
[0087] In HEVC, each intracoded and / or decoded block has a square shape, and the length of each of its sides is a power of 2. Thus, no division operation is required to generate an intrapredictor using DC mode. In VTM5, blocks can have a rectangular shape, which necessitates the use of a block division operation in the general case. To avoid division operations for DC forecasting, only the longest side is used to compute the average for non-square blocks.
[0088] Figure 6 shows an example of 67 intraprediction modes.
[0089] To keep the complexity of generating the most probable mode (MPM) list low, an intra-mode encoding and / or decoding method with 6 MPMs is used by considering two available neighboring intra-modes. The following three aspects are considered to construct the MPM list: - Standard intra-modes - Intra-neighbor modes - Intra-derived modes
[0090] A unified 6-MPM list is used for intra blocks, Petition 870220099106, dated 10 / 26 / 2022, page 23 / 161 / 123 regardless of whether MRL and ISP encoding and / or decoding tools are applied or not. The MPM list is constructed based on intra-block modes to the left and above. Assuming the left block mode is denoted as Left and the above block mode is denoted as Above, the unified MPM list is constructed as follows (the left and above blocks are shown in Figure 7): Figure 7 is an example of the neighbors to the left and above of current block.
[0091] - When a neighboring block is unavailable, its mode Intra is set to Plan by default.
[0092] Angular: - If both Left and Up modes are not * MPM list ^ {Plane, DC, V, H, V-4, V+4} - If one of the Left and Up modes is an angular mode, and the another non-angular for loop: * Set a Max mode as the largest mode in Left and Above * MPM list ^ {Plane, Max, DC, Max -1, Max +1, Max - 2} - If both Left and Above are angular and the even if they are different: * Adjust a Max mode as the largest mode in Left and Above * if the difference between Left and Above modes is within the range of 62, inclusive * MPM List -> {Plane, Left, Above, DC, Max -1, Max +1} * In other circumstances * MPM List -> {Plane, Left, Above, DC, Max -2, Max Petition 870220099106, dated 10 / 26 / 2022, page 24 / 161 / 123 +2} If both "Left" and "Above" are angular and equal in length: * MPM List -> {Plane, Left, Left -1, Left +1, DC, Left -2}
[0093] Furthermore, the first bin of the mpm index codeword is encoded and / or decoded in CABAC context. In total, three contexts are used, corresponding to whether the current intra block is activated in MRL, activated in ISP, or a normal intra block.
[0094] During the process of generating the 6 MPM list, pruning is used to remove duplicate modes, so that only unique modes can be included in the MPM list. For entropy encoding and / or decoding of the 61 non-MPM modes, a Truncated Binary Code (TBC) is used.
[0095] For chroma intra-mode encoding and / or decoding, a total of 8 intra modes are allowed for chroma intra-mode encoding and / or decoding. These modes include five traditional intra modes and three cross-component linear model modes (CCLM, LM_A, and LM_L). The chroma mode signaling and derivation processes are shown in Table 2. Chroma mode encoding and / or decoding is directly dependent on the intra prediction mode of the corresponding luma block. Since the separate block partitioning structure for luma and chroma components is activated in I-slices, a chroma block can correspond to multiple luma blocks. Therefore, for DM Chroma mode, the intra prediction mode of the corresponding luma block that covers the central position of the current chroma block is directly inherited. Table 2-4 - Derivation of chroma prediction mode from luma mode while cclm_is enabled__________________________________ Chroma prediction mode Corresponding intraprediction luma mode 0 50 18 1 X ( 0 <= X <= 66 ) 0 66 0 0 0 0 Petition 870220099106, dated 10 / 26 / 2022, page 25 / 161 20 / 123 1 50 66 50 50 50 2 18 18 66 18 18 3 1 1 1 66 1 4 81 81 81 81 81 5 82 82 82 82 82 6 83 83 83 83 83 7 0 50 18 1 2.7 Quantized Residual Block Differential Pulse Code Modulation (QR-BDPCM)
[0096] In JVET-M0413, a quantized residual block differential pulse code modulation (QR-BDPCM) is proposed to efficiently encode screen contents.
[0097] The prediction directions used in QR-BDPCM can be vertical and horizontal prediction modes. Intraprediction is performed on the entire block by copying the sample in the prediction direction (horizontal or vertical prediction) similar to intraprediction. The residual is quantized and the delta between the quantized residual and its quantized predictor value (horizontal or vertical) is encoded and / or decoded. This can be described as follows: For a block of size M (rows) x N (columns), consider Tj p 0 < í < M — 1, 0 < ;' < AZ — 1 as the prediction residual after performing intraprediction horizontally (copying the left neighbor pixel value across the predicted block row by row) or vertically (copying the top neighbor row for each row in the predicted block) using unfiltered samples from the block contour samples above or to the left.Consider that 0 < i < M — 1, 0 < / < AZ — 1 denotes the quantized version of the residual r^·, where the residual is the difference between the values of the original block and the predicted block. Then, the block DPCM is applied to the quantized residual samples, resulting in a modified M x N array R with elements. When vertical BDPCM is signed: i=0.. 0 <j <(W- 1) < i < (M - 1), C < ; < (W - 1) (2-7-1) Petition 870220099106, dated 10 / 26 / 2022, page 26 / 161 / 123
[0098] For horizontal forecasting, similar rules apply, and the residual quantized samples are obtained by - = í0- ' -15··' =0(2 7 2)Tíl1)
[0099] Residual quantized samples are sent to the decoder.
[00100] On the decoder side, the calculations shown are reversed to produce 0 < í < M — 1, 0 <; < A — 1. For the vertical prediction case, <?(rw) = EUA / . 0<y<(N-l) (2-7-3)
[00101] For the horizontal case, = ΣΪ=0Λλ- o < ϊ < (μ - 1), 0 < j < (A - 1) (2-7-4)
[00102] The inverse quantized residuals, Q-11, are added to the intra-block prediction values to produce the reconstructed sample values.
[00103] The main benefit of this scheme is that the inverse DPCM can be done quickly during coefficient analysis by simply adding the predictor as the coefficients are analyzed, or the same can be done after the analysis. 2.8 Adaptive Loop Filter
[00104] In VTM5, an Adaptive Loop Filter (ALF) with block-based filter adaptation is applied. For the luma component, one of 25 filters is selected for each 4x4 block, based on the direction and activity of local gradients. 2.8.1.1 Filter Shape
[00105] In VTM5, two forms of the diamond filter (as shown in Figure 8) are used. The 7x7 diamond form is applied to the Luma component and the 5x5 diamond form is applied to the Petition 870220099106, dated 10 / 26 / 2022, page 27 / 161 22 / 123 chroma components.
[00106] Figure 8 shows examples of ALF filter shapes (chroma: 5x5 diamond, luma: 7x7 diamond) 2.8.1.2 Block Classification
[00107] For the Luma component, each 4x4 block is categorized into one of 25 classes. The classification index C is derived based on its directionality D and a quantized activity value A, as follows: C = 5D + Â (2-9-1)
[00108] To calculate D and A, gradients in the horizontal, vertical, and two diagonal directions are first calculated using the 1D Laplacian: =ςη 2 vkJ. = 12R(k. n - R(k.: - n - r (k.i+η i (2-9-2) , HfcI-12RU. 0 - RO - 1.0 - R(k +1.01 (2-1) to = ΣΚ-2 Σίζΐί Olw, Ol».< = |2RO, 0 - RO -1.1-1)RO I 1,1 I 1)1 (2-9-4) to = Z1S-2Σ£;-2 , D2t.t = 12RO.I) - RO - 1,1 + 1) fltTíHh 1,1- 1)| (2-9-5)
[00109] When the indices i and / refer to the coordinates of the upper left sample in the 4x4 block and R(i,j) indicates a sample reconstructed at the coordinate
[00110] To reduce the complexity of block classification, the 1D subsampled Laplacian calculation is applied. As shown in Figure 9, the same subsampled positions are used for gradient calculation in all directions.
[00111] Figure 9 shows an example of an undersampled Laplacian calculation. (a) undersampled positions for vertical gradient (b) undersampled positions for horizontal gradient (c) undersampled positions for diagonal gradient (d) undersampled positions for diagonal gradient. Petition 870220099106, dated 10 / 26 / 2022, page 28 / 161 23 / 123
[00112] Then, D maximum and minimum values of the gradients in the horizontal and vertical directions are adjusted as: = maxtg^gj, g^n= min(gkrgv) (2-9-6)
[00113] The maximum and minimum values of the gradient in two diagonal directions are adjusted as follows: βι = 0½ = (2-9-7)
[00114] To derive the value of the directionality £?, these values are compared with each other and with two limits G and t2: Step 1. If both g™x< t1-g^,nwhile ' tfSíi are true, D is defined as 0.
[00115] Step 2. If g^ / g^vn> SdoSi / S^di' continue from Step 3; otherwise, continue from Step 4.
[00116] Step 3. If g™ > t2· gff, D is defined as 2; otherwise, D is defined as 1.
[00117] Step 4. If g1^ > t3 g^nãl, D is defined as 4; otherwise, D is defined as 3.
[00118] The value of activity A is calculated as: A = Σ^Σ^.^ι + M (2-9-8)
[00119] A is additionally quantized in the range from 0 to 4 inclusive, and the quantized value is denoted as Â.
[00120] For the chroma components in a figure, no classification method is applied, that is, a single set of ALF coefficients is applied to each chroma component. 2.8.1.3 Geometric Transformations of Filter Coefficients and Bounding Values
[00121] Before filtering each 4x4 luma block, geometric transformations, such as rotation or diagonal and vertical inversion, are applied to the filter coefficients f(k, í) and the corresponding limiting values. Petition 870220099106, dated 10 / 26 / 2022, page 29 / 161 24 / 123 of filter c(krl), depending on gradient values calculated for this block. This is equivalent to applying these transformations to the samples in the filter's support region. The idea is to make different blocks to which ALF is applied more similar by aligning their directionality.
[00122] Three geometric transformations, including diagonal inversion, vertical inversion, and rotation, are introduced: Diagonal: fD(k, Z) = f(l, k), cD(k, 0 = c(l, k), (2-9-9) Vertical inversion: Λq= f(l{i K_ j _13,Cv(ki=c(kiκ-1-l) (2-9-10) Rotation: fRÇkrl) = f(Kll.k), cR(k,l) = cÇK-l - 1,k) (2-9-11) where K is the filter size and Q < k,l < K — 1 are coefficient coordinates, such that the location (0,0) is in the upper left corner and the location (K — 1, / í — 1J) is in the lower right corner. The transformations are applied to the filter coefficients f(k, Z) and the limiting values c(ííj), depending on gradient values calculated for this block. The relationship between the transformation and the four gradients of the four directions is summarized in the following table. Table 2-5 - Mapping of the calculated gradient for a block and the transformations________________________________________________________ Gradient values gd2 transformation <gdiegh<gv Nenhuma transformação gd2<gdiegv<gh Diagonal gdi < gd2 e gh < gv Inversão vertical gdi < gd2 e gv < gh Rotação 2.8.1.4 Signaling of Filter Parameters
[00123] In VTM5, ALF filter parameters are signaled in the Adaptation Parameter Set (APS). In an APS, up to 25 sets of luma filter coefficients and limiting value indices, and up to one set of chroma filter coefficients and limiting value indices can be signaled. To reduce bit overprocessing, filter coefficients of different classifications can be merged. In the slice header, the indices of the APSs used for the current slice are signaled. Petition 870220099106, dated 10 / 26 / 2022, page 30 / 161 25 / 123
[00124] Limiting value indices, which are decoded from the APS, allow determining limiting values using a Luma table of limiting values and a Chroma table of limiting values. These limiting values are dependent on the internal bit depth. More precisely, the Luma table of limiting values and the Chroma table of limiting values are obtained by the following formulas: AlfClipL= jroundJ parant [1.. A]j. (2-9-12) AlfClipc= ground^ff-3^+3jv-i parant [l..A]j (2-9-13) with B equals the internal bit depth and N equals 4, which is the number of limit values allowed in VTM5.0.
[00125] The filtering process can be controlled at the CTB level. An indicator is always displayed to show whether ALF is applied in a luma CTB. A luma CTB can choose a set of filters from 16 fixed filter sets and filter sets from the APSs. A filter set index is displayed to a luma CTB to indicate which filter set is applied. The 16 fixed filter sets are predefined and permanently encoded and / or decoded in both the encoder and the decoder.
[00126] The filter coefficients are quantized with a norm equal to 128. In order to restrict the complexity of the multiplication, a continuous bitstream conformity is applied so that the non-central position coefficient value must be in the range of -27 to 27-1, inclusive. The central position coefficient is not signed in the continuous bitstream and is considered to be equal to 128. 2.8.1.5 Filtration Process
[00127] On the decoder side, when ALF is activated for a CTB, each sample R(i, j) in the CU is filtered, resulting in the sample value. Petition 870220099106, dated 10 / 26 / 2022, page 31 / 161 26 / 123 of the form shown below, = i?[í, jj + ((Σλ^Σ^ο / 0<. i)xK(fí(i -i- kj + O (Zy- 14J where f(k, l) denotes the decoded filter coefficients, kXqyJ is the limiting function and c(7q / ) denotes the decoded limiting parameters. The variables k and l vary between — - and -, where L denotes the length of the filter. The limiting function K (x, y) = min (y, max(— which corresponds to the function function CUp3 (—ν,T, v)· 2.8.1.6 Virtual Contour Filtering Process for Reducing Temporary Line Storage
[00128] In VTM5, to reduce the requirement for temporary ALF line storage, modified block classification and filtering are employed for samples near horizontal CTU boundaries. For this purpose, a virtual boundary is defined as a line offset from the horizontal CTU boundary with “N” samples, as shown in Figure 10, with N equal to 4 for the Luma component and 2 for the Chroma component.
[00129] Figure 10 shows an example of a modified block classification in virtual boundaries.
[00130] The modified block classification is applied to the Luma component, as shown in Figure 11, the value of activity A is thus scaled by taking into account the reduced number of samples used in the 1D Laplacian gradient calculation.
[00131] For filtering processing, symmetrical filling of virtual boundaries is used for both luma and chroma components. As shown in Figure 11, when the sample being filtered is located below the virtual boundary, the neighboring samples located above the virtual boundary are filled. In this particular case, the corresponding samples on the other sides are also filled. Petition 870220099106, dated 10 / 26 / 2022, page 32 / 161 / 123 symmetrically.
[00132] Figure 11 shows examples of modified ALF filtering for the Luma component on virtual contours. 2.9 Adaptive Sample Shift (SAO)
[00133] Sample Adaptive Shifting (SAO) is applied to the reconstructed signal after the unblocking filter by using the offsets specified for each CTB by the encoder. The HM encoder first decides whether or not the SAO process should be applied to the current slice. If SAO is applied to the slice, each CTB is classified as one of five SAO types, as shown in Table 2. The concept of SAO is to classify pixels into categories and reduce distortion by adding an offset in pixels from each category. The SAO operation includes Edge Shifting (EO), which uses edge properties for pixel classification in SAO types 1-4, and Band Shifting (BO), which uses pixel intensity for pixel classification in SAO type 5. Each applicable CTB has SAO parameters that include sao_merge_left_flag, sao_merge_up_flag, SAO type, and four offsets.If sao_merge_left_flag is equal to 1, the current CTB will reuse the SAO type and offset the CTB to the left. If sao_merge_up_flag is equal to 1, the current CTB will reuse the SAO type and offset the CTB up. Table 2-6 - SAO Type Specification_________________________ SAO Type Sample Adaptive Offset Type to be Used Number of Categories 0 None 0 1 Standard 0-degree edge offset 1D 4 2 Standard 90-degree edge offset 1D 4 3 Standard 135-degree edge offset 1D 4 4 Standard 45-degree edge offset 1D 4 5 Band offset 4 2.9.1 Operation of Each Type of SAO
[00134] Edge offset uses four 3-pixel 1D patterns to Petition 870220099106, dated 10 / 26 / 2022, page 33 / 161 / 123 classification of the current pixel p by considering the directional information of the edge, as shown in figure 12. From left to right, they are: 0 degrees, 90 degrees, 135 degrees and 45 degrees.
[00135] Figure 12 shows examples of four 3-pixel 1D patterns for pixel classification in EO.
[00136] Each CTB is classified into one of five categories, according to Table 2-7. Table 2-7 - Pixel classification rule for EO__________________ Category Condition Meaning 0 None of the following Broadly monotonic 1 p < 2 neighbors Local minimum 2 p < 1 neighbor && p == 1 neighbor Edge 3 p > 1 neighbor && p == 1 neighbor Edge 4 p > 2 neighbors Local maximum
[00137] Bandshift (BSO) classifies all pixels in a CTB region into 32 uniform bands by using the five most significant bits of the pixel value as the band index. In other words, the pixel intensity range is divided into 32 equal segments, from zero to the maximum intensity value (e.g., 255 for 8-bit pixels). Four adjacent bands are grouped together, and each group is indicated by its leftmost position, as shown in Figure 13. The encoder searches every position to obtain the group with the maximum distortion reduction by compensating for the offset of each band.
[00138] Figure 13 shows an example of four bands that are grouped and represented by their initial band position. 2.10 Combined Inter- and Intra-Forecast (CIIP)
[00139] In VTM5, when a CU is encoded and / or decoded in blended mode, if the CU contains at least 64 luma samples (i.e., CU width times CU height equals or is greater than 64), and if both the CU width and CU height are less than 128 luma samples, an additional indicator is signaled to indicate whether the combined inter / intraprediction (CIIP) mode is applied to the current CU. As its name Petition 870220099106, dated 10 / 26 / 2022, p. 34 / 161 29 / 123 indicates that the CIIP forecast combines an interforecast signal with an intraforecast signal. The interforecast signal in CIIP mode is derived using the same interforecast process applied to regular blend mode; and the intraforecast signal is derived following the regular intraforecast process with the flat mode. Then, the intra- and interforecast signals are combined using weighted averaging, where the weight value is calculated depending on the encoding and / or decoding modes of the top and left neighboring blocks (represented in Figure 14), as follows: - If the top neighbor is available and is intra-encoded and / or decoded, then set isIntraTop to 1, otherwise set isIntraTop to 0; - If the left neighbor is available and is intra-encoded and / or decoded, then set isIntraLeft to 1; otherwise, set isIntraLeft to 0. - If (isIntraLeft + isIntraLeft) equals 2, then wt is defined as 3; Otherwise, if (isIntraLeft + isIntraLeft) equals 1, then wt is defined as 2; Otherwise, adjust wt by 1.
[00140] The CIIP forecast is formed as follows: few = ((4- wt) * + wt* Pintra+ 2) » 2 (3.2)
[00141] Figure 14 shows examples of top and left adjacent blocks used in CIIP weight derivation. 2.11 Luma Mapping with Chroma Scale (LMCS)
[00142] In VTM5, an encoding and / or decoding tool called luma mapping with chroma scaling (LMCS) is added as a new processing block before the loop filters. LMCS has two main components: 1) loop mapping of the Luma component based on adaptive piece-by-piece linear models; 2) for the Petition 870220099106, dated 10 / 26 / 2022, page 35 / 161 / 123 chroma components, luma-dependent chroma residual scale is applied. Figure 15 shows the LMCS architecture from the decoder's perspective. The dotted blocks in Figure 15 indicate where processing is applied in the mapped domain; these include inverse quantization, inverse transform, luma intraprediction, and addition of luma prediction along with the luma residual. The non-standardized blocks in Figure 15 indicate where processing is applied in the original (i.e., unmapped) domain; these include loop filters such as unblocking, ALF, and SAO, motion-compensated prediction, chroma intraprediction, addition of chroma prediction along with the chroma residual, and storage of decoded figures as reference figures.The checkerboard blocks in Figure 15 are the new LMCS functional blocks, including direct and inverse luma signal mapping and a luma-dependent chroma scaling process. Like most other tools in VVC, LMCS can be enabled / disabled at the sequence level using an SPS indicator.
[00143] Figure 15 shows examples of luma mapping architecture with chroma scaling. 2.12 Dual Tree Partitioning
[00144] In the current VVC project, for I slices, each CTU can be split into encoding and / or decoding units with 64x64 luma samples using an implicit split quad tree, and where these encoding and / or decoding units are the root of two separate coding_tree syntax structures for luma and chroma.
[00145] Since the dual tree in intrafigure allows for different partitioning in the chroma encoding and / or decoding tree, compared to the luma encoding and / or decoding tree, the dual tree introduces a longer encoding and / or decoding channel and the value range of QTBT MinQTSizeC and MinBtSizeY and MinTTSizeY in Petition 870220099106, dated 10 / 26 / 2022, page 36 / 161 / 123. Chroma trees allow for small chroma blocks, such as 2x2, 4x2, and 2x4. This presents difficulties in practical decoder design. Furthermore, various prediction modes, such as CCLM, planar, and angular modes, require multiplication. In order to alleviate the aforementioned problems, small chroma block sizes (2x2 / 2x4 / 4x2) are restricted in dual trees as a partitioning constraint. 2.13 Smallest Chroma Intraprediction Unit (SCIPU) in JVET-O0050
[00146] Small chroma size is not hardware-friendly. In dual-tree cases, chroma blocks with very small sizes are disallowed. However, in single-tree cases, the VVC 5 sketch still allows 2x2, 2x4, 4x2 chroma blocks. To restrict the chroma block size, in single-tree encoding and / or decoding, an SCIPU is defined in JVET-O0050 as a node in the encoding and / or decoding tree whose chroma block size is greater than or equal to TH chroma samples and has at least one child luma block smaller than 4TH luma samples, where TH is defined as 16 in this contribution. It is required that, in each SCIPU, all CBs be inter, or all CBs be non-inter, that is, either intra or IBC.In the case of a non-intermediate SCIPU, it is additionally required that the chroma of the non-intermediate SCIPU should not be further divided and that the luma of the SCIPU should be further divided. In this way, the smallest intra-chroma CB size is 16 chroma samples, and 2x2, 2x4, and 4x2 chroma CBs are removed. Furthermore, chroma scaling is not applied in the case of a non-intermediate SCIPU.
[00147] Two examples of SCIPU are shown in Figure 16. In Figure 16(a), a chroma CB of 8x4 chroma samples and three luma CBs (4x8, 8x8, 4x8 luma CBs) form an SCIPU because the ternary tree (TT) split from the 8x4 chroma samples results in chroma CBs smaller than 16 chroma samples. In Figure 16(b), a CB of Petition 870220099106, dated 10 / 26 / 2022, page 37 / 161 / 123 chroma of 4x4 chroma samples (the left side of the 8x4 chroma samples) and three luma CBs (8x4, 4x4, 4x4 luma CBs) form a SCIPU, and the other 4x4 chroma CB (the right side of the 8x4 chroma samples) and two luma CBs (8x4, 8x4 luma CBs) form a SCIPU by virtue of the binary tree (BT) split from the 4x4 chroma samples resulting in chroma CBs smaller than 16 chroma samples.
[00148] Figure 16 shows examples of SCIPU.
[00149] The type of a SCIPU is inferred to be non-inter if the current slice is an I slice or the current SCIPU has a 4x4 luma partition in it after being further divided once (by virtue of no 4x4 inter being allowed in VVC); otherwise, the type of the SCIPU (inter or non-inter) is indicated by a signaled indicator before the analysis of the CUs in the SCIPU. 2.14 Small Chroma Block Constraints in VVC Sketch 6
[00150] In the VVC 6 sketch (JVET-O2001-vE.docx), the constraints on the small chroma blocks are implemented as follows (related part is marked in bold and italics). coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, depthOffset, partIdx, treeTypeCurr, modeTypeCurr ) { Descritor se( split_cu_flag ) { se( ( allowSplitBtVer | | allowSplitBtHor | | allowSplitTtVer | | allowSplitTtHor ) && allowSplitQT ) split_qt_flag ae(v) se( !split_qt_flag ) { se( ( allowSplitBtHor | | allowSplitTtHor ) && ( allowSplitBtVer 11 allowSplitTtVer ) ) mtt_split_cu_vertical_flag ae(v) se( ( allowSplitBtVer && allowSplitTtVer && mtt_split_cu_vertical_flag ) | | ( allowSplitBtHor && allowSplitTtHor && !mtt_split_cu_vertical_flag ) ) mtt_split_cu_binary_flag ae(v)} se( modeTypeCondition = = 1) modeType = MODE_TYPE_INTRA se não se( modeTypeCondition = = 2 ) { mode_constraint_flag ae(v) modeType = mode_constraintflag ? MODETYPE INTRA : MODE_TYPE_INTER} se não { modeType = modeTypeCurr Petição 870220099106, de 26 / 10 / 2022, pág. 38 / 161 / 123 } treeType = ( modeType = = MODE_TYPE_INTRA ) ? DUAL_TREE_LUMA : treeTypeCurr se( !split_qt_flag ) { se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_VER ) { depthOffset += ( x0 + cbWidth > pic_width_in_luma_samples ) ? 1 : 0 x1 = x0 + ( cbWidth / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeightY, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_HOR ) { depthOffset += ( y0 + cbHeight > pic_heigth_in_luma_samples ) ? 1 : 0 y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1,depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_TT_VER ) { x1 = x0 + ( cbWidth / 4 ) x2 = x0 + ( 3 * cbWidth / 4 ) qgOnY = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnC = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( x0, y0, cbWidth / 4, cbHeight, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) coding_tree( x1, y0, cbWidth / 2, cbHeight, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) coding_tree( x2, y0, cbWidth / 4, cbHeight, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )} se não { / * SPLIT_TT_HOR * / y1 = y0 + ( cbHeight / 4 ) y2 = y0 + ( 3 * cbHeight / 4 ) qgOnY = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnC = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( x0, y0, cbWidth, cbHeight / 4, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset,0, treeType, modeType ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) coding_tree( x0, y2, cbWidth, cbHeight / 4, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )}} otherwise { x1 = x0 + ( cbWidth / 2 ) y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 0, treeType, modeType ) if( x1 < pic_width_in_luma_samples ), Petition 870220099106, dated 10 / 26 / 2022, p. 39 / 161 / 123 coding_tree( x1, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 1, treeType, modeType ) if( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 2, treeType, modeType ) if( y1 < pic_heigth_in_luma_samples && x1 < pic_width_in_luma_samples ) coding_tree( x1, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 3, treeType, modeType )} if( modeTypeCur = = MODE_TYPE_ALL && modeType = = MODETYPEINTRA ) { coding_tree(x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, 0, 0 DUAL_tree_chroma, modeType)}} if not coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeTypeCurr , modeTypeCurr )} 2.14.1.1 Syntax of the Encoding and / or Decoding Unit coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeType, modeType ) { Descritor chType = treeType = = DUAL_tree_chroma? 1 : 0 se( slice_type != I | | sps_ibc_enabled_flag | | sps_palette_enabled_flag) { se( treeType != DUAL_TREE_CHROMA && !( ( ( cbWidth = = 4 && cbHeight = = 4 ) 1 1 modeType = = MODE_TYPE_INTRA ) && !sps_ibc_enabled_flag ) ) cu_skip_flag[ x0 ][ y0 ] ae(v) se( cu_skip_flag[ x0 ][ y0 ] = = 0 && slice_type != I && !( cbWidth = = 4 && cbHeight = = 4 ) && modeType = = MODE_TYPE_ALL ) pred_mode_flag ae(v) se( ( ( slice_type = = I && cu_skip_flag[ x0 ][ y0 ] = =0 ) 11 ( slice_type != I && ( CuPredMode[ chType ][ x0 ][ y0 ] != MODE_INTRA 11 ( cbWidth = = 4 && cbHeight = = 4 && cu_skip_flag[ x0 ][ y0 ] = = 0 ) ) ) ) && cbWidth <= 64 && cbHeight <= 64 && modeType != MODE_TYPE_INTER && sps_ibc_enabled_flag && treeType != DUAL_TREE_CHROMA ) pred_mode_ibc_flag ae(v) se( ( ( ( slice_type = = I | | ( cbWidth = = 4 && cbHeight = = 4 ) | | sps_ibc_enabled_flag ) && CuPredMode[ x0 ][y0 ] = = MODE_INTRA ) 11 ( slice_type != I && !( cbWidth = = 4 && cbHeight = = 4 ) && !sps_ibc_enabled_flag && CuPredMode[ x0 ][ y0 ] != MODE_INTRA ) ) && sps_palette_enabled_flag && cbWidth <= 64 && cbHeight <= 64 && && cu_skip_flag[ x0 ][ y0 ] = = 0 && modeType != MODE_INTER ) pred_mode_plt_flag ae(v)} The variable modeTypeCondition is derived as follows: Petition 870220099106, dated 10 / 26 / 2022, p. 40 / 161 / 123 If one of the following conditions is true, modeTypeCondition is set to 0. - slice_type = = I and qtbtt_dual_tree_intra_fag equals 1 - modeTypeCurr is not equal to MODE_TYPE_ALL - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1. - cbWidth * cbHeight equals 64 and split_qt_fag equals 1 - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth * cbHeight equals 32 and MttSplitMode[ x0 ][y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1 + (slice_type != I ? 1 : 0) - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - cbWidth * cbHeight equals 128 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - In other circumstances, modeTypeCondition is set to 0. Quadruple division process allowed The inputs in this process are: - a block size for encoding and / or decoding (cbSize) in luma samples, - a multi-type tree depth mttDepth, - a treeType variable that specifies whether a single tree (SINGLE_TREE) or a dual tree is used to partition the CTUs and, when a dual tree is used, whether the luma components Petition 870220099106, dated 10 / 26 / 2022, page 41 / 161 / 123 (DUAL_TREE_LUMA) or chroma (DUAL_TREE_CHROMA) are currently being processed, - a modeType variable that specifies whether intra (MODE_INTRA), IBC (MODE_IBC), palette (MODE_PLT), and inter encoding and / or decoding modes can be used (MODE_TYPE_ALL), or whether only intra, IBC, and palette encoding and / or decoding modes can be used (MODE_TYPE_INTRA), or whether only inter encoding and / or decoding modes can be used (MODE_TYPE_INTER) for encoding and / or decoding units within the encoding and / or decoding tree node.
[00151] The output of this process is the variable allowSplitQt.
[00152] The allowSplitQt variable is derived as follows: If one or more of the following conditions are true, allowSplitQt is set to FALSE: - treeType is equal to SINGLE_TREE or DUAL_TREE_LUMA and cbSize is less than or equal to MinQtSizeY - treeType is equal to DUAL_TREE_CHROMA and cbSize / SubWidthC is less than or equal to MinQtSizeC - mttDepth is not equal to 0 - treeType is equal to DUAL_TREE_CHROMA and (cbSize / SubWidthC) is less than or equal to 4 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA - In other circumstances, allowSplitQt is set to TRUE. Binary division process allowed
[00153] Inputs in this process are: - a binary split mode called btSplit, - the width of the encoding and / or decoding block Petition 870220099106, dated 10 / 26 / 2022, page 42 / 161 / 123 cbWidth in luma samples, - a block height for encoding and / or decoding (cbHeight) in luma samples, - a location (x0, y0) of the top-left luma sample of the considered encoding and / or decoding block relative to the top-left luma sample of the figure, - a multi-type tree depth mttDepth, - a maximum depth of the multitype tree with maxMttDepth offset, - a maximum binary tree size maxBtSize, - a minimum quad tree size minQtSize, - a partition index partIdx, - a treeType variable that specifies whether a single tree (SINGLE_TREE) or a dual tree is used to partition the CTUs and, when a dual tree is used, whether luma (DUAL_TREE_LUMA) or chroma (DUAL_TREE_CHROMA) components are currently being processed, - a modeType variable that specifies whether intra (MODE_INTRA), IBC (MODE_IBC), palette (MODE_PLT) and inter encoding and / or decoding modes can be used (MODE_TYPE_ALL), or whether only intra, IBC, and palette encoding and / or decoding modes can be used (MODE_TYPE_INTRA), or whether only inter encoding and / or decoding modes can be used (MODE_TYPE_INTER) for encoding and / or decoding units within the encoding and / or decoding tree node.
[00154] The output of this process is the variable allowBtSplit. Table 6-2 - Specification of parallelTtSplit and cbSize based on btSplit. btSplit = = SPLIT_BT_VER btSplit = = SPLIT_BT_HOR parallelTtSplit SPLIT_TT_VER SPLIT_TT_HOR cbSize cbWidth cbHeight
[00155] The variables parallelTtSplit and cbSize are derived from the form Petition 870220099106, dated 10 / 26 / 2022, page 43 / 161 / 123 specified in Table 6-2.
[00156] The allowBtSplit variable is derived as follows: If one or more of the following conditions are true, allowBtSplit is set to FALSE: - cbSize is less than or equal to MinBtSizeY - cbWidth is greater than maxBtSize - cbHeight is greater than maxBtSize - mttDepth is greater than or equal to maxMttDepth - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 16 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE. - btSplit is equal to SPLIT_BT_VER - y0 + cbHeight is greater than pic_height_in_luma_samples - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE. - btSplit is equal to SPLIT_BT_VER - cbHeight is greater than MaxTbSizeY - x0 + cbWidth is greater than pic_width_in_luma_samples - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE. - btSplit is equal to SPLIT_BT_HOR - cbWidth is greater than MaxTbSizeY - y0 + cbHeight is greater than pic_height_in_luma_samples - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE. - x0 + cbWidth is greater than pic_width_in_luma_samples Petition 870220099106, dated 10 / 26 / 2022, p. 44 / 161 / 123 - y0 + cbHeight is greater than pic_height_in_luma_samples - cbWidth is greater than minQtSize - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE. - btSplit is equal to SPLIT_BT_HOR - x0 + cbWidth is greater than pic_width_in_luma_samples - y0 + cbHeight is less than or equal to pic_height_in_luma_samples - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE: - mttDepth is greater than 0 - partIdx equals 1 - MttSplitMode[ x0 ][ y0 ][ mttDepth - 1 ] is equal to parallelTtSplit - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE. - btSplit is equal to SPLIT_BT_VER - cbWidth is less than or equal to MaxTbSizeY - cbHeight is greater than MaxTbSizeY - In other circumstances, if all of the following conditions are true, allowBtSplit is set to FALSE. - btSplit is equal to SPLIT_BT_HOR - cbWidth is greater than MaxTbSizeY - cbHeight is less than or equal to MaxTbSizeY - In other circumstances, allowBtSplit is set to TRUE. Ternary division process allowed
[00157] Inputs in this process are: - a ternary split mode ttSplit, Petition 870220099106, dated 10 / 26 / 2022, page 45 / 161 / 123 - a block width for encoding and / or decoding (cbWidth) in luma samples, - a block height for encoding and / or decoding (cbHeight) in luma samples, - a location (x0, y0) of the top-left luma sample of the considered encoding and / or decoding block relative to the top-left luma sample of the figure, - a multi-type tree depth mttDepth - a maximum depth of the multitype tree with maxMttDepth offset, - a maximum size for the ternary tree maxTtSize, - a treeType variable that specifies whether a single tree (SINGLE_TREE) or a dual tree is used to partition the CTUs and, when a dual tree is used, whether luma (DUAL_TREE_LUMA) or chroma (DUAL_TREE_CHROMA) components are currently being processed, - a modeType variable that specifies whether intra (MODE_INTRA), IBC (MODE_IBC), palette (MODE_PLT) and inter encoding and / or decoding modes can be used (MODE_TYPE_ALL), or whether only intra, IBC, and palette encoding and / or decoding modes can be used (MODE_TYPE_INTRA), or whether only inter encoding and / or decoding modes can be used (MODE_TYPE_INTER) for encoding and / or decoding units within the encoding and / or decoding tree node.
[00158] The output of this process is the variable allowTtSplit. Table 6-3 - cbSize specification based on ttSplit. ttSplit = = SPLIT_TT_VER ttSplit = = SPLIT_TT_HOR cbSize cbWidth cbHeight
[00159] The variable cbSize is derived from the form specified in Table 6-3. Petition 870220099106, dated 10 / 26 / 2022, page 46 / 161 / 123
[00160] The allowTtSplit variable is derived as follows: If one or more of the following conditions are true, allowTtSplit is set to FALSE: - cbSize is less than or equal to 2 * MinTtSizeY - cbWidth is greater than Min( MaxTbSizeY, maxTtSize ) - cbHeight is greater than Min( MaxTbSizeY, maxTtSize ) - mttDepth is greater than or equal to maxMttDepth - x0 + cbWidth is greater than pic_width_in_luma_samples - y0 + cbHeight is greater than pic_height_in_luma_samples - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 32 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA - In other circumstances, allowTtSplit is set equal to TRUE.
[00161] pred_mode_flag equal to 0 specifies that the current encoding and / or decoding unit is encoded and / or decoded in inter-prediction mode. pred_mode_flag equal to 1 specifies that the current encoding and / or decoding unit is encoded and / or decoded in intra-prediction mode.
[00162] When pred_mode_flag is not present, the following is inferred:
[00163] - If cbWidth equals 4 and cbHeight equals 4, pred_mode_flag is inferred to be equal to 1.
[00164] - In other circumstances, if modeType is equal to MODE_TYPE_INTRA, pred_mode_flag is inferred to be equal to 1.
[00165] - In other circumstances, if modeType is equal to MODE_TYPE_INTER, pred_mode_flag is inferred to be equal to 0.
[00166] - In other circumstances, pred_mode_flag is inferred as Petition 870220099106, dated 10 / 26 / 2022, page 47 / 161 / 123 equal to 1 during the decoding of slice I, and equal to 0 during the decoding of slice P or B, respectively.
[00167] The variable CuPredMode[ chType ][ x ][ y ] is derived as follows for x = x0..x0 + cbWidth - 1 and y = y0..y0 + cbHeight - 1: - If pred_mode_flag is equal to 0, CuPredMode[ chType ][ x ][ y ] is set equal to MODE_INTER.
[00168] - Under other circumstances (pred_mode_flag equals 1), CuPredMode[ chType ][ x ][ y ] is set equal to MODE_INTRA.
[00169] pred_mode_ibc_flag equal to 1 specifies that the current encoding and / or decoding unit is encoded and / or decoded in IBC prediction mode. pred_mode_ibc_flag equal to 0 specifies that the current encoding and / or decoding unit is not encoded and / or decoded in IBC prediction mode.
[00170] When pred_mode_ibc_flag is not present, it is inferred as follows: - If cu_skip_flag[ x0 ][ y0 ] equals 1, and cbWidth equals 4, and cbHeight equals 4, pred_mode_ibc_flag is inferred to be equal to 1.
[00171] - In other circumstances, if both cbWidth and cbHeight are equal to 128, pred_mode_ibc_flag is inferred to be equal to 0.
[00172] - In other circumstances, if modeType is equal to MODE_TYPE_INTER, pred_mode_ibc_flag is inferred to be equal to 0.
[00173] - In other circumstances, if treeType is equal to DUAL_TREE_CHROMA, pred_mode_ibc_flag is inferred to be equal to 0.
[00174] - In other circumstances, pred_mode_ibc_flag is inferred to be equal to the value of sps_ibc_enabled_flag during the decoding of an I slice, and 0 during the decoding of a P or B slice, respectively.
[00175] When pred_mode_ibc_flag is equal to 1, the variable CuPredMode[ chType ][ x ][ y ] is set to be equal to MODE_IBC for x = x0..x0 + cbWidth - 1 and y = y0..y0 + cbHeight - 1. Petition 870220099106, dated 10 / 26 / 2022, p. 48 / 161 / 123 3. Problems
[00176] 1. Currently, IBC is considered as MODE_TYPE_INTRA, and thus a small block of chroma is disallowed, leading to unnecessary loss of encoding and / or decoding efficiency.
[00177] 2. Currently, palette is considered as MODE_TYPE_INTRA, and thus a small block of chroma is disallowed, leading to unnecessary loss of encoding and / or decoding efficiency.
[00178] 3. Currently, small block chroma restrictions do not consider color subsampling format.
[00179] 4. Currently, the same partitioning mode and small-block prediction constraints are applied across all chroma formats. However, it may be desirable to design different small-block constraint mechanisms in 4:2:0 and 4:2:2 chroma formats.
[00180] 5. Currently, the palette mode indicator signaling depends on modeType, which is undesirable, since palette may not apply to small block constraints.
[00181] 6. Currently, the IBC mode flag is inferred as 0 for P / B slice with cu_skip_flag equal to 1, but MODE_TYPE equal to MODE_TYPE_INTRA, this is illegal in syntax parsing.
[00182] 7. Currently, the non-4x4 IBC luma mode is not allowed for SCIPU luma blocks, which may be undesirable and could cause loss of encoding and / or decoding efficiency.
[00183] 8. The 2xH chroma block is still allowed, which is not hardware implementation friendly.
[00184] 9. CIIP is considered to be of MODE_INTER as long as it uses intraprediction, which breaks the restrictions in some cases.
[00185] 10. When SCIPU is applied, delta QP for chroma can be Petition 870220099106, dated 10 / 26 / 2022, p. 49 / 161 / 123, flagged depending on the luma split. For example, when the current block dimensions are 16x8 in luma samples and are split with vertical TT, a local dual tree can be applied. It is specified that qgOnC = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ).
[00186] Therefore, qgOnC is set to zero if cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv. This conditional setting assumes that the chroma component is also split by TT. With the local dual tree, the chroma component may not be split, thus cbSubdiv may be greater than cu_chroma_qp_offset_subdiv. IsCuChromaQpOffsetCoded should be set to 0 to allow QP delta signaling for chroma. However, IsCuChromaQpOffsetCoded is not set to 0 because qgOnC is set to 0.
[00187] 1. The maximum transform size for lossless encoding and / or decoding can be set differently from the maximum transform size for lossy encoding and / or decoding. 4. Examples of technical solutions and modalities
[00188] The following list should be considered as examples. These techniques should not be interpreted in a strict manner. Furthermore, these techniques can be combined in any way.
[00189] In this document, “MxN encoding and / or decoding tree node” indicates an MxN block, with M as the block width and N as the block height in luma samples, which may be further partitioned, such as by QT / BT / TT. For example, a block may be a QT node, or a BT node, or a TT node. An encoding and / or decoding tree node may be a single encoding and / or decoding unit (e.g., with three color components for a single tree, with two chroma color components for dual tree chroma encoding and / or decoding, and only one component). Petition 870220099106, dated 10 / 26 / 2022, page 50 / 161 / 123 of luma color for encoding and / or decoding of dual tree luma), or a luma encoding and / or decoding block, or a chroma encoding and / or decoding block. A “small node unit of the encoding and / or decoding tree” may indicate a node of the encoding and / or decoding tree with a block size MxN equal to 32 / 64 / 128 in luma samples.
[00190] Unless specifically mentioned, the width W and height H for an encoding and / or decoding block are measured in luma samples. For example, encoding and / or decoding block MxN means one luma block MxN, and / or two chroma blocks (M / SubWidthC) x (N / SubHeightC), where SubWidthC and SubHeightC are derived by chroma format, as follows.___________________________________ chroma_format_idc separate_colour_plane_flag Chroma Format SubWidthC SubHeightC 0 0 Monochrome 1 1 1 0 4:2:0 2 2 2 0 4:2:2 2 1 3 0 4:4:4 1 1 3 1 4:4:4 1 1
[00191] 1. Whether and / or how to partition into small blocks may depend on color formats.
[00192] a. In one example, for the 4:4:4 color format, the restrictions on chroma block sizes may follow those restrictions on luma blocks.
[00193] b. In one example, for the 4:2:2 color format, the restrictions on chroma block sizes may follow those restrictions for the 4:2:0 color format.
[00194] c. In one example, for the 4:0:0 and / or 4:4:4 chroma format, the restrictions on small block partitions and / or prediction modes may not apply.
[00195] d. In one example, the restrictions on small block partitions and / or prediction modes may be applied differently for different chroma formats. Petition 870220099106, dated 10 / 26 / 2022, page 51 / 161 / 123
[00196] i. In one example, for the MxN encoding and / or decoding tree node (such as 8x8) with horizontal BT splitting, in 4:2:2 chroma format, horizontal BT splitting may be enabled for both chroma and luma blocks, whereas, in 4:2:0 chroma format, horizontal BT splitting may be enabled for luma blocks but disabled for chroma blocks.
[00197] ii. In one example, for an MxN encoding and / or decoding tree node (such as 16x4) with vertical BT splitting, in 4:2:2 chroma format, vertical BT splitting may be enabled for both chroma and luma blocks, whereas, in 4:2:0 chroma format, vertical BT splitting may be enabled for luma blocks but disabled for chroma blocks.
[00198] iii. In one example, for the MxN encoding and / or decoding tree node (such as 8x16) with horizontal TT splitting, in 4:2:2 chroma format, horizontal TT splitting may be enabled for both chroma and luma blocks, whereas, in 4:2:0 chroma format, horizontal TT splitting may be enabled for luma blocks but disabled for chroma blocks.
[00199] iv. In one example, for the MxN encoding and / or decoding tree node (such as 32x4) with vertical TT splitting, in 4:2:2 chroma format, vertical TT splitting may be enabled for both chroma and luma blocks, whereas, in 4:2:0 chroma format, vertical TT splitting may be enabled for luma blocks but disabled for chroma blocks.
[00200] v. In one example, for 4:0:0 and / or 4:4:4 color formats, small block restrictions may not apply.
[00201] e. In one example, whether SCIPU is enabled is dependent on the color format.
[00202] i. In one example, SCIPU is enabled for color formats Petition 870220099106, dated 10 / 26 / 2022, p. 52 / 161 / 123 4:2:0 and 4:2:2.
[00203] ii. In one example, SCIPU is disabled for the 4:0:0 and / or 4:4:4 color format.
[00204] 1. In one example, modeType can always be equal to MODE_TYPE_ALL for 4:0:0 and / or 4:4:4 color format.
[00205] 2. In one example, modeTypeCondition can always be equal to 0 for the 4:0:0 and / or 4:4:4 color format.
[00206] 2. How determining the prediction modes (and / or modeType) for (sub)blocks of a node in the encoding and / or decoding tree may depend on chroma formats.
[00207] a. In one example, if one of the following conditions is true, the modeType of (sub)blocks partitioned by this node of the encoding and / or decoding tree may be equal to MODE_TYPE_ALL for the 4:2:2 chroma format, while for the 4:2:0 chroma format, the modeType may be equal to MODE_TYPE_INTRA or MODE_TYPE_INTER.
[00208] i. Node of the MxN encoding and / or decoding tree (such as 8x8) with horizontal BT division
[00209] ii. Node of the MxN encoding and / or decoding tree (such as 16x4) with vertical BT split.
[00210] iii. Node of the MxN encoding and / or decoding tree (such as 8x16) with horizontal TT division
[00211] iv. Node of the MxN encoding and / or decoding tree (such as 32x4) with vertical TT division
[00212] 3. It is proposed to rename MODE_TYPE_INTRA to MODE_TYPE_NO_INTER and restrict the use of MODE_INTER.
[00213] a. In one example, when modeType of an encoding and / or decoding unit is equal to MODE_TYPE_NO_INTER, MODE_INTER may be disallowed. Petition 870220099106, dated 10 / 26 / 2022, p. 53 / 161 / 123
[00214] 4. It is proposed to rename MODE_TYPE_INTER to MODE_TYPE_NO_INTRA and restrict the use of MODE_INTRA.
[00215] a. In one example, when modeType of an encoding and / or decoding unit is equal to MODE_TYPE_NO_INTRA, MODE_INTRA may be disallowed.
[00216] 5. The mode restriction indicator can never be signaled in 4:2:2 and / or 4:0:0 and / or 4:4:4 chroma formats.
[00217] a. In one example, when the mode restriction indicator is not present, it can be inferred to be equal to 1.
[00218] i. Alternatively, when the mode restriction flag is not present, it can be inferred to be equal to 0.
[00219] 6. Whether and / or how to apply SCIPU to an MxN encoding and / or decoding block, with M as the block width and N as the block height, may depend on whether the color format is 4:2:0 or 4:2:2.
[00220] a. In one example, in 4:2:2 color format, for an MxN encoding and / or decoding block with M as the block width and N as the block height, SCIPU can only be activated if M multiplied by N (denoted by M*N) equals 64 or 32.
[00221] b. In one example, a node in the encoding and / or decoding tree with M*N = 128 may never be treated as a SCIPU block in 4:2:2 color format.
[00222] c. In one example, a node in the encoding and / or decoding tree with BT split and M*N = 64 may never be treated as a SCIPU block in 4:2:2 color format.
[00223] d. In one example, a node in the encoding and / or decoding tree with split_qt_flag equal to 1 and M*N = 64 could be a SCIPU block in 4:2:2 color format.
[00224] e. In one example, a node in the encoding and / or decoding tree with TT division and M*N = 64 can be treated as a block. Petition 870220099106, dated 10 / 26 / 2022, p. 54 / 161 / 123 SCIPU in 4:2:2 color format.
[00225] f. In one example, a node in the encoding and / or decoding tree with BT split and M*N = 32 can be treated as a SCIPU block in 4:2:2 color format.
[00226] g. In the description shown, for a SCIPU block in 4:2:2 color format, modeTypeCondition can always be equal to 1.
[00227] h. In the description shown, for a SCIPU block in 4:2:2 color format, only MODE_TYPE_INTRA can be allowed for both the current block in the parent node and all sub-blocks under the child leaf nodes.
[00228] 7. In 4:2:2 color format, modeTypeCondition of a block SCIPU can always equal 1.
[00229] a. In one example, modeTypeCondition can be equal to 0 or 1 for the 4:2:2 color format.
[00230] b. In one example, for SCIPU blocks in 4:2:2 color format, modeTypeCondition can never be equal to 2.
[00231] 8. In the 4:2:2 color format, modeType of a SCIPU block can always be equal to MODE_TYPE_INTRA.
[00232] a. In one example, modeType can be equal to MODE_TYPE_ALL or MODE_TYPE_INTRA in the 4:2:2 color format.
[00233] b. In one example, for SCIPU blocks in 4:2:2 color format, MODE_TYPE_INTER can be disabled.
[00234] 9. Whether block partitioning is allowed or not can depend on modeType and / or block size.
[00235] a. In one example, whether BT and / or TT splitting is allowed for a block may be dependent on the modeType.
[00236] i. In one example, if modeType is equal to MODE_TYPE_INTER, then BT splitting can be disallowed for the current encoding and / or decoding block (for example, allowBtSplit is set equal to false). Petition 870220099106, dated 10 / 26 / 2022, p. 55 / 161 / 123
[00237] ii. In one example, if modeType is equal to MODE_TYPE_INTER, then TT splitting can be disallowed for the current encoding and / or decoding block (for example, allowTtSplit is set equal to false).
[00238] b. In one example, whether BT and / or TT splitting is allowed for a block may be dependent on the modeType and block size.
[00239] i. In one example, for an MxN encoding and / or decoding block, with M as the block width and N as the block height, when M*N is less than or equal to 32 and modeType is equal to MODE_TYPE_INTER, the BT split can be disallowed (for example, allowBtSplit is set equal to false).
[00240] ii. In one example, for an MxN encoding and / or decoding block, with M as the block width and N as the block height, when M*N is less than or equal to 64 and modeType is equal to MODE_TYPE_INTER, the TT split can be disallowed (for example, allowTtSplit is set equal to false).
[00241] 10. When modeTypeCurr of an encoding and / or decoding tree is equal to MODE_TYPE_INTER, the division of the encoding and / or decoding tree may be restricted.
[00242] a. In one example, when modeTypeCurr of an encoding and / or decoding tree is equal to MODE_TYPE_INTER, BT splitting may be disallowed.
[00243] b. In one example, when modeTypeCurr of an encoding and / or decoding tree is equal to MODE_TYPE_INTER, TT splitting may be disallowed.
[00244] c. In one example, when modeTypeCurr of an encoding and / or decoding tree is equal to MODE_TYPE_INTER, QT splitting may be disallowed.
[00245] d. In one example, when modeTypeCurr of a tree of Petition 870220099106, dated 10 / 26 / 2022, page 56 / 161 / 123 If encoding and / or decoding is equal to MODE_TYPE_INTER and the luma block size is less than or equal to 32, BT division may be disallowed.
[00246] e. In one example, when modeTypeCurr of an encoding and / or decoding tree is equal to MODE_TYPE_INTER and the luma block size is less than or equal to 64, TT splitting may be disallowed.
[00247] 11. An encoding and / or decoding unit with treeType being DUAL_TREE_LUMA can be encoded and / or decoded in inter mode.
[00248] a. In one example, the encoding and / or decoding unit encoded and / or decoded in inter encoding and / or decoding mode, i.e., MODE_INTER, may only contain Luma components even for color formats with multiple color components.
[00249] b. In one example, pred_mode_flag may need to be parsed for the DUAL_TREE_LUMA block.
[00250] c. In one example, for the DUAL_TREE_LUMA block encoded and / or decoded in inter mode, the same inter mode restrictions for SINGLE_TREE may also apply.
[00251] i. In one example, the inter 4x4 DUAL_TREE_LUMA block can be disallowed.
[00252] 12. Intra chroma blocks (and / or IBCs) with a block width equal to M (such as M=2) chroma samples may not be allowed.
[00253] a. In one example, intra-chroma blocks 2xN (such as, N <= 64) may be disallowed in a dual tree.
[00254] i. In one example, when treeType is equal to DUAL_TREE_CHROMA and the block width is equal to 4 chroma samples, vertical BT splitting can be disabled.
[00255] ii. In one example, when treeType equals Petition 870220099106, dated 10 / 26 / 2022, p. 57 / 161 / 123 If DUAL_TREE_CHROMA has a block width equal to 8 chroma samples, vertical TT splitting can be disabled.
[00256] b. In one example, intra-chroma blocks 2xN (such as N <= 64) (and / or IBC) may not be allowed in an individual tree.
[00257] i. In one example, for an MxN encoding and / or decoding tree node (such as M=8 and N<=64) with vertical BT splitting, one of the following processes can be applied.
[00258] 1. Vertical BT split may be disabled for 4xN or 4x (N / 2) chroma blocks, but allowed for 8xN luma blocks.
[00259] 2. The 4xN or 4x (N / 2) chroma block may not be vertical BT division, and it may be encoded and / or decoded by MODE_INTRA, or MODE_IBC.
[00260] 3. Vertical BT splitting may be allowed for both 8xN luma and 4xN or 4x (N / 2) chroma blocks, but for both luma and chroma blocks not encoded and / or decoded by MODE_INTRA (for example, they may be encoded and / or decoded by MODE_INTER, or MODE_IBC).
[00261] ii. In one example, for an MxN encoding and / or decoding tree node (such as M=16 and N<=64) with vertical TT splitting, one of the following processes can be applied.
[00262] 1. Vertical TT splitting may be disabled for 8xN or 8x (N / 2) chroma blocks, but allowed for 16xN luma blocks.
[00263] 2. The 8xN or 8x (N / 2) chroma block may not be vertically TT division and encoded and / or decoded by MODE_INTRA, or MODE_IBC.
[00264] 3. Vertical TT division may be allowed for both 16xN luma blocks and 8xN or 8x (N / 2) chroma blocks, but both luma and chroma blocks may not be encoded and / or decoded by MODE_INTRA (for example, they may be encoded and / or decoded by MODE_INTER, or MODE_IBC). Petition 870220099106, dated 10 / 26 / 2022, p. 58 / 161 / 123
[00265] 13. IBC mode may be enabled for luma and / or chroma blocks, regardless of whether the block is of small size.
[00266] a. In one example, IBC mode may be enabled for luma blocks including 8x4 / 8x8 / 16x4 and 4xN luma blocks (such as N <= 64), even if modeType is equal to MODE_TYPE_INTRA.
[00267] b. In one example, IBC mode may be allowed for chroma blocks, even if modeType is equal to MODE_TYPE_INTRA.
[00268] 14. The IBC forecast mode signaling indicator may depend on the forecast mode type (e.g., MODE_TYPE_INTRA).
[00269] a. In one example, the IBC prediction mode indicator for a non-SKIP block (e.g., an encoding and / or decoding block that is not encoded and / or decoded by the skip mode) can be explicitly signaled in the continuous bitstream when treeType is not equal to DUAL_TREE_CHROMA and modeType is equal to MODE_TYPE_INTRA.
[00270] 15. The forecast IBC mode indicator can be inferred depending on the CU SKIP indicator and the mode type (e.g., modeType).
[00271] a. In one example, if the current block is encoded and / or decoded with skip mode (such as cu_skip_flag equals 1), and modeType equals MODE_TYPE_INTRA, the IBC prediction mode indicator (such as pred_mode_ibc_flag) can be inferred to be equal to 1.
[00272] 16. Explicit signaling of the palette mode indicator may not depend on modeType.
[00273] a. In one example, the flagging of the palette mode indicator (such as pred_mode_plt_flag) may depend on the slice type, block size, prediction mode, etc., but it doesn't matter what the Petition 870220099106, dated 10 / 26 / 2022, p. 59 / 161 / 123 modeType.
[00274] b. In one example, the palette mode indicator (such as pred_mode_plt_flag) is inferred to be 0 when modeType is equal to MODE_TYPE_INTER or MODE_TYPE_INTRA.
[00275] 17. IBC mode may be allowed for use when modeType is equal to MODE_TYPE_INTER a. In one example, IBC chroma may be disallowed when modeType is equal to MODE_TYPE_INTRA.
[00276] b. In one example, IBC mode may be allowed for use when modeType is equal to MODE_TYPE_INTRA or MODE_TYPE_INTER.
[00277] c. In one example, IBC mode may be allowed for use regardless of what the modeType is.
[00278] d. In one example, in a SCIPU, both IBC and inter modes may be permitted.
[00279] e. In one example, the size of the IBC chroma block can always correspond to the size of the corresponding luma block.
[00280] f. In one example, when modeType is equal to MODE_TYPE_INTER and the encoding and / or decoding unit size is 4x4 in luma, the pred_mode_ibc_flag signaling can be ignored and pred_mode_ibc_flag can be inferred as equal to 1.
[00281] 18. Palette mode may be enabled for use when modeType is MODE_TYPE_INTER a. In one example, the chroma palette may be disabled when modeType is MODE_TYPE_INTRA.
[00282] b. In one example, IBC mode may be allowed for use when modeType is equal to MODE_TYPE_INTRA or MODE_TYPE_INTER.
[00283] c. In one example, IBC mode may be allowed for use Petition 870220099106, dated 10 / 26 / 2022, pp. 60 / 161 / 123 regardless of the modeType.
[00284] d. In one example, palette mode may be allowed for use when modeType is equal to MODE_TYPE_INTRA or MODE_TYPE_INTER.
[00285] e. In one example, palette mode may be allowed for use regardless of what the modeType is.
[00286] f. In one example, in a SCIPU, both palette and inter modes may be allowed.
[00287] g. In one example, in a SCIPU, palette, IBC and inter modes can all be enabled.
[00288] h. In one example, the palette chroma block size can always match the corresponding luma block size.
[00289] i. In one example, when modeType is equal to MODE_TYPE_INTER and the encoding and / or decoding unit size is 4x4 in luma, the pred_mode_plt_flag signaling can be ignored and pred_mode_plt_flag can be inferred as equal to 1.
[00290] j. In one example, when modeType is equal to MODE_TYPE_INTER and the encoding and / or decoding unit size is 4x4 in luma, a message can be sent to indicate whether the current prediction mode is IBC or palette.
[00291] k. In one example, whether palette mode is enabled / disabled may depend on slice types and modeType.
[00292] i. In one example, for slices I with MODE_TYPE_INTRA, palette mode can be enabled.
[00293] ii. In one example, for B / W slices with MODE_TYPE_INTER, palette mode can be enabled.
[00294] 19. When palette mode is enabled, the local dual tree may be disabled.
[00295] a. In one example, when palette mode is activated, Petition 870220099106, dated 10 / 26 / 2022, p. 61 / 161 / 123 modeTypeCondition can always be set to 0.
[00296] 20. For small chroma blocks with width equal to M (e.g., M = 2) or height equal to N (e.g., N = 2), allowed intraprediction modes may be restricted to be different from those allowed for large chroma blocks.
[00297] a. In one example, only a subset of intra-prediction modes of available chroma intraprediction modes can be used.
[00298] b. In one example, only the INTRA_DC mode can be used.
[00299] c. In one example, only the INTRA_PLANAR mode can be used.
[00300] d. In one example, only the INTRA_ANGULAR18 mode can be used.
[00301] e. In one example, only the INTRA_ANGULAR50 mode can be used.
[00302] f. In one example, CCLM modes can be deauthorized.
[00303] 21. For small chroma blocks with width equal to M (for example, M = 2) or height equal to N (for example, N = 2), transform types may be restricted to be different from those allowed for large chroma blocks.
[00304] a. In one example, only ignore transform can be used.
[00305] b. In one example, only a one-dimensional transform can be used.
[00306] c. In one example, encoding and / or decoding tools that support multiple types of transforms are disallowed.
[00307] i. Alternatively, the signaling of the tools of Petition 870220099106, dated 10 / 26 / 2022, page 62 / 161 / 123, encoding and / or decoding that support multiple types of transforms is omitted.
[00308] 22. CIIP can be considered as MODE_TYPE_INTRA.
[00309] a. In one example, CIIP mode may be enabled when dual tree partitioning is used.
[00310] i. In one example, CIIP mode may be enabled when the CU type is DUAL_TREEE_CHROMA.
[00311] b. Alternatively, CIIP can be considered as MODE_TYPE_INTER
[00312] i. In one example, when the chroma block width is equal to M (for example, M=2), the CIIP mode may be disabled.
[00313] ii. In one example, when the chroma block width is equal to M (for example, M=2), the intraprediction modes for chroma in CIIP can be restricted to simple intraprediction mode.
[00314] 1. In one example, INTRA_DC can be used for intraprediction of chroma, when the width of the chroma block is equal to M (for example, M=2).
[00315] 2. In one example, INTRA_ANGULAR18 can be used for intraprediction of chroma, when the width of the chroma block is equal to M (for example, M=2).
[00316] 3. In one example, INTRA_ANGULAR50 can be used for intrachroma prediction, when the chroma block width is equal to M (for example, M=2).
[00317] iii. In one example, intraprediction modes for chroma in CIIP can be restricted to simple intraprediction mode.
[00318] 1. In one example, INTRA_DC can be used for intrachroma prediction.
[00319] 2. In one example, the INTRA_ANGULAR18 mode can be used for intrachroma prediction. Petition 870220099106, dated 10 / 26 / 2022, page 63 / 161 / 123
[00320] 3. In one example, the INTRA_ANGULAR50 mode can be used for intrachroma prediction.
[00321] 23. For the items shown, the variables M and / or N can be predefined or flagged.
[00322] a. In one example, M and / or N may be additionally dependent on color formats (e.g., 4:2:0, 4:2:2, 4:4:4).
[00323] 24. modeType can be extended to cover more types.
[00324] a. In one example, modeType might be MODE_TYPE_IBC. When modeType equals MODE_TYPE_IBC, the prediction mode is inferred to be IBC.
[00325] i. In one example, pred_mode_flag is not flagged in this case.
[00326] ii. In one example, pred_mode_ibc_flag is not flagged in this case.
[00327] iii. In one example, pred_mode_plt_flag is not flagged in this case.
[00328] b. In one example, modeType might be MODE_TYPE_PALETTE. When modeType equals MODE_TYPE_PALETTE, the prediction mode is inferred as palette mode.
[00329] i. In one example, pred_mode_flag is not flagged in this case.
[00330] ii. In one example, pred_mode_ibc_flag is not flagged in this case.
[00331] iii. In one example, pred_mode_plt_flag is not flagged in this case.
[00332] c. In one example, mode_constraint_flag can be replaced by an index to indicate which of the allowed modeTypes are being used.
[00333] 25. In one example, if QT splitting is allowed for a block Petition 870220099106, dated 10 / 26 / 2022, p. 64 / 161 / 123, with WxH dimensions, may depend on modeType combined with dimensions.
[00334] a. For example, if modeType equals MODE_TYPE_INTER and W equals 8 and H equals 8, QT division is disallowed.
[00335] 26. In one example, whether vertical TT splitting is allowed for a block with WxH dimensions may depend on modeType combined with dimensions.
[00336] a. For example, if modeType equals MODE_TYPE_INTER and W equals 16 and H equals 4, vertical TT splitting is disallowed.
[00337] 27. In one example, whether horizontal TT splitting is allowed for a block with WxH dimensions may depend on modeType combined with dimensions.
[00338] a. For example, if modeType equals MODE_TYPE_INTER and W equals 4 and H equals 16, horizontal TT division is disallowed.
[00339] 28. In one example, whether vertical BT splitting is allowed for a block with WxH dimensions may depend on modeType combined with dimensions.
[00340] a. For example, if modeType equals MODE_TYPE_INTER and W equals 8 and H equals 4, vertical BT splitting is disabled.
[00341] 29. In one example, whether horizontal TT splitting is allowed for a block with WxH dimensions may depend on modeType combined with dimensions.
[00342] a. For example, if modeType equals MODE_TYPE_INTER and W equals 4 and H equals 8, horizontal BT splitting is disabled. Petition 870220099106, dated 10 / 26 / 2022, pp. 65 / 161 / 123
[00343] 30. In one example, whether the prediction mode of a CU is inferred by modeType may depend on color components and / or WxH block dimensions.
[00344] a. For example, the prediction mode of a chroma CU is inferred by modeType; but the prediction mode of a luma CU is signaled rather than inferred by modeType.
[00345] i. For example, the prediction mode of a luma CU is signaled rather than inferred by modeType if W>4 or H>4.
[00346] 31. When SCIPU is applied, whether and / or how to signal delta QP-related information for a first component may depend on how the first component is split.
[00347] a. In one example, when SCIPU is applied, whether and / or how to signal delta QP-related information from a first component may depend on the way the first component is split and be decoupled from the way a second component is split.
[00348] b. In one example, the first component is luma and the second component is chroma.
[00349] c. In one example, the first component is chroma and the second component is luma.
[00350] 32. No variable related to delta QP of a first component may be modified during the decoding or analysis process of a second component when the dual tree structure and / or the local dual encoding and / or decoding tree is applied.
[00351] a. In one example, the structure of the local dual encoding and / or decoding tree can be used in accordance with SCIPU.
[00352] b. In one example, the first component is luma and the second component is chroma.
[00353] i. The variable can be IsCuQpDeltaCoded.
[00354] c. In one example, the first component is chroma and the Petition 870220099106, dated 10 / 26 / 2022, page 66 / 161 / 123 second component is luma.
[00355] i. The variable can be IsCuChromaQpOffsetCoded.
[00356] 33. When SCIPU is applied, delta QP information for a component (such as luma or chroma) can be signaled at most once in a specific region where it is required that the luma component and the chroma component share the same mode type (such as MODE_TYPE_INTER or MODE_TYPE_INTRA).
[00357] a. In one example, the specific region is considered as a quantization group.
[00358] 34. Intra-chroma blocks MxN with M as block width and N as block height may not be allowed.
[00359] a. In one example, DC prediction can be used for intraprediction of MxN chroma, for example, M = 2 chroma samples, N = 8 and / or 16 and / or 32 chroma samples.
[00360] i. In one example, the reconstructed neighboring pixels may not be used for DC prediction.
[00361] ii. In one example, neighboring reference pixels can be set equal to 1 << (bit depth - 1) for DC prediction.
[00362] iii. In one example, PDPC may not be applied to the DC forecast.
[00363] iv. In one example, DC mode information may not be encoded and / or decoded for the intrachroma MxN block, but derived.
[00364] b. In one example, CCLM prediction can be used for intraprediction of MxN chroma, for example, M = 2 chroma samples, N = 8 and / or 16 and / or 32 chroma samples.
[00365] i. In one example, the reconstructed neighboring pixels may not be used for CCLM prediction.
[00366] ii. In one example, for CCLM prediction predC = a*recL + b where the chroma prediction value predC is derived from the value Petition 870220099106, dated 10 / 26 / 2022, page 67 / 161 / 123, reconstructed from luma recL, the aeb parameters can be initialized to fixed default values (such as a=0, b=512) at the beginning of a video unit, such as SPS / VPS / PPS / Figure / Subfigure / Slice / Grid / Block / CTU line / CTU / VPDU / CU / PU / TU.
[00367] 1. In one example, a first-in, first-out table can be quickly maintained to update the CCLM parameters a and b.
[00368] iii. In one example, PDPC may not be applied to the CCLM forecast.
[00369] iv. In one example, the CCLM mode information may not be encoded and / or decoded for the intrachroma MxN block, but derived.
[00370] v. Alternatively, the proposed methods can be applied to other types of chroma blocks encoded and / or decoded in CCLM with width not equal to M or height not equal to N.
[00371] 1. In one example, the CCLM parameters of previously encoded and / or decoded blocks can be used for the current block, instead of being derived based on reconstruction information from the current block's neighboring blocks.
[00372] 2. In one example, the CCLM parameters can be stored in a table and updated quickly, such as using FIFO.
[00373] c. In one example, intra-chroma blocks MxN may not be allowed in a dual tree, for example, M = 2 chroma samples, N = 8 and / or 16 and / or 32 chroma samples.
[00374] i. In one example, when treeType is equal to DUAL_TREE_CHROMA, X-splitting can be disabled for an encoding and / or decoding tree node with dimension equal to (M*a)x(N*b), where M*a is the width of the encoding and / or decoding tree node in chroma samples, and N*b is the height of the tree node. Petition 870220099106, dated 10 / 26 / 2022, page 68 / 161 / 123 encoding and / or decoding in chroma samples.
[00375] 1. In one example, X is vertical division BT, a = 2, b = 1 2. In one example, X is horizontal division BT, a = 1, b = 2 3. In one example, X is vertical division TT, a = 4, b = 1 4. In one example, X is horizontal division T, a = 1, b = 4 d. In one example, intra-chroma blocks MxN may not be allowed in an individual tree, for example, M = 2 chroma samples, N = 8 and / or 16 and / or 32 chroma samples.
[00376] i. In one example, in a single tree, X splitting can be disabled for the chroma components of an encoding and / or decoding tree node with dimension equal to (M*a*subWidthC) x (N*b*subHeightC), where M*a is the width of the encoding and / or decoding tree node in luma samples, N*b is the height of the encoding and / or decoding tree node in luma samples, and subWidthC and subHeightC are the ratio of chroma subsampling to the width and height dimensions, for example, subWidthC and subHeightC are equal to 2 for the 4:2:0 chroma format.
[00377] 1. In an example, X = vertical division BT, a = 2, b = 1 2. In one example, X = vertical division TT, a = 4, b = 1 3. In one example, X = horizontal division BT, a = 1, b = 2 4. In one example, X = horizontal division TT, a = 1, b = 2 5. In one example, X = horizontal division TT, a = 1, b = 4 6. In one example, the undivided chroma block can have dimensions equal to (M*a) x (N*d).
[00378] 7. In one example, the undivided chroma block can be determined as MODE_TYPE_INTRA and only intraprediction (and / or IBC and / or PLT modes) can be allowed for this chroma block.
[00379] 8. In one example, the X split may be allowed for the luma components of this encoding and / or decoding tree node, Petition 870220099106, dated 10 / 26 / 2022, p. 69 / 161 / 123, for example, the node of the luma encoding and / or decoding tree can be further divided into multiple luma child nodes, and each luma child node can be determined in MODE_TYPE_INTER, while only interprediction (and / or IBC mode) can be allowed.
[00380] 9. Alternatively, the chroma component can be further split along with the colocalized luma component, but the mode type can be equal to MODE_TYPE_INTER and only interprediction (and / or IBC mode) can be allowed.
[00381] ii. In one example, intra-chroma MxN blocks may not be allowed in CIIP.
[00382] 1. In one example, CIIP may not be allowed for an encoding and / or decoding block with a dimension equal to (M*subWidthC) x (N*subHeightC) in luma samples.
[00383] a) When CIIP is not allowed, the associated syntax element, such as the CIIP indicator, may not be encoded and / or decoded in the continuous bitstream.
[00384] 2. In one example, the process of combining chroma in CIIP can only be filled with forecasts originating from the inter party.
[00385] a) In one example, only luma intraprediction can be applied to a CIIP-encoded and / or decoded block, while chroma intraprediction may not be applied to a CIIP-encoded and / or decoded block with dimensions equal to (M*subWidthC) x (N*subHeightC) in luma samples.
[00386] 3. In one example, DC prediction can be used for intraprediction of MxN chroma for a CIIP block, as described in item 34(a).
[00387] 4. In one example, CCLM prediction can be used for intraprediction of MxN chroma for a CIIP block, as described in item 34(b). Petition 870220099106, dated 10 / 26 / 2022, pp. 70 / 161 / 123
[00388] Relationship between losslessSizeY and maxCTB / maxTBsize / maxTS size
[00389] 35. The maximum transform size can be signaled and / or inferred in different ways for lossless (and / or near lossless) and lossy encoding and / or decoding.
[00390] a. In one example, the maximum transform size for lossless and / or near-lossless encoding and / or decoding may be referred to by other terms, such as “maximum residual size” or “maximum representation size”, since no transform is involved. In this description, it may be referred to as “maxLosslessTbSizeY”.
[00391] b. In one example, lossless encoding and / or decoding for a block can be referred to as a CU_transquant_bypass_flag for this block is equal to 1.
[00392] c. In one example, near lossless encoding and / or decoding for a block can be referred to as encoding and / or decoding with a QP lower than a given threshold.
[00393] i. In one example, the limit can be indicated in DPS / VPS / SPS / PPS / Grid / Slice / Block Header.
[00394] d. In one example, near lossless encoding and / or decoding for a block can be referred to as encoding and / or decoding with a QP less than a given threshold and transform_skip_flag is equal to 1 for this block.
[00395] i. In one example, the limit can be indicated in DPS / VPS / SPS / PPS / Grid / Slice / Block Header.
[00396] e. A first maximum transform size for lossless and / or near-lossless encoding and / or decoding (e.g., maxLosslessTbSizeY) can be set conditional on a second maximum transform size that can be used for Petition 870220099106, dated 10 / 26 / 2022, page 71 / 161 / 123 lossy encoding and / or decoding, and / or maximum size of the encoding and / or decoding tree unit, and / or maximum size of the ignore transform.
[00397] f. The maximum transform size for lossless and / or near lossless encoding and / or decoding can be signaled at the video unit level, such as a syntax element (SE) in SPS / VPS / PPS / Subfigure / Slice / Grid / Block / CTU / VPDU.
[00398] i. In one example, the SE can be signaled depending on the maximum size of the CTB (e.g., log2_ctu_size_minus5, CtbSizeY, etc.)
[00399] 1. For example, the indicator can be signaled when log2_ctu_size_minus5 is greater than N (such as, N=0).
[00400] ii. In one example, the SE can be flagged depending on the maximum transform size (e.g., sps_max_luma_transform_size_64_flag, MaxTbSize, etc.)
[00401] 1. For example, the SE can be signaled when sps_max_luma_transform_size_64_flag is equal to M (such as, M=1).
[00402] iii. In one example, the SE can be signaled depending on the maximum size of the skip transform (e.g., log2_transform_skip_max_size_minus2, MaxTsSize, etc.)
[00403] 1. For example, SE can be signaled when log2_transform_skip_max_size_minus2 is greater than K (such as, K=3).
[00404] iv. In one example, a delta value between log(maxLosslessTbSizeY) and X can be signaled.
[00405] 1. For example, X can be equal to log2_ctu_size_minus5 2. For example, X could be equal to sps_max_luma_transform_size_64_flag 3. For example, X can be equal to log2_transform_skip_max_size_minus2 Petition 870220099106, dated 10 / 26 / 2022, page 72 / 161 / 123 4. For example, X can be equal to a fixed integer.
[00406] 5. In one example, delta - K can be signed, where K is an integer, such as 1.
[00407] v. In one example, a delta value between maxLosslessTbSizeY and X can be signaled.
[00408] 1. For example, X can be equal to CtbSizeY 2. For example, X can be equal to MaxTbSize 3. For example, X can be equal to MaxTsSize 4. For example, X can be equal to a fixed integer.
[00409] 5. In one example, delta - K can be signed, where K is an integer, such as 1.
[00410] vi. In one example, maxLosslessTbSizeY of a video unit (such as a sequence / figure / subfigure / slice / grid / CTU / VPDU / CU / PU / TU) can be derived from the SE.
[00411] vii. SE can be an indicator.
[00412] viii. When the indicator is not present, it can be inferred to be equal to a positive integer N.
[00413] g. In one example, if lossless and / or nearly lossless encoding and / or decoding is applied to a video unit (such as cu_transquant_bypass_flag is equal to 1), the maximum transform size for the video unit can be set equal to maxLosslessTbSizeY, different from maxTbSizeY.
[00414] h. Alternatively, the maximum transform size for lossless and / or near-lossless encoding and / or decoding for a video unit (such as a sequence / figure / subfigure / slice / grid / CTU / VPDU / CU / PU / TU) can be derived instead of being signaled.
[00415] i. For example, the same can be set equal to a value Petition 870220099106, dated 10 / 26 / 2022, page 73 / 161 / 123 fixed integral M (such as M = 32 in luma samples).
[00416] ii. For example, the same can be set equal to a maximum transform size of one second that can be used for lossy encoding and / or decoding,
[00417] iii. For example, it can be set equal to the maximum unit size of the encoding and / or decoding tree,
[00418] iv. For example, it can be adjusted to match the size of the VPDU,
[00419] v. For example, the same can be set equal to the maximum size of the block transformation ignore.
[00420] vi. For example, it can be set equal to the maximum residual size of the encoding and / or decoding block.
[00421] 36. For a residue block MxN by lossless encoding and / or decoding (and / or near lossless encoding and / or decoding), it can be divided into more than one of the smallest residue subblocks, depending on maxLosslessTbSizeY.
[00422] a. After the split, the width and height of all subblocks are no greater than maxLosslessTbSizeY.
[00423] b. In one example, it can be divided into sub-blocks in a recursive manner until the width and height of all sub-blocks are no greater than maxLosslessTbSizeY. Related unlocking
[00424] 37. Palette mode can be enabled in MODE_TYPE_ALL or MODE_TYPE_INTRA, but is always disabled in MODE_TYPE_INTER.
[00425] 38. Unblocking filtering strength (bS) for chroma components can be set to 0 when one side is in IBC mode and the other side is in palette mode.
[00426] a. In one example, bS for the chroma components, when Petition 870220099106, dated 10 / 26 / 2022, p. 74 / 161 / 123 ChromaArrayType is not equal to 0; it is set to 0 when one side is in IBC mode and the other side is in palette mode.
[00427] Minimum QP allowed for blocks to ignore related transform
[00428] 39. The syntax element, for example internal_minus_input_bit_depth shown in JVET-R0045, from which the input bit depth can be inferred, can be limited according to a certain profile.
[00429] a. In one example, (QpPrimeTsMin - 4) / 6 can be limited to being in the range of [0, 2] in a 10-bit profile.
[00430] b. In one example, (QpPrimeTsMin - 4) / 6 can be limited to 0 in an 8-bit profile.
[00431] c. In one example, (QpPrimeTsMin - 4) / 6 can be limited to be in [0, K] in a (K+8)-bit profile.
[00432] d. In one example, (QpPrimeTsMin - 4) / 6 can be limited to be in [0, K] in a (K+8)-bit profile.
[00433] 40. The minimum allowed QP, for example, QpPrimeTsMin, may be limited according to a certain profile.
[00434] a. In one example, (QpPrimeTsMin - 4) / 6 can be limited to being in the range of [0, 2] in a 10-bit profile.
[00435] b. In one example, (QpPrimeTsMin - 4) / 6 can be limited to 0 in an 8-bit profile.
[00436] c. In one example, (QpPrimeTsMin - 4) / 6 can be limited to be in [0, K] in a (K+8)-bit profile.
[00437] d. In one example, (QpPrimeTsMin - 4) / 6 can be limited to be in [0, K] in a (K+8)-bit profile. 5. Modalities Newly added parts are marked in bold and italics, and deleted parts of the VVC working outline are marked with square brackets. Petition 870220099106, dated 10 / 26 / 2022, page 75 / 161 / 123 doubles (e.g., [[a]] denotes the deletion of the character “a”). The modifications are based on the latest VVC working draft (JVETO2001-v11). 5.1 An example modality no. 1 The following modality concerns restrictions on small block partitions, and prediction modes are applied to 4:2:0 and 4:4:4 chroma formats only (they do not apply to 4:0:0 and 4:4:4 chroma formats). 7.4.9.4 Encoding and / or decoding tree semantics
[00438] The modeTypeCondition variable is derived as follows: If one of the following conditions is true, modeTypeCondition is set to 0. - slice_type = = I and qtbtt_dual_tree_intra_flag equals 1 - modeTypeCurr is not equal to MODE_TYPE_ALL - chroma_format_idc equals 0 - chroma_format_idc equals 3 - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1. - cbWidth * cbHeight equals 64 and split_qt_flag equals 1 - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth * cbHeight equals 32 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1 + (slice_type != I ? 1 : 0) - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - cbWidth * cbHeight equals 128 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - In other circumstances, modeTypeCondition is adjusted. Petition 870220099106, dated 10 / 26 / 2022, p. 76 / 161 / 123 equals 0 5.2 An example modality no. 2 The following method is about signaling the palette mode indicator that does not depend on modeType. 7.3.8.5 Syntax of the encoding and / or decoding unit coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeType, modeType ) { Descritor chType = treeType = = DUAL_TREE_CHROMA? 1 : 0 se( slice_type != I | | sps_ibc_enabled_flag | | sps_palette_enabled_flag) { se( treeType != DUAL_TREE_CHROMA && !( ( ( cbWidth = = 4 && cbHeight = = 4 ) | | modeType = = MODE_TYPE_INTRA ) && !sps_ibc_enabled_flag ) ) cu_skip_flag[ x0 ][ y0 ] ae(v) se( cu_skip_flag[ x0 ][ y0 ] = = 0 && slice_type != I && !( cbWidth = = 4 && cbHeight = = 4 ) && modeType = = MODE_TYPE_ALL ) pred_mode_flag ae(v) se( ( ( slice_type = = I && cu_skip_flag[ x0 ][ y0 ] = =0 ) 11 ( slice_type != I && ( CuPredMode[ chType ][ x0 ][ y0 ] != MODE_INTRA 11 ( cbWidth = = 4 && cbHeight = = 4 && cu_skip_flag[ x0 ][ y0 ] = = 0 ) ) ) ) && cbWidth <= 64 && cbHeight <= 64 && modeType != MODE_TYPE_INTER && sps_ibc_enabled_flag && treeType != DUAL_TREE_CHROMA ) pred_mode_ibc_flag ae(v) se( ( ( ( slice_type = = I | | ( cbWidth = = 4 && cbHeight = = 4 ) | | sps_ibc_enabled_flag ) && CuPredMode[ x0 ][y0 ] = = MODE_INTRA ) 11 ( slice_type != I && !( cbWidth = = 4 && cbHeight = = 4 ) && !sps_ibc_enabled_flag && CuPredMode[ x0 ][ y0 ] != MODE_INTRA ) ) && sps_palette_enabled_flag && cbWidth <= 64 && cbHeight <= 64 && && cu_skip_flag[ x0 ][ y0 ] = = 0 [[&& modeType != MODE_INTER ]]) pred_mode_plt_flag ae(v) 5.3 An example modality no. 3 The following section refers to the IBC forecast mode indicator, which is inferred depending on the CU SKIP indicator and the modeType.
[00439] pred_mode_ibc_flag equal to 1 specifies that the current encoding and / or decoding unit is encoded and / or decoded in IBC prediction mode. pred_mode_ibc_flag equal to 0 specifies that the current encoding and / or decoding unit is not encoded and / or decoded in IBC prediction mode. Petition 870220099106, dated 10 / 26 / 2022, p. 77 / 161 / 123
[00440] When pred_mode_ibc_flag is not present, it is inferred as follows: - If cu_skip_flag[ x0 ][ y0 ] equals 1, and cbWidth equals 4, and cbHeight equals 4, pred_mode_ibc_flag is inferred to be equal to 1.
[00441] - In other circumstances, if both cbWidth and cbHeight equal 128, pred_mode_ibc_flag is inferred to be equal to 0.
[00442] - [[ In other circumstances, if cu_skip_flag[ x0 ][ y0 ] equals 1, and modeType equals MODE_TYPE_INTRA, pred_mode_ibc_flag is inferred to be equal to 1.]]
[00443] - In other circumstances, if modeType is equal to MODE_TYPE_INTER, pred_mode_ibc_flag is inferred to be equal to 0.
[00444] - In other circumstances, if treeType is equal to DUAL_TREE_CHROMA, pred_mode_ibc_flag is inferred to be equal to 0.
[00445] - In other circumstances, pred_mode_ibc_flag is inferred to be equal to the value of sps_ibc_enabled_flag during the decoding of an I slice, and 0 during the decoding of a P or B slice, respectively.
[00446] When pred_mode_ibc_flag is equal to 1, the variable CuPredMode[ chType ][ x ][ y ] is set to be equal to MODE_IBC for x = x0..x0 + cbWidth - 1 and y = y0..y0 + cbHeight - 1. 5.4 An example modality no. 4 The following modality concerns the IBC forecast mode signaling indicator that depends on MODE_TYPE_INTRA, and / or the IBC mode that is enabled for luma blocks regardless of whether they have a small block size. 7.3.8.5 Syntax of the encoding and / or decoding unit coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeType, modeType ) { Descriptor chType = treeType = = DUAL_TREE_CHROMA? 1 : 0 if( slice_type != I 1 1 sps_ibc_enabled_flag 1 1 sps_palette_enabled_flag) { if( treeType != DUAL_TREE_CHROMA && !( ( ( cbWidth = = 4 && cbHeight = = 4 ) 1 1 modeType = = MODE_TYPE_INTRA ) && !sps_ibc_enabled_flag ) ) cu_skip_flag[ x0 ][ y0 ] ae(v) Petition 870220099106, dated 10 / 26 / 2022, p. 78 / 161 / 123 if( cu_skip_flag[ x0 ][ y0 ] = = 0 && slice_type != I && !( cbWidth = = 4 && cbHeight = = 4 ) && modeType = = MODE_TYPE_ALL ) pred_mode_flag ae(v) if( ( ( slice_type = = I && cu_skip_flag[ x0 ][ y0 ] = =0 ) 1 1 ( slice_type != I && ( CuPredMode[ chType ][ x0 ][ y0 ] != MODE_INTRA 1 1 ( modeType = = MODE_TYPE_INTRA && cu_skip_lag[ x0 ][y0 ] == 0 ) 1 1 ( cbWidth = = 4 && cbHeight = = 4 && cu_skip_flag[ x0 ][ y0 ] = = 0 ) ) ) ) && cbWidth <= 64 && cbHeight <= 64 && modeType != MODE_TYPE_INTER && sps_ibc_enabled_flag && treeType != DUAL_TREE_CHROMA ) pred_mode_ibc_flag ae(v) 5.5 An example modality no. 5 The following section is about applying different intra-block constraints to 4:2:0 and 4:2:2 color formats. 7.4.9.4 Encoding and / or decoding tree semantics
[00447] The modeTypeCondition variable is derived as follows: If one of the following conditions is true, modeTypeCondition is set to 0. - slice_type = = I and qtbtt_dual_tree_intra_flag equals 1 - modeTypeCurr is not equal to MODE_TYPE_ALL - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1. - cbWidth * cbHeight equals 64 and split_qt_flag equals 1 - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth * cbHeight equals 32 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1 + (slice_type != I ? 1 : 0) - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER and chroma _format_idc equals 1 - cbWidth * cbHeight equals 128 and MttSplitMode[ x0 ][ y0 Petition 870220099106, dated 10 / 26 / 2022, page. 79 / 161 / 123 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER and chroma_format_idc equals 1 — cbWidth equals 8 and cbHeight equals 8 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_VER and chroma_format_idc equals 2 — cbWidth equals 4 and cbHeight equals 16 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR and chroma_format_idc equals 2 — cbWidth equals 16 and cbHeight equals 8 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_VER and chroma_format_idc are equal to 2 — cbWidth is equal to 4 and cbHeight is equal to 32 and MttSplitMode[x0][y0][mttDepth] is equal to SPLIT_TT_HOR and chroma_format_idc is equal to 2 — In other circumstances, modeTypeCondition is set equal to 0 5.6 An example modality no. 6 The following approach is about disallowing intra-chroma 2xN blocks in an individual tree. 7.4.9.4 Encoding and / or decoding tree semantics
[00448] The modeTypeCondition variable is derived as follows: — If one of the following conditions is true, modeTypeCondition is set to 0 — slice_type == I and qtbtt_dual_tree_intra_flag is equal to 1 — modeTypeCurr is not equal to MODE_TYPE_ALL — In other circumstances, if one of the following conditions is true, modeTypeCondition is set to 1 — cbWidth * cbHeight is equal to 64 and split_qt_flag is equal to 1 — cbWidth * cbHeight is equal to 64 and MttSplitMode[ x0 ][ y0 ][ Petition 870220099106, dated 10 / 26 / 2022, p. 80 / 161 / 123 mttDepth ] is equal to SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth * cbHeight equals 32 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1 + (slice_type != I ? 1 : 0) - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - cbWidth * cbHeight equals 128 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth equals 8 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_VER - cbWidth equals 16 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_VER - In other circumstances, modeTypeCondition is set to 0. 5.7 An example modality no. 7 The following modality is about disallowing intra-chroma 2xN blocks in a dual tree. 6.4.2 Allowed binary division process
[00449] The allowBtSplit variable is derived as follows: If one or more of the following conditions are true, allowBtSplit is set to FALSE: - cbSize is less than or equal to MinBtSizeY - cbWidth is greater than maxBtSize - cbHeight is greater than maxBtSize - mttDepth is greater than or equal to maxMttDepth - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 16 - btSplit equals SPLIT_BT_VER and treeType equals Petition 870220099106, dated 10 / 26 / 2022, page 81 / 161 / 123 DUAL_TREE_CHROMA and (cbWidth / SubWidthC) is less than or equal to 4 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA 6.4.3 Allowed ternary division process
[00450] The allowTtSplit variable is derived as follows: If one or more of the following conditions are true, allowTtSplit is set to FALSE: - cbSize is less than or equal to 2 * MinTtSizeY - cbWidth is greater than Min( MaxTbSizeY, maxTtSize ) - cbHeight is greater than Min( MaxTbSizeY, maxTtSize ) - mttDepth is greater than or equal to maxMttDepth - x0 + cbWidth is greater than pic_width_in_luma_samples - y0 + cbHeight is greater than pic_height_in_luma_samples - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 32 - btSplit equals SPLIT_TT_VER and treeType equals DUAL_TREE_CHROMA and (cbWidth / SubWidthC) is less than or equal to 8 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA - In other circumstances, allowTtSplit is set equal to TRUE. 5.8 An example modality no. 8 The following modality is about activating MODE_IBC for SCIPU chroma blocks. 7.3.8.5 Syntax of the encoding and / or decoding unit ________ coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeType, modeType ) { Descritor chType = treeType = = DUAL_TREE_CHROMA? 1 : 0 se( slice_type != I 1 1 sps_ibc_enabled_flag 1 1 sps_palette_enabled_flag) { Petição 870220099106, de 26 / 10 / 2022, pág. 82 / 161 / 123 se( treeType != DUAL_TREE_CHROMA && !( ( ( cbWidth = = 4 && cbHeight = = 4 ) 1 1 modeType = = MODE_TYPE_INTRA ) && !sps_ibc_enabled_flag ) ) cu_skip_flag[ x0 ][ y0 ] ae(v) se( cu_skip_flag[ x0 ][ y0 ] = = 0 && slice_type != I && !( cbWidth = = 4 && cbHeight = = 4 ) && modeType = = MODE_TYPE_ALL ) pred_mode_flag ae(v) se( ( ( slice_type = = I && cu_skip_flag[ x0 ][ y0 ] = =0 ) 1 1 ( slice_type != I && ( CuPredMode[ chType ][ x0 ][ y0 ] != MODE_INTRA 1 1 ( modeType = = MODE_TYPE_INTRA && cu_skip_flag[ x0 ][ y0 ] == 0 ) 1 1 ( cbWidth = = 4 && cbHeight = = 4 && cu_skip_flag[ x0 ][ y0 ] = = 0 ) ) ) ) && cbWidth <= 64 && cbHeight <= 64 && modeType != MODE_TYPE_INTER && sps_ibc_enabled_flag && '(modeType == MODE_TYPE_ALL && treeType == DUAL_TREE_CHROMA) [[treeType != DUAL_TREE_CHROMA)]] pred_mode_ibc_flag ae(v) 5.9 Uma modalidade de exemplo n° 9 sobre desautorizar a partição de bloco quando modeType for MODE_TYPE_INTER (solução 1) 6.4.2 Allowed binary division process
[00451] The allowBtSplit variable is derived as follows: If one or more of the following conditions are true, allowBtSplit is set to FALSE: - cbSize is less than or equal to MinBtSizeY - cbWidth is greater than maxBtSize - cbHeight is greater than maxBtSize - mttDepth is greater than or equal to maxMttDepth - treeType is equal to DUAL_TREE_CHROMA and ( cbWidth / If (SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 16 - modeType equals MODE_TYPE_INTER and cbWidth * cbHeight is less than or equal to 32 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA 6.4.3 Allowed ternary division process
[00452] The allowTtSplit variable is derived as follows: Petition 870220099106, dated 10 / 26 / 2022, page 83 / 161 / 123 If one or more of the following conditions are true, allowTtSplit is set to FALSE: - cbSize is less than or equal to 2 * MinTtSizeY - cbWidth is greater than Min( MaxTbSizeY, maxTtSize ) - cbHeight is greater than Min( MaxTbSizeY, maxTtSize ) - mttDepth is greater than or equal to maxMttDepth - x0 + cbWidth is greater than pic_width_in_luma_samples - y0 + cbHeight is greater than pic_height_in_luma_samples - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 32 - modeType equals MODE_TYPE_INTER and cbWidth * cbHeight is less than or equal to 64 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA - In other circumstances, allowTtSplit is set to TRUE. 5.10 Example 10 on disallowing block partitioning when modeType is MODE_TYPE_INTER (solution 2) 6.4.2 Allowed binary division process
[00453] The allowBtSplit variable is derived as follows: If one or more of the following conditions are true, allowBtSplit is set to FALSE: - cbSize is less than or equal to MinBtSizeY - cbWidth is greater than maxBtSize - cbHeight is greater than maxBtSize - mttDepth is greater than or equal to maxMttDepth - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 16 - modeType is equal to MODE_TYPE_INTER Petition 870220099106, dated 10 / 26 / 2022, page 84 / 161 / 123 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA 6.4.3 Allowed ternary division process
[00454] The allowTtSplit variable is derived as follows: If one or more of the following conditions are true, allowTtSplit is set to FALSE: - cbSize is less than or equal to 2 * MinTtSizeY - cbWidth is greater than Min( MaxTbSizeY, maxTtSize ) - cbHeight is greater than Min( MaxTbSizeY, maxTtSize ) - mttDepth is greater than or equal to maxMttDepth - x0 + cbWidth is greater than pic_width_in_luma_samples - y0 + cbHeight is greater than pic_height_in_luma_samples - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 32 - modeType is equal to MODE_TYPE_INTER - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA - In other circumstances, allowTtSplit is set to TRUE. 5.11 An example modality no. 11 The following modality concerns the additional restrictions on splitting an encoding and / or decoding tree when MODE_TYPE_INTER is derived. 7.3.8.4 Syntax of the encoding and / or decoding tree _______ coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, depthOffset, partIdx, treeTypeCurr, modeTypeCurr ) { Descriptor ... treeType = ( modeType = = MODE_TYPE_INTRA ) ? DUAL_TREE_LUMA : treeTypeCurr if ( modeType = = MODE_TYPE_INTER ) mttDepth = max( mttDepth, maxMttDepth -1) Petition 870220099106, dated 10 / 26 / 2022, p. 85 / 161 / 123 if( !split_qt_flag ) { 5.12 An example modality no. 12 The following section is about restrictions on small block partitions, and prediction modes are not applied when palette mode is enabled. 7.4.9.4 Encoding and / or decoding tree semantics
[00455] The modeTypeCondition variable is derived as follows: If one of the following conditions is true, modeTypeCondition is set to 0. - slice_type = = I and qtbtt_dual_tree_intra_flag equals 1 - modeTypeCurr is not equal to MODE_TYPE_ALL - sps_palette_enabled_flag is equal to 1 - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1. - cbWidth * cbHeight equals 64 and split_qt_flag equals 1 - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth * cbHeight equals 32 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1 + (slice_type != I ? 1 : 0) - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - cbWidth * cbHeight equals 128 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - In other circumstances, modeTypeCondition is set to 0 - 5.13 An example modality no. 13 The following section concerns small block intrachromatic restrictions. Petition 870220099106, dated 10 / 26 / 2022, p. 86 / 161 / 123 for 4:2:2 color formats. 7.4.9.4 Encoding and / or decoding tree semantics
[00456] The modeTypeCondition variable is derived as follows: If one of the following conditions is true, modeTypeCondition is set to 0. - slice_type = = I and qtbtt_dual_tree_intra_flag equals 1 - modeTypeCurr is not equal to MODE_TYPE_ALL - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1. - cbWidth * cbHeight equals 64 and split_qt_flag equals 1 - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth * cbHeight equals 32 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - In other circumstances, if chroma_format_idc equals 1 and one of the following conditions is true, modeTypeCondition is set equal to 1 + (slice_type != I ? 1 : 0) - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - cbWidth * cbHeight equals 128 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - In other circumstances, modeTypeCondition is set to 0. 5.14 Example #1 of delta QP signaling in SCIPU coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, depthOffset, partIdx, treeTypeCurr, modeTypeCurr ) { Described r if( ( allowSplitBtVer 1 1 allowSplitBtHor 1 1 allowSplitTtVer 1 1 allowSplitTtHor 1 1 allowSplitQT ) &&( x0 + cbWidth <= pic_width_in_luma_samples ) && (y0 + cbHeight <= pic_heigth_in_luma_samples ) ) split_cu_flag ae(v) if( cu_qp_delta_enabled_flag && qgOnY && cbSubdiv <= cu_qp_delta_subdiv ) { IsCuQpDeltaCoded = 0 CuQpDeltaVal = 0 CuQgTopLeftX = x0 Petition 870220099106, dated 10 / 26 / 2022, p. 87 / 161 / 123 CuQgTopLeftY = y0} se( cu_chroma_qp_offset_enabled_flag && qgOnC && cbSubdiv <= cu_chroma_qp_offset_subdiv ) IsCuChromaQpOffsetCoded = 0 se( split_cu_flag ) { se( ( allowSplitBtVer | | allowSplitBtHor | | allowSplitTtVer | | allowSplitTtHor ) && allowSplitQT ) split_qt_flag ae(v) se( !split_qt_flag ) { se( ( allowSplitBtHor | | allowSplitTtHor ) && ( allowSplitBtVer 11 allowSplitTtVer ) ) mtt_split_cu_vertical_flag ae(v) se( ( allowSplitBtVer && allowSplitTtVer && mtt_split_cu_vertical_flag ) | | ( allowSplitBtHor && allowSplitTtHor && !mtt_split_cu_vertical_flag ) ) mtt_split_cu_binary_flag ae(v)} se( modeTypeCondition = = 1 ) modeType = MODE_TYPE_INTRA se não se( modeTypeCondition = = 2 ) { mode_constraint_flag ae(v) modeType = mode_constraint_flag ? MODE_TYPE_INTRA : MODE_TYPE_INTER} se não { modeType = modeTypeCurr} treeType = ( modeType = = MODE_TYPE_INTRA ) ? DUAL_TREE_LUMA : treeTypeCurr se( !split_qt_flag ) { se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_VER ) {depthOffset += ( x0 + cbWidth > pic_width_in_luma_samples ) ? 1 : 0 x1 = x0 + ( cbWidth / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeightY, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_HOR ) { depthOffset += ( y0 + cbHeight > pic_heigth_in_luma_samples ) ? 1 : 0 y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_TT_VER ) { x1 = x0 + ( cbWidth / 4 ) x2 = x0 + ( 3 * cbWidth / 4 )qgOnYnext = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnCnext = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( x0, y0, cbWidth / 4, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) coding_tree( x1, y0, cbWidth / 2, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) Petition 870220099106, dated 10 / 26 / 2022, p. 88 / 161 / 123 coding_tree( x2, y0, cbWidth / 4, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )} se não { / * SPLIT_TT_HOR * / y1 = y0 + ( cbHeight / 4 ) y2 = y0 + ( 3 * cbHeight / 4 ) qgOnYnext = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnCnext = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( x0, y0, cbWidth, cbHeight / 4, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnYnext, qgOnCnext, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) coding_tree( x0, y2, cbWidth, cbHeight / 4, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )}} se não { x1 = x0 + ( cbWidth / 2 ) y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 0, treeType,modeType ) se( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 1, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 2, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples && x1 < pic_width_in_luma_samples ) coding_tree( x1, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 3, treeType, modeType )} se( modeTypeCur = = MODE_TYPE_ALL && modeType = = MODE_TYPE_INTRA ) { coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, 0, 0 DUAL_TREE_CHROMA , modeType )}} se não coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeTypeCurr , modeTypeCurr )}, 5.15 Exemplo n° 2 da sinalização de delta QP em SCIPU coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, depthOffset, partIdx, treeTypeCurr, modeTypeCurr ) { Descritor se( ( allowSplitBtVer | | allowSplitBtHor | | allowSplitTtVer | | allowSplitTtHor | | allowSplitQT ) &&( x0 + cbWidth <= pic_width_in_luma_samples ) && (y0 + cbHeight <= pic_heigth_in_luma_samples ) ) split_cu_flag ae(v) se( cu_qp_delta_enabled_flag && qgOnY && cbSubdiv <= cu_qp_delta_subdiv ) { IsCuQpDeltaCoded = 0 CuQpDeltaVal = 0 CuQgTopLeftX = x0 CuQgTopLeftY = y0} Petição 870220099106, de 26 / 10 / 2022, pág. 89 / 161 / 123 se( cu_chroma_qp_offset_enabled_flag && qgOnC && cbSubdiv <= cu_chroma_qp_offset_subdiv ) IsCuChromaQpOffsetCoded = 0 se( split_cu_flag ) { se( ( allowSplitBtVer | | allowSplitBtHor | | allowSplitTtVer | | allowSplitTtHor ) && allowSplitQT ) split_qt_flag ae(v) se( !split_qt_flag ) { se( ( allowSplitBtHor | | allowSplitTtHor ) && ( allowSplitBtVer 11 allowSplitTtVer ) ) mtt_split_cu_vertical_flag ae(v) se( ( allowSplitBtVer && allowSplitTtVer && mtt_split_cu_vertical_flag ) | | ( allowSplitBtHor && allowSplitTtHor && !mtt_split_cu_vertical_flag ) ) mtt_split_cu_binary_flag ae(v)} se( modeTypeCondition = = 1 ) modeType = MODE_TYPE_INTRA se não se( modeTypeCondition = = 2 ) { mode_constraint_flag ae(v) modeType = mode_constraint_flag ? MODE_TYPE_INTRA : MODE_TYPE_INTER} se não { modeType = modeTypeCurr} treeType = ( modeType = = MODE_TYPE_INTRA ) ? DUAL_TREE_LUMA : treeTypeCurr se( !split_qt_flag ) { se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_VER ) { depthOffset += ( x0 +cbWidth > pic_width_in_luma_samples ) ? 1 : 0 x1 = x0 + ( cbWidth / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeightY, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_HOR ) { depthOffset += ( y0 + cbHeight > pic_heigth_in_luma_samples ) ? 1 : 0 y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_TT_VER ) { x1 = x0 + ( cbWidth / 4 ) x2 = x0 + ( 3 * cbWidth / 4 ) qgOnYnext = qgOnY && (cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnCnext = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( x0, y0, cbWidth / 4, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) coding_tree( x1, y0, cbWidth / 2, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) coding_tree( x2, y0, cbWidth / 4, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType ) Petição 870220099106, de 26 / 10 / 2022, pág. 90 / 161 85 / 123 } se não { / * SPLIT_TT_HOR * / yl = yO + (cbHeight / 4) y2 = yO + ( 3 * cbHeight / 4) qgOnYnext = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv) qgOnCnext = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( xO, yO, cbWidth, cbHeight / 4, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthoffset, 0, treeType, modeType) coding_tree( xO, yl, cbWidth, cbHeight / 2, qgOnYnext, qgOnCnext, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthoffset, 1, treeType, modeType) coding_tree( xO, y2, cbWidth, cbHeight / 4, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthoffset, 2, treeType, modeType) ]} se não { xl = xO + ( cbWidth / 2 ) yl = yO + (cbHeight / 2) coding_tree( xO, yO, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 0, treeType, modeType) se( xl < pic_width_in_luma_samples) coding_tree( xl, yO, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 1, treeType,modeType) se( yl < pic_heigth_in_luma_samples) coding_tree( xO, yl, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 2, treeType, modeType) se( yl < pic_heigth_in_luma_samples && xl < pic_width_in_luma_samples) coding_tree( xl, yl, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 3, treeType, modeType) ] se( modeTypeCur = = MODE_TYPE_ALL && modeType = = MODE_TYPE_INTRA) { coding_tree( xO, yO, cbWidth, cbHeight, qgOnY, 0, cbSubdiv, cqtDepth, mttDepth, 0, 0 DUAL_TREE_CHROMA , modeType) ]} se não coding_unit( xO, yO, cbWidth, cbHeight, cqtDepth, treeTypeCurr, modeTypeCurr)}, 5.16 Exemplo ηθ 3 da sinalização de delta QP em SCIPU coding_tree( xO, yO, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, depthoffset, partldx, treeTypeCurr, modeTypeCurr) { Descritor se( (allowSplitBtVer 11 allowSplitBtHor 11 allowSplitTtVer 11 allowSplitTtHor 11 allowSplitQT) &&( xO + cbWidth <= pic_width_in_luma_samples) && (yO + cbHeight <= pic_heigth_in_luma_samples)) split_cu_flag ae(v) se( cu_qp_delta_enabled_flag && qgOnY && cbSubdiv <= cu_qp_delta_subdiv && treeTypeCurr != DUAL_TREE_CHROMA ) { IsCuQpDeltaCoded = 0 CuQpDeltaVal = 0 CuQgTopLeftX = xO CuQgTopLeftY = yO} Petição 870220099106, de 26 / 10 / 2022, pág. 91 / 161 / 123 se( cu_chroma_qp_offset_enabled_flag && qgOnC && cbSubdiv <= cu_chroma_qp_offset_subdiv && && treeTypeCurr != DUAL_TREE_LUMA ) IsCuChromaQpOffsetCoded = 0 se( split_cu_flag ) { se( ( allowSplitBtVer | | allowSplitBtHor | | allowSplitTtVer | | allowSplitTtHor ) && allowSplitQT ) split_qt_flag ae(v) se( !split_qt_flag ) { se( ( allowSplitBtHor | | allowSplitTtHor ) && ( allowSplitBtVer 11 allowSplitTtVer ) ) mtt_split_cu_vertical_flag ae(v) se( ( allowSplitBtVer && allowSplitTtVer && mtt_split_cu_vertical_flag ) | | ( allowSplitBtHor && allowSplitTtHor && !mtt_split_cu_vertical_flag ) ) mtt_split_cu_binary_flag ae(v)} se( modeTypeCondition = = 1 ) modeType = MODE_TYPE_INTRA se não se( modeTypeCondition = = 2 ) { mode_constraint_flag ae(v) modeType = mode_constraint_flag ? MODE_TYPE_INTRA : MODE_TYPE_INTER} se não { modeType = modeTypeCurr} treeType = ( modeType = = MODE_TYPE_INTRA ) ? DUAL_TREE_LUMA : treeTypeCurr se( !split_qt_flag ) { se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = =SPLIT_BT_VER ) { depthOffset += ( x0 + cbWidth > pic_width_in_luma_samples ) ? 1 : 0 x1 = x0 + ( cbWidth / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeightY, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_HOR ) { depthOffset += ( y0 + cbHeight > pic_heigth_in_luma_samples ) ? 1 : 0 y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_TT_VER ) { x1 = x0 + ( cbWidth / 4 ) x2 = x0 + ( 3 *cbWidth / 4 ) qgOnYnext = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnCnext = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv) coding_tree( x0, y0, cbWidth / 4, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) coding_tree( x1, y0, cbWidth / 2, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) Petition 870220099106, dated 10 / 26 / 2022, pp. 92 / 161 / 123 coding_tree( x2, y0, cbWidth / 4, cbHeight, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )} se não { / * SPLIT_TT_HOR * / y1 = y0 + ( cbHeight / 4 ) y2 = y0 + ( 3 * cbHeight / 4 ) qgOnYnext = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnCnext = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( x0, y0, cbWidth, cbHeight / 4, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnYnext, qgOnCnext, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) coding_tree( x0, y2, cbWidth, cbHeight / 4, qgOnYnext, qgOnCnext, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )}} se não { x1 = x0 + ( cbWidth / 2 ) y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 0, treeType,modeType ) se( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 1, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 2, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples && x1 < pic_width_in_luma_samples ) coding_tree( x1, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 3, treeType, modeType )} se( modeTypeCur = = MODE_TYPE_ALL && modeType = = MODE_TYPE_INTRA ) { coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, 0, cbSubdiv, cqtDepth, mttDepth, 0, 0 DUAL_TREE_CHROMA , modeType )}} se não coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeTypeCurr , modeTypeCurr )}, 5.17 Exemplo n° 4 da sinalização de delta QP em SCIPU coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, depthOffset, partIdx, treeTypeCurr, modeTypeCurr ) { Descritor se( ( allowSplitBtVer | | allowSplitBtHor | | allowSplitTtVer | | allowSplitTtHor | | allowSplitQT ) &&( x0 + cbWidth <= pic_width_in_luma_samples ) && (y0 + cbHeight <= pic_heigth_in_luma_samples ) ) split_cu_flag ae(v) se( cu_qp_delta_enabled_flag && qgOnY && cbSubdiv <= cu_qp_delta_subdiv ) { IsCuQpDeltaCoded = 0 CuQpDeltaVal = 0 CuQgTopLeftX = x0 Petição 870220099106, de 26 / 10 / 2022, pág. 93 / 161 / 123 CuQgTopLeftY = y0} se( cu_chroma_qp_offset_enabled_flag && qgOnC && cbSubdiv <= cu_chroma_qp_offset_subdiv ) IsCuChromaQpOffsetCoded = 0 se( split_cu_flag ) { se( ( allowSplitBtVer | | allowSplitBtHor | | allowSplitTtVer | | allowSplitTtHor ) && allowSplitQT ) split_qt_flag ae(v) se( !split_qt_flag ) { se( ( allowSplitBtHor | | allowSplitTtHor ) && ( allowSplitBtVer 11 allowSplitTtVer ) ) mtt_split_cu_vertical_flag ae(v) se( ( allowSplitBtVer && allowSplitTtVer && mtt_split_cu_vertical_flag ) | | ( allowSplitBtHor && allowSplitTtHor && !mtt_split_cu_vertical_flag ) ) mtt_split_cu_binary_flag ae(v)} se( modeTypeCondition = = 1 ) modeType = MODE_TYPE_INTRA se não se( modeTypeCondition = = 2 ) { mode_constraint_flag ae(v) modeType = mode_constraint_flag ? MODE_TYPE_INTRA : MODE_TYPE_INTER} se não { modeType = modeTypeCurr} se(modeTypeCondition > 0) qgOnY = qgOnC = 0 treeType = ( modeType = = MODE_TYPE_INTRA ) ? DUAL_TREE_LUMA : treeTypeCurr se( !split_qt_flag ) { se( MttSplitMode[ x0][ y0 ][ mttDepth ] = = SPLIT_BT_VER ) { depthOffset += ( x0 + cbWidth > pic_width_in_luma_samples ) ? 1 : 0 x1 = x0 + ( cbWidth / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeightY, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_BT_HOR ) { depthOffset += ( y0 + cbHeight > pic_heigth_in_luma_samples ) ? 1 : 0 y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) se( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType )} se não se( MttSplitMode[ x0 ][ y0 ][ mttDepth ] = = SPLIT_TT_VER ) { x1 = x0 + (cbWidth / 4 ) x2 = x0 + ( 3 * cbWidth / 4 ) qgOnY = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnC = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree ( cbHeight, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) Petition 870220099106, dated 10 / 26 / 2022, pp. 94 / 161 / 123 coding_tree( x1, y0, cbWidth / 2, cbHeight, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) coding_tree( x2, y0, cbWidth / 4, cbHeight, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )} se não { / * SPLIT_TT_HOR * / y1 = y0 + ( cbHeight / 4 ) y2 = y0 + ( 3 * cbHeight / 4 ) qgOnY = qgOnY && ( cbSubdiv + 2 <= cu_qp_delta_subdiv ) qgOnC = qgOnC && ( cbSubdiv + 2 <= cu_chroma_qp_offset_subdiv ) coding_tree( x0, y0, cbWidth, cbHeight / 4, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 0, treeType, modeType ) coding_tree( x0, y1, cbWidth, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 1, cqtDepth, mttDepth + 1, depthOffset, 1, treeType, modeType ) coding_tree( x0, y2, cbWidth, cbHeight / 4, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth, mttDepth + 1, depthOffset, 2, treeType, modeType )}} se não { x1 = x0 + ( cbWidth / 2 ) y1 = y0 + ( cbHeight / 2 ) coding_tree( x0, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC,cbSubdiv + 2, cqtDepth + 1, 0, 0, 0, treeType, modeType ) if( x1 < pic_width_in_luma_samples ) coding_tree( x1, y0, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 1, treeType, modeType ) if( y1 < pic_heigth_in_luma_samples ) coding_tree( x0, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 2, treeType, modeType ) if( y1 < pic_height_in_luma_samples && x1 < pic_width_in_luma_samples ) coding_tree( x1, y1, cbWidth / 2, cbHeight / 2, qgOnY, qgOnC, cbSubdiv + 2, cqtDepth + 1, 0, 0, 3, treeType, modeType )} if( modeTypeCur = = MODE_TYPE_ALL && modeType = = MODE_TYPE_INTRA ) { coding_tree( x0, y0, cbWidth, cbHeight, qgOnY, qgOnC, cbSubdiv, cqtDepth, mttDepth, 0, 0 DUAL_TREE_CHROMA , modeType )}} if not coding_unit( x0, y0, cbWidth, cbHeight, cqtDepth, treeTypeCurr , modeTypeCurr )}, 5.18 Example #14 of intra-block deactivation of 2x8 chroma 6.4.2. Allowed binary splitting process
[00457] The allowBtSplit variable is derived as follows: If one or more of the following conditions are true, allowBtSplit is set to FALSE: - cbSize is less than or equal to MinBtSizeY Petition 870220099106, dated 10 / 26 / 2022, pp. 95 / 161 / 123 - cbWidth is greater than maxBtSize - cbHeight is greater than maxBtSize - mttDepth is greater than or equal to maxMttDepth - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 16 - treeType equals DUAL_TREE_CHROMA and btSplit equals SPLIT_BT_VER and (cbWidth / SubWidthC) equals 4 and (cbHeight / SubHeightC) equals 8 - treeType equals DUAL_TREE_CHROMA and btSplit equals SPLIT_BT_HOR and (cbWidth / SubWidthC) equals 2 and (cbHeight / SubHeightC) equals 16 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA 6.4.3. Allowed ternary division process
[00458] The allowTtSplit variable is derived as follows: If one or more of the following conditions are true, allowTtSplit is set to FALSE: - cbSize is less than or equal to 2 * MinTtSizeY - cbWidth is greater than Min( MaxTbSizeY, maxTtSize ) - cbHeight is greater than Min( MaxTbSizeY, maxTtSize ) - mttDepth is greater than or equal to maxMttDepth - x0 + cbWidth is greater than pic_width_in_luma_samples - y0 + cbHeight is greater than pic_height_in_luma_samples - treeType is equal to DUAL_TREE_CHROMA and (cbWidth / SubWidthC) * (cbHeight / SubHeightC) is less than or equal to 32 - treeType equals DUAL_TREE_CHROMA and btSplit equals SPLIT_TT_VER and (cbWidth / SubWidthC) equals 8 and (cbHeight / SubHeightC) equals 8 Petition 870220099106, dated 10 / 26 / 2022, pages 96 / 161 / 123 - treeType equals DUAL_TREE_CHROMA and btSplit equals SPLIT_TT_HOR and (cbWidth / SubWidthC) equals 2 and (cbHeight / SubHeightC) equals 32 - treeType equals DUAL_TREE_CHROMA and modeType equals MODE_TYPE_INTRA - In other circumstances, allowTtSplit is set equal to TRUE. 7.4.9.4. Encoding and / or decoding tree semantics
[00459] The modeTypeCondition variable is derived as follows: If one of the following conditions is true, modeTypeCondition is set to 0. - slice_type = = I and qtbtt_dual_tree_intra_flag equals 1 - modeTypeCurr is not equal to MODE_TYPE_ALL - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1. - cbWidth * cbHeight equals 64 and split_qt_flag equals 1 - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth * cbHeight equals 32 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - In other circumstances, if one of the following conditions is true, modeTypeCondition is set equal to 1 + (slice_type != I ? 1 : 0) - cbWidth * cbHeight equals 64 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_BT_HOR or SPLIT_BT_VER - cbWidth * cbHeight equals 128 and MttSplitMode[ x0 ][ y0 ][ mttDepth ] equals SPLIT_TT_HOR or SPLIT_TT_VER - cbWidth equals 8 and (cbHeight / SubHeightC) equals 8 and MttSplitMode[x0][y0][mttDepth] equals SPLIT_BT_VER - cbWidth equals 16 and (cbHeight / SubHeightC) equals Petition 870220099106, dated 10 / 26 / 2022, page 97 / 161 / 123 and MttSplitMode[x0][y0][mttDepth] is equal to SPLIT_TT_VER - cbWidth equals 4 and (cbHeight / SubHeightC) equals 16 and MttSplitMode[x0][y0][mttDepth] equals SPLIT_BT_HOR or SPLIT_TT_HOR - cbWidth equals 4 and (cbHeight / SubHeightC) equals 32 and MttSplitMode[x0][y0][mttDepth] equals SPLIT_TT_HOR - In other circumstances, modeTypeCondition is set to 0. 7.4.9.7. Semantics of merge data
[00460] ciip_flag[ x0 ][ y0 ] specifies whether combined interfigure blending and intrafigure prediction is applied to the current encoding and / or decoding unit. The array indices x0, y0 specify the location ( x0, y0 ) of the top-left luma sample of the considered encoding and / or decoding block relative to the top-left luma sample of the figure.
[00461] When ciip_flag[ x0 ][ y0 ] is not present, the following is inferred: If all of the following conditions are true, ciip_flag[x0][y0] is inferred to be equal to 1: - sps_ciip_enabled_flag is equal to 1. - general_merge_flag[ x0 ][ y0 ] equals 1. - merge_subblock_flag[ x0 ][ y0 ] equals 0. - regular_merge_flag[ x0 ][ y0 ] equals 0. - cbWidth is less than 128. - cbHeight is less than 128. - cbWidth is greater than 4 and cbHeight is not equal to 16. - cbWidth * cbHeight is greater than or equal to 64. - In other circumstances, ciip_flag[ x0 ][ y0 ] is inferred to be equal to 0. Petition 870220099106, dated 10 / 26 / 2022, pp. 98 / 161 / 123 7.3.8.7. Merge data syntax merge_data( x0, y0, cbWidth, cbHeight, chType ) { Descritor se ( CuPredMode[ chType ][ x0 ][ y0 ] = = MODE_IBC ) { se( MaxNumIbcMergeCand > 1 ) merge_idx[ x0 ][ y0 ] ae(v)} se não { se( MaxNumSubblockMergeCand > 0 && cbWidth >= 8 && cbHeight >= 8 ) merge_subblock_flag[ x0 ][ y0 ] ae(v) se( merge_subblock_flag[ x0 ][ y0 ] = = 1 ) { se( MaxNumSubblockMergeCand > 1 ) merge_subblock_idx[ x0 ][ y0 ] ae(v)} se não { se( ( cbWidth * cbHeight ) >= 64 && ( (sps_ciip_enabled_flag && cu_skip_flag[ x0 ][ y0 ] = = 0 && cbWidth < 128 && cbHeight < 128) 11 ( sps_triangle_enabled_flag && MaxNumTriangleMergeCand > 1 && slice_type = = B ) ) ) regular_merge_flag[ x0 ][ y0 ] ae(v) se ( regular_merge_flag[ x0 ][ y0 ] = = 1 ){ se( sps_mmvd_enabled_flag ) mmvd_merge_flag[ x0 ][ y0 ] ae(v) se( mmvd_merge_flag[ x0 ][ y0 ] = = 1 ) { se( MaxNumMergeCand > 1 ) mmvd_cand_flag[ x0 ][ y0 ] ae(v) mmvd_distance_idx[ x0 ][ y0 ] ae(v) mmvd_direction_idx[ x0 ][ y0 ] ae(v)} se não { se( MaxNumMergeCand > 1 ) merge_idx[x0 ][ y0 ] ae(v)}} if not { if( sps_ciip_enabled_flag && sps_triangle_enabled_flag && MaxNumTriangleMergeCand > 1 && slice_type = = B && cu_skip_flag[ x0 ][ y0 ] = = 0 && ÜcbWidth = = 4 && cbWidth = = 16) && ( cbWidth * cbHeight ) >= 64 && cbWidth < 128 && cbHeight < 128 ) { ciip_flag[ x0 ][ y0 ] ae(v) se( ciip_flag[ x0 ][ y0 ] && MaxNumMergeCand > 1 ) merge_idx[ x0 ][ y0 ] ae(v) se( !ciip_flag[ x0 ][ y0 ] && MaxNumTriangleMergeCand > 1 ) { merge_triangle_split_dir[ x0 ][ y0 ] ae(v) merge_triangle_idx0[ x0 ][ y0 ] ae(v) merge_triangle_idx1[ x0 ][ y0 ] ae(v)}}}}} 5.18 Example for adjusting chroma deblock filtering strength to 0
[00462] The following changes, recently added parts, are Petition 870220099106, dated 10 / 26 / 2022, p. 99 / 161 / 123, marked in bold and italics, and the deleted parts are marked with double square brackets (e.g., [[a]] denotes the deletion of the character “a”). The modifications are based on JVET-Q2001-vE. 8.8.3.5 Boundary filtering force derivation process
[00463] For xDi with i = 0..xN and yDj with j = 0..yN, the following applies: - If edgeFlags[ xDi ][ yDj ] is equal to 0, the variable bS[ xDi ][ yDj ] is set equal to 0.
[00464] - In other circumstances, the following applies: The sample values p0 and q0 are derived as follows: - If edgeType is equal to EDGE_VER, p0 is set equal to recPicture[ xCb + xDi - 1 ][ yCb + yDj ] and q0 is set equal to recPicture[ xCb + xDi ][ yCb + yDj ].
[00465] - In other circumstances (edgeType is equal to EDGE_HOR), p0 is set equal to recPicture[ xCb + xDi ][ yCb + yDj - 1 ] and q0 is set equal to recPicture[ xCb + xDi ][ yCb + yDj ].
[00466] - The variable bS[ xDi ][ yDj ] is derived as follows: - If cIdx is equal to 0 and both samples p0 and q0 are in an encoding and / or decoding block with intra_bdpcm_luma_flag equal to 1, bS[ xDi ][ yDj ] is set equal to 0.
[00467] - In other circumstances, if cIdx is greater than 0 and both samples p0 and q0 are in an encoding and / or decoding block with intra_bdpcm_chroma_flag equal to 1, bS[ xDi ][ yDj ] is set equal to 0.
[00468] - In other circumstances, if sample p0 or q0 is in the encoding and / or decoding block of an encoding and / or decoding unit encoded and / or decoded with intra prediction mode, bS[ xDi ][ yDj ] is set equal to 2.
[00469] - In other circumstances, if the edge of the block is also Petition 870220099106, dated 10 / 26 / 2022, page 100 / 161 / 123, if an edge of the encoding and / or decoding block and the sample po or qo is in an encoding and / or decoding block with ciip_flag equal to 1, bS[xDi][yDj] is set equal to 2.
[00470] - In other circumstances, if the block boundary is also a transform block boundary and the sample p0 or q0 is in a transform block that contains one or more non-zero transform coefficient levels, bS[ xDi ][ yDj ] is set equal to 1.
[00471] - [[In other circumstances, if the prediction mode of the encoding and / or decoding subblock containing sample p0 is different from the prediction mode of the encoding and / or decoding subblock containing sample q0 (i.e., one of the encoding and / or decoding subblocks is encoded and / or decoded in IBC prediction mode and the other is encoded and / or decoded in inter-prediction mode), bS[ xDi ][ yDj ] is set equal to 1.]] - In other circumstances, if cIdx equals 0, edgeFlags[xDi][yDj] is set to 2, and one or more of the following conditions are true, bS[xDi][yDj] is set to 1: The prediction mode for the encoding and / or decoding sub-block containing sample p0 is different from the prediction mode for the encoding and / or decoding sub-block containing sample q0.
[00472] - Both the encoding and / or decoding sub-block containing sample p0 and the encoding and / or decoding sub-block containing sample q0 are encoded and / or decoded in IBC prediction mode, and the absolute difference between the horizontal or vertical component of the block vectors used in the prediction of the two encoding and / or decoding sub-blocks is greater than or equal to 8 in luma 1 / 16 sample units.
[00473] - For the prediction of the encoding and / or decoding sub-block containing the sample p0, different reference figures or a Petition 870220099106, dated 10 / 26 / 2022, page 101 / 161 / 123 different number of motion vectors are used than for the prediction of the encoding and / or decoding sub-block containing the sample qo.
[00474] NOTE 1 - The determination of whether the reference figures used for the two encoding and / or decoding sub-blocks are the same or different is based solely on which figures are referenced, without considering whether a prediction is formed using an index in list 0 of the reference figure or an index in list 1 of the reference figure, and also without considering whether the position of the index in a list of the reference figure is different.
[00475] NOTE 2 - The number of motion vectors used for the prediction of a top-left sample encoding and / or decoding subblock covering (xSb, ySb) is equal to PredFlagL0[xSb][ySb] + PredFlagL1[xSb][ySb].
[00476] - A motion vector is used to predict the encoding and / or decoding sub-block containing sample p0 and a motion vector is used to predict the encoding and / or decoding sub-block containing sample q0, and the absolute difference between the horizontal or vertical component of the motion vectors used is greater than or equal to 8 in luma 1 / 16 sample units.
[00477] - Two motion vectors and two different reference figures are used to predict the encoding and / or decoding sub-block containing sample p0, two motion vectors for the same two reference figures are used to predict the encoding and / or decoding sub-block containing sample q0 and the absolute difference between the horizontal or vertical component of the two motion vectors used in predicting the two encoding and / or decoding sub-blocks for the same reference figure is greater than or equal to 8 in luma 1 / 16 sample units.
[00478] - Two motion vectors for the same figure of Petition 870220099106, dated 10 / 26 / 2022, page 102 / 161 / 123: reference figures are used to predict the encoding and / or decoding sub-block containing sample p0; two motion vectors for the same reference figure are used to predict the encoding and / or decoding sub-block containing sample q0; and both of the following conditions are true: - The absolute difference between the horizontal or vertical component of the motion vectors from list 0 used in predicting the two encoding and / or decoding subblocks is greater than or equal to 8 in 1 / 16 luma samples, or the absolute difference between the horizontal or vertical component of the motion vectors from list 1 used in predicting the two encoding and / or decoding subblocks is greater than or equal to 8 in 1 / 16 luma sample units.
[00479] - The absolute difference between the horizontal or vertical component of the motion vector from list 0 used in predicting the encoding and / or decoding sub-block containing sample p0 and the motion vector from list 1 used in predicting the encoding and / or decoding sub-block containing sample q0 is greater than or equal to 8 in 1 / 16 luma sample units, or the absolute difference between the horizontal or vertical component of the motion vector from list 1 used in predicting the encoding and / or decoding sub-block containing sample p0 and the motion vector from list 0 used in predicting the encoding and / or decoding sub-block containing sample q0 is greater than or equal to 8 in 1 / 16 luma sample units.
[00480] In other circumstances, the variable bS[ xDi ][ yDj ] is set equal to 0.
[00481] Figure 17A is a block diagram of a 1700 video processing device. The 1700 device can be used to implement one or more of the methods described herein. The 1700 device can be incorporated into a smartphone, tablet, computer, Internet receiver, etc. Petition 870220099106, dated 10 / 26 / 2022, pages 103 / 161 / 123 Things (IoT) and so forth. The 1700 device may include one or more 1702 processors, one or more 1704 memories, and 1706 video processing hardware. The 1702 processor(s) may be configured to implement one or more methods described herein. The 1704 memory(ies) may be used to store data and code used to implement the methods and techniques described herein. The 1706 video processing hardware may be used to implement, within the hardware circuitry, some techniques described herein.
[00482] Figure 17B is another example of a block diagram of a video processing system in which the techniques described here can be implemented. Figure 17B is a block diagram showing an example of the 1710 video processing system in which several techniques described here can be implemented. Various implementations may include some or all of the components of the 1710 system. The 1710 system may include 1712 input to receive video content. The video content may be received in a raw or uncompressed format, for example, 8- or 10-bit multicomponent pixel values, or it may be in a compressed or encoded format. The 1712 input 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 network (PON), etc., and wireless interfaces such as Wi-Fi or cellular interfaces.
[00483] The 17100 system may include an encoding and / or decoding component 1714 that may implement the various encoding and / or decoding methods described in this document. The encoding and / or decoding component 1714 may reduce the average bitrate of the video from the input 1712 to the output of the encoding and / or decoding component 1714 to produce a Petition 870220099106, dated 10 / 26 / 2022, pp. 104 / 161 / 123, encoded and / or decoded representation of the video. The encoding and / or decoding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the encoding and / or decoding component 1714 can be either stored or transmitted via a connected communication, as represented by component 1716. The stored or communicated (or encoded and / or decoded) representation of the continuous bitstream received at input 1712 can be used by component 1718 to generate pixel values or displayable video that is sent to a display interface 1720. The process of generating user-viewable video from the continuous bitstream representation is sometimes called video decompression.Furthermore, although certain video processing operations are referred to as "encoding and / or decoding" operations or tools, it will be understood that encoding and / or decoding tools or operations are used in an encoder, and corresponding decoding tools or operations that reverse the results of encoding and / or decoding will be performed by a decoder.
[00484] Examples of a peripheral bus interface or a display interface may include Universal Serial Bus (USB) or High-Definition Multimedia Interface (HDMI) or DisplayPort and so on. Examples of storage interfaces include SATA (Serial Attachment Technology Advanced), PCI, IDE interface and the like. The techniques described in this document can be incorporated into various electronic devices, such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and / or video display.
[00485] Figure 21 is a block diagram illustrating an example of a video encoding and / or decoding system 100 that can be used Petition 870220099106, dated 10 / 26 / 2022, pp. 105 / 161 100 / 123 the techniques in this description.
[00486] As shown in Figure 21, the video encoding and / or decoding system 100 may include a source device 110 and a destination device 120. The source device 110 generates encoded video data and may be referred to as a video encoding device. The destination device 120 may decode the encoded video data generated by the source device 110 and may be referred to as a video decoding device.
[00487] The source device 110 may include a video source 112, a video encoder 114, and an input / output (I / O) interface 116.
[00488] 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 system of computer graphics elements for generating video data, or a combination of such sources. The video data may comprise one or more images. The video encoder 114 encodes the video data from the video source 112 to generate a continuous bitstream. The continuous bitstream may include a sequence of bits that forms an encoded and / or decoded representation of the video data. The continuous bitstream may include encoded and / or decoded images and associated data. The encoded and / or decoded image is an encoded and / or decoded representation of an image. The associated data may include sequence parameter sets, image parameter sets, and other syntax structures.The I / O interface 116 may include a modulator / demodulator (modem) and / or a transmitter. The encoded video data may be transmitted directly to the destination device 120 via the I / O interface 116 through the network 130a. The encoded video data may also be stored on a media / server. Petition 870220099106, dated 10 / 26 / 2022, pp. 106 / 161 101 / 123 storage 130b for access by the target device 120.
[00489] The target device 120 may include an I / O interface 126, a video decoder 124 and a display device 122.
[00490] The I / O interface 126 may include a receiver and / or a modem. The I / O interface 126 may acquire encoded video data from the source device 110 or from the storage media / server 130b. The video decoder 124 may decode the encoded video data. The display device 122 may display the decoded video data to a user. The display device 122 may be integrated with the target device 120, or it may be external to the target device 120 that is configured to interface with an external display device.
[00491] The 114 video encoder and the 124 video decoder can operate according to a video compression standard, such as the High Efficiency Video Coding and / or Decoding (HEVC) standard, the Versatile Video Coding and / or Decoding (VVC) standard, and other current and / or additional standards.
[00492] Figure 22 is a block diagram illustrating an example of video encoder 200, which may be video encoder 114 in system 100 illustrated in Figure 21.
[00493] The Video Encoder 200 can be configured to perform any and all techniques described herein. In the example in Figure 22, the Video Encoder 200 includes a plurality of functional components. The techniques described herein can be shared among the various components of the Video Encoder 200. In some examples, a processor can be configured to perform any and all techniques described herein.
[00494] The functional components of the video encoder 200 may include a partition unit 201, a prediction unit 202 that Petition 870220099106, dated 10 / 26 / 2022, pp. 107 / 161 102 / 123 may include a mode selection unit 203, a motion estimation unit 204, a motion compensation unit 205 and an intraprediction unit 206, a residual generation unit 207, a transform unit 208, a quantization unit 209, an inverse quantization unit 210, an inverse transform unit 211, a reconstruction unit 212, a temporary storage 213, and an entropy encoding unit 214.
[00495] In other examples, the video encoder 200 may include more, fewer, or different functional components. In one example, the prediction unit 202 may include an intrablock copy (IBC) unit. The IBC unit may perform prediction in an IBC mode where at least one reference image is an image in which the current video block is located.
[00496] Furthermore, some components, such as the motion estimation unit 204 and the motion compensation unit 205, may be highly integrated, but are represented separately in the example in Figure 22 for explanatory purposes.
[00497] Partition unit 201 can partition an image into one or more video blocks. Video encoder 200 and video decoder 300 can support various video block sizes.
[00498] The mode selection unit 203 can select one of the encoding and / or decoding modes, intra or inter, for example, based on error results, and provide the resulting intra- or inter-encoded and / or decoded block to a residual generation unit 207 to generate residual block data and to a reconstruction unit 212 to reconstruct the encoded block for use as a reference image. In some examples, the mode selection unit 203 can select a combination of intra- and inter-prediction (CIIP) mode where the prediction is based on an interprediction signal and an intraprediction signal. The unit of Petition 870220099106, dated 10 / 26 / 2022, pp. 108 / 161 103 / 123 mode selection 203 can also select a resolution for a motion vector (e.g., subpixel or integral pixel precision) for the block in the case of interprediction.
[00499] To perform interprediction on a current video block, the motion estimation unit 204 can generate motion information for the current video block by comparing one or more reference frames from temporary storage 213 with the current video block. The motion compensation unit 205 can determine a predicted video block for the current video block based on motion information and decoded image samples from temporary storage 213 different from the image associated with the current video block.
[00500] The motion estimation unit 204 and the motion compensation unit 205 can perform different operations for a current video block, for example, depending on whether the current video block is in an I slice, a P slice, or a B slice.
[00501] In some examples, motion estimation unit 204 can perform one-way prediction for the current video block, and motion estimation unit 204 can retrieve reference images from list 0 or list 1 for a reference video block for the current video block. Motion estimation unit 204 can then generate a reference index indicating the reference image in list 0 or list 1 that contains 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 can transmit the reference index, a prediction direction indicator, and the motion vector as the motion information for the current video block. Motion compensation unit 205 can generate the predicted video block from the current block based on the reference video block. Petition 870220099106, dated 10 / 26 / 2022, pp. 109 / 161 104 / 123 indicated by the movement information of the current video block.
[00502] In other examples, motion estimation unit 204 can perform bidirectional prediction for the current video block; motion estimation unit 204 can retrieve reference images from list 0 for a reference video block for the current video block, and it can also retrieve reference images from list 1 for another reference video block for the current video block. Motion estimation unit 204 can then generate reference indices that indicate the reference images in list 0 and list 1 containing the reference video blocks, and motion vectors that indicate spatial displacements between the reference video blocks and the current video block. Motion estimation unit 204 can transmit the reference indices and motion vectors of the current video block as the motion information of the current video block.The motion compensation unit 205 can generate the predicted video block from the current video block based on the reference video blocks indicated by the motion information of the current video block.
[00503] In some examples, the motion estimation unit 204 can transmit a complete set of motion information to the decoding processing of a decoder.
[00504] In some examples, motion estimation unit 204 may not transmit a complete set of motion information for the current video. Instead, motion estimation unit 204 may signal the motion information of the current video block relative to the 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.
[00505] In one example, the unit of motion estimate 204 Petition 870220099106, dated 10 / 26 / 2022, pp. 110 / 161 105 / 123 may indicate, in a syntax structure associated with the current video block, a value that tells the video decoder 300 that the current video block has the same motion information as another video block.
[00506] In another example, motion estimation unit 204 can identify, in a syntax structure associated with the current video block, another video block and a motion vector difference (MVD). 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 can use the motion vector of the indicated video block and the motion vector difference to determine the motion vector of the current video block.
[00507] As discussed previously, the Video Encoder 200 can predictively signal the motion vector. Two examples of predictive signaling techniques that can be implemented by the Video Encoder 200 include advanced motion vector prediction (AMVP) and blend mode signaling.
[00508] The intraprediction unit 206 can perform intraprediction on the current video block. When the intraprediction unit 206 performs intraprediction on the current video block, the intraprediction unit 206 can generate prediction data for the current video block based on decoded samples of other video blocks in the same image. The prediction data for the current video block can include a predicted video block and various syntax elements.
[00509] Residual generation unit 207 can generate residual data for the current video block by subtracting (e.g., indicated by the minus sign) the predicted video block(s) 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 components. Petition 870220099106, dated 10 / 26 / 2022, pp. 111 / 161 106 / 123 sample of the samples in the current video block.
[00510] In other examples, there may be no residual data for the current video block, for example in an ignore mode, and the residual generation unit 207 may not perform the subtraction operation.
[00511] Transform processing unit 208 can generate one or more video blocks from the transform coefficient for the current video block by applying one or more transforms to a residual video block associated with the current video block.
[00512] After the transform processing unit 208 generates a video block of the transform coefficient associated with the current video block, the quantization unit 209 can quantize the video block of the transform coefficient associated with the current video block based on one or more values of the quantization parameter (QP) associated with the current video block.
[00513] The inverse quantization unit 210 and the inverse transform unit 211 can apply inverse quantization and inverse transforms to the transform coefficient video block, respectively, to reconstruct a residual video block from the transform coefficient video block. The reconstruction unit 212 can add the reconstructed residual video block to the corresponding samples from one or more predicted video blocks generated by the prediction unit 202 to produce a reconstructed video block associated with the current block for storage in temporary storage 213.
[00514] After reconstruction unit 212 reconstructs the video block, loop filtering can be performed to reduce video block artifacts in the video block.
[00515] The entropy encoding unit 214 can receive data from other functional components of the video encoder 200. Petition 870220099106, dated 10 / 26 / 2022, pp. 112 / 161 107 / 123 When the entropy-encoding unit 214 receives the data, it can perform one or more entropy encoding operations to generate entropy-encoded data and transmit a continuous bit stream that includes the entropy-encoded data.
[00516] Figure 23 is a block diagram illustrating an example of video decoder 300 which may be video decoder 114 in system 100 illustrated in figure 21.
[00517] The 300 video decoder can be configured to perform any and all techniques described herein. In the example in Figure 23, the 300 video decoder includes a plurality of functional components. The techniques described herein can be shared among the various components of the 300 video decoder. In some examples, a processor can be configured to perform any and all techniques described herein.
[00518] In the example in Figure 23, the video decoder 300 includes an entropy decoding unit 301, a motion compensation unit 302, an intraprediction unit 303, an inverse quantization unit 304, an inverse transform unit 305, and a reconstruction unit 306 and a temporary storage unit 307. The video decoder 300 can, in some examples, perform a decoding pass that is generally reciprocal to the encoding pass described in relation to the video encoder 200 (for example, Figure 22).
[00519] The entropy decoding unit 301 can recover a continuous stream of encoded bits. The continuous stream of encoded bits may include entropy-encoded and / or entropy-decoded video data (e.g., encoded blocks of video data). The entropy decoding unit 301 can decode the entropy-encoded and / or entropy-decoded video data, and, from the entropy-decoded video data... Petition 870220099106, dated 10 / 26 / 2022, pp. 113 / 161 108 / 123 entropy, the 302 motion compensation unit can determine motion information including motion vectors, motion vector accuracy, reference image list indices, and other motion information. The 302 motion compensation unit can, for example, determine such information by performing AMVP and blending modes.
[00520] The motion compensation unit 302 can produce blocks with compensated motion, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used with subpixel precision can be included in the syntax elements.
[00521] The motion compensation unit 302 can use interpolation filters used by the video encoder 200 during video block encoding to calculate interpolated values for subintegral pixels of a reference block. The motion compensation unit 302 can determine the interpolation filters used by the video encoder 200 according to the received syntax information and use the interpolation filters to produce predictive blocks.
[00522] The 302 motion compensation unit can use some of the syntax information to determine block sizes used to encode frame(s) and / or slice(s) of the encoded video sequence, partition information that describes how each macroblock of an image in the encoded video sequence is partitioned, modes that indicate how each partition is encoded, one or more reference frames (and reference frame lists) for each intercoded block, and other information to decode the encoded video sequence.
[00523] The intraprediction unit 303 can use intraprediction modes, for example, received in the continuous bit stream to form a prediction block from spatially adjacent blocks. The unit Petition 870220099106, dated 10 / 26 / 2022, pp. 114 / 161 109 / 123 of inverse quantization 303 inversely quantizes, that is, dequantizes, the quantized video block coefficients provided in the continuous bit stream and decoded by the entropy decoding unit 301. The inverse transform unit 303 applies an inverse transform.
[00524] The reconstruction unit 306 can sum the residual blocks with the corresponding prediction blocks generated by the motion compensation unit 202 or the intraprediction unit 303 to form decoded blocks. If desired, a deblocking filter can also be applied to filter the decoded blocks in order to remove blocking artifacts. The decoded video blocks are then stored in temporary storage 307, which provides reference blocks for subsequent motion compensation.
[00525] Figure 18 is a flowchart for an 1800 method of processing a video. The 1800 method includes analyzing (1802), for a conversion between a video region of a video and an encoded and / or decoded representation of the video region, the encoded and / or decoded representation according to a syntax rule that defines a relationship between a chroma block size and a color format of the video region; and performing (1804) the conversion by performing the analysis according to the syntax rule.
[00526] A list of examples preferred by some modalities is provided below. In the present document, a video region can be an encoding and / or decoding block or a slice or a encoding and / or decoding unit tree or a prediction block or a transform block.
[00527] The first set of clauses shows example modalities of techniques discussed in the previous section. The following clauses can be implemented together with additional techniques described in item 1 of the previous section. Petition 870220099106, dated 10 / 26 / 2022, pp. 115 / 161 110 / 123
[00528] 1. A video processing method comprising: To analyze, for a conversion between a video region of a video and an encoded and / or decoded representation of the video region, the encoded and / or decoded representation according to a syntax rule that defines a relationship between a chroma block size and a color format of the video region; and to perform the conversion by performing the analysis according to the syntax rule.
[00529] 2. The method in clause 1, where the color format is 4:4:4 and the syntax rule specifies that the chroma block is subject to the same size restriction as that for one of the luma blocks.
[00530] 3. The method in clause 1, where the color format is 4:2:2 and the syntax rule specifies that the chroma block is subject to the same size restriction as that for the 4:2:0 color format.
[00531] 4. The method of any of clauses 1-3, wherein the syntax specifies that one of the prediction modes and small block partitions are used in a chroma format-dependent manner.
[00532] 5. The method in clause 1, where the syntax rule defines that a smaller allowed resource size is enabled for video region conversion based on the video region color format.
[00533] The following clauses can be implemented together with additional techniques described in item 2 of the previous section.
[00534] 6. A video processing method comprising: Based on a video property and a video chroma key format, determine an encoding and / or decoding mode for a node in the video's encoding and / or decoding tree; and perform a conversion between an encoded and / or decoded representation of the video and a video block from the encoding and / or decoding tree node using the determined encoding and / or decoding mode.
[00535] 7. The method of clause 6, in which the encoding and / or Petition 870220099106, dated 10 / 26 / 2022, pp. 116 / 161 111 / 123 decoding is determined to be MODE_TYPE_ALL for the chroma format being 4:2:2, MODE_TYPE_INTRA or MODE_TYPE_INTER for the chroma format being 4:2:0 in the case where the property is: i. the encoding and / or decoding node is a node of the MxN encoding and / or decoding tree with a horizontal binary tree split; ii. the encoding and / or decoding node is a node of the MxN encoding and / or decoding tree with a vertical binary tree split; iii. the encoding and / or decoding node is a node of the MxN encoding and / or decoding tree with a horizontal ternary tree split; or iv. the encoding and / or decoding node is a node of the MxN encoding and / or decoding tree with a vertical ternary tree split.
[00536] 8. The method of clause 7, where M = 8, or 16 or 32 and N = 4 or 8 or 16.
[00537] The following clauses can be implemented together with additional techniques described in item 12 of the previous section.
[00538] 9. A video processing method comprising: To determine, based on a rule, whether a certain size of chroma blocks is allowed in a video region of a video; and to perform a conversion between the video region and an encoded and / or decoded representation of the video region based on the determination.
[00539] 10. The method in clause 9, where the rule specifies that 2xN chroma blocks are disallowed due to the video region including a dual tree partition.
[00540] 11. The method of clause 9, in which the rule specifies that 2N chroma blocks are disallowed due to the video region that includes Petition 870220099106, dated 10 / 26 / 2022, pp. 117 / 161 112 / 123 a single tree partition.
[00541] 12. The method of clauses 10 or 11, where N <= 64.
[00542] The following clauses can be implemented together with additional techniques described in items 13, 14 and 15 of the previous section.
[00543] 13. A video processing method comprising: To determine, based on a rule that allows the use of an encoding and / or decoding mode for a video condition, that an encoding and / or decoding mode is permitted for a video region; and to perform a conversion between an encoded and / or decoded representation of pixels in the video region and pixels of the video region based on that determination.
[00544] 14. The method of clause 13, where the video condition is block size, and where the rule allows the use of intra block copy mode for small block sizes of luma blocks.
[00545] 15. The method of clause 14, wherein small block sizes include luma block sizes 8x4, 8x8, 16x4 or 4xN.
[00546] 16. The method of clause 13, in which the rule allows the use of intra block copy mode for video region conversion using a MODE_TYPE_INTER encoding and / or decoding mode.
[00547] 17. The method of clause 13, in which the rule allows the use of palette encoding and / or decoding mode for video region conversion using a MODE_TYPE_INTER encoding and / or decoding mode.
[00548] The following clauses can be implemented together with additional techniques described in items 16, 17, 18 of the previous section.
[00549] 18. A video processing method comprising: Perform a conversion between a video block of a video and an encoded and / or decoded representation of the video block using a video encoding and / or decoding mode, where an element of Petition 870220099106, dated 10 / 26 / 2022, pp. 118 / 161 113 / 123 syntax that signals the encoding and / or decoding mode is selectively included in the encoded and / or decoded representation based on a rule.
[00550] 19. The method of clause 18, wherein the video encoding and / or decoding mode is an intra-block encoding and / or decoding mode and wherein the rule specifies using a type of video encoding and / or decoding mode to control the inclusion of the syntax element in the encoded and / or decoded representation.
[00551] 20. The method of clause 19, in which the rule specifies the explicit signaling of a block not to IGNORE.
[00552] 21. The method of clause 18, in which the rule specifies to implicitly signal the intra block copy indicator based on an ignore indicator and a video block mode type.
[00553] 22. The method of clause 18, wherein the encoding and / or decoding mode is a palette encoding and / or decoding mode and wherein the rule specifies to selectively include a palette encoding and / or decoding indicator based on the video block mode type.
[00554] The following clauses can be implemented together with additional techniques described in item 21 of the previous section.
[00555] 23. A video processing method comprising: To determine, due to a chroma block having a size smaller than a threshold size, that a type of transform used during a conversion between the chroma block and an encoded and / or decoded representation of the chroma block is different from a type of transform used for a corresponding conversion of the luma block; and to perform the conversion based on that determination.
[00556] 24. The method of clause 23, where the limit size is MxN, where M is 2.
[00557] The following clauses can be implemented together Petition 870220099106, dated 10 / 26 / 2022, pp. 119 / 161 114 / 123 with additional techniques described in item 22 of the previous section.
[00558] 25. The method of any of clauses 1 to 24, where the conversion uses a combined inter and intra prediction mode as a MODE_TYPE_INTRA mode.
[00559] 26. The method of any of clauses 18 to 22, wherein the conversion uses a combined inter and intra prediction mode as a MODE_TYPE_INTER mode. For example, when considering CIIP as MODE_TYPE_INTER, the methods described in items 14-17 in the previous section may be applied. Or, when the methods described in items 14-16 are applied, CIIP may be considered as MODE_TYPE_INTER.
[00560] The following clauses can be implemented along with additional techniques described in items 3-6 of the previous section.
[00561] 27. A video processing method comprising: To determine whether a smallest chroma block rule is applied during a conversion between an encoded and / or decoded representation of a video region and pixel values of the video region, based on an encoding and / or decoding condition of the video region; and to perform the conversion based on that determination.
[00562] 28. The method of clause 17, in which the encoding and / or decoding condition comprises a color format of the video region.
[00563] 29. The method of clause 18, wherein the video region has a width of M pixels and a height of N pixels, and wherein the encoding and / or decoding condition additionally depends on values of M and / or N.
[00564] 30. The method in clause 29, where the smallest chroma block rule is activated because the video region has a 4:2:2 color format and M*N = 32 or M*N = 64.
[00565] The following clauses can be implemented together Petition 870220099106, dated 10 / 26 / 2022, pp. 120 / 161 115 / 123 with additional techniques described in items 7-11 of the previous section.
[00566] 31. A video processing method comprising: To determine, for a conversion between an encoded and / or decoded representation of a video region in a 4:2:2 format and pixel values of the video region, a mode type to be used for the conversion based on whether a smallest block chroma rule is enabled for the video region; and to perform the conversion based on that determination.
[00567] 32. The method in clause 31, where the video region mode type is set to 1 because the video region has a 4:2:2 format and the smallest chroma block rule is enabled.
[00568] 33. The method of clause 31, in which the determination of the mode type includes determining the mode type as an INTRA type due to the smallest chroma block rule being activated for the video region.
[00569] 34. The method of clause 31, in which the determination of the mode type includes determining that the INTER mode type is disabled due to the smallest chroma block rule being activated for the video region.
[00570] The following clauses can be implemented together with the additional techniques described in items 7-11 of the previous section.
[00571] 35. A video processing method comprising: To determine, for a conversion between an encoded and / or decoded representation of a video block and a video block of a video, whether block partitioning is allowed during the conversion, based on a mode type used during the conversion or a video block dimension; and to perform the conversion using the determination.
[00572] 36. The method of clause 35, wherein the block partitioning comprises either a binary tree partitioning or a ternary tree partitioning.
[00573] 37. The method of any of clauses 35-36, wherein, in the case where the mode type is INTER mode, block partitioning Petition 870220099106, dated 10 / 26 / 2022, pp. 121 / 161 116 / 123 is based on a restriction rule that allows or disallows certain partition types.
[00574] The following clauses can be implemented together with additional techniques described in item 34 of the previous section.
[00575] 38. A video processing method comprising: To determine, for a conversion between an encoded and / or decoded representation of a video segment and the video segment, apply a special processing mode to a chroma block of size MxN, where M by N are integers; and perform the conversion based on the determination.
[00576] 39. The method in clause 38, where the special processing mode disables the use of chroma blocks during conversion.
[00577] 40. The method of clause 38, in which the special processing mode uses DC prediction for an intraprediction of the chroma block.
[00578] 41. The method of clause 38, in which the special processing mode includes using a linear cross-component model to predict intra-block chroma coefficients derived from corresponding downsampled luma coefficients.
[00579] 42. The method of any of clauses 38-41, in which the special processing mode disables the use of the chroma block due to the video segment using a dual tree partitioning.
[00580] 43. The method of any of clauses 38-41, in which the special processing mode disables the use of the chroma block due to the video segment using a single tree partitioning.
[00581] 44. The method of any of clauses 1 to 43, wherein the conversion comprises encoding the video in the encoded and / or decoded representation. Petition 870220099106, dated 10 / 26 / 2022, pp. 122 / 161 117 / 123
[00582] 45. The method of any of clauses 1 to 43, wherein the conversion comprises decoding the encoded and / or decoded representation to generate pixel values of the video.
[00583] 46. A video decoding apparatus comprising a processor configured to implement a method cited in one or more of clauses 1 to 45.
[00584] 47. A video encoding apparatus comprising a processor configured to implement a method cited in one or more of clauses 1 to 45.
[00585] 48. A computer program product that has computer code stored in it, the code, when executed by a processor, causes the processor to implement a method mentioned in any of clauses 1 to 45.
[00586] 49. A method, apparatus or system described in this document.
[00587] A second set of clauses shows example modalities of techniques discussed in the previous section (e.g., items 37-40).
[00588] 1. A video processing method (for example, method 2400 of the form shown in figure 24A), comprising: performing 2402 a conversion between a video that includes a video region and a continuous bitstream of the video according to a rule; and wherein the rule specifies a relationship between activation of a palette mode and a type of encoding and / or decoding of the video region.
[00589] 2. The method in clause 1, where the rule specifies that palette mode is activated in the case where the encoding and / or decoding type is MODE_TYPE ALL which allows an intra mode, a palette mode, and an intra block copy mode for conversion or MODE_TYPE_INTRA which allows the use of an intra mode for conversion. Petition 870220099106, dated 10 / 26 / 2022, pp. 123 / 161 118 / 123
[00590] 3. The method in clause 2, where the rule specifies that palette mode is always disabled in the case where the encoding and / or decoding type is MODE_TYPE_INTER which allows only one inter encoding and / or decoding mode.
[00591] 4. A video processing method (for example, method 2410 of the form shown in figure 24B), comprising: performing 2412 a conversion between a video comprising a first video region and a second video region and a continuous bitstream of the video according to a rule; and wherein the rule specifies that a filtering strength (bs) of an unlock filter for chroma components of the video is set to 0 in the case where a first block is in an intra-block copy mode and a second block is in a palette mode.
[00592] 5. The method in clause 4, where the rule further specifies that the filtering strength is set to 0 in the case where a variable related to a chroma component in the video has a determined value.
[00593] 6. The method of clause 5, in which the determined value is not equal to 0.
[00594] 7. A video processing method (for example, method 2420 of the form shown in figure 24C), comprising: performing 2422 a conversion between a video and a continuous bitstream of the video according to a format rule, and wherein the format rule specifies that a variable related to an input bit intensity of the video is limited according to a profile of the continuous bitstream.
[00595] 8. The method in clause 7, where the variable is internal_minus_input_bit_depth.
[00596] 9. The method of clause 7, in which the format rule specifies that the variable is limited to being in a range [0, 2] in the case of a Petition 870220099106, dated 10 / 26 / 2022, pp. 124 / 161 119 / 123 10-bit profile.
[00597] 10. The method of clause 7, in which the format rule specifies that the variable is limited to being 0 in the case of an 8-bit profile.
[00598] 11. The method of clause 7, in which the format rule specifies that the variable is limited to being in a range [0, K] in the case of a (K+8) bit profile, where K is an integer greater than 0.
[00599] 12. A video processing method (for example, method 2430, as shown in figure 24D), comprising: performing 2432 a conversion between a video and a continuous bitstream of the video according to a format rule, and wherein the format rule specifies that a variable indicating the minimum allowed quantization parameter is limited according to a profile of the continuous bitstream.
[00600] 13. The method of clause 12, in which the variable is QpPrimeTsMin.
[00601] 14. The method of clause 13, where the format rule specifies that (QpPrimeTsMin - 4) / 6 is limited to being in a range [0, 2] in the case of a 10-bit profile.
[00602] 15. The method of clause 13, where the format rule specifies that (QpPrimeTsMin - 4) / 6 is limited to being 0 in the case of an 8-bit profile.
[00603] 16. The method of clause 12, where the format rule specifies that (QpPrimeTsMin - 4) / 6 is limited to being in a range [0, K] in the case of a (K+8) bit profile, where K is an integer greater than 0.
[00604] 17. The method of any of clauses 1 to 16, where the conversion includes encoding the video in a continuous bitstream.
[00605] 18. The method of any of clauses 1 to 16, where the conversion includes decoding the video from the continuous bitstream.
[00606] 19. The method of any of clauses 1 to 16, in which the Petition 870220099106, dated 10 / 26 / 2022, pp. 125 / 161 120 / 123 conversion involves generating a continuous bitstream from the video, and the method further comprises: storing the continuous bitstream on a non-transient, computer-readable recording medium.
[00607] 20. A video processing device, comprising a processor configured to implement a method mentioned in any one or more of clauses 1 to 19.
[00608] 21. A method for storing a continuous bitstream of a video, comprising a method cited in any of clauses 1 to 19, and further including storing the continuous bitstream on a non-transient, computer-readable recording medium.
[00609] 22. A computer-readable medium that stores program code which, when executed, causes a processor to implement a method cited in any one or more of clauses 1 to 19.
[00610] 23. A computer-readable medium that stores a continuous bit stream generated in accordance with any of the methods described above.
[00611] 24. A video processing device for storing a continuous bitstream representation, wherein the video processing device is configured to implement a method mentioned in any one or more of clauses 1 to 19.
[00612] The solutions, examples, embodiments, modules, and functional operations described, and others described in this document, may be implemented in a set of digital electronic circuits, or in computer software, embedded software, or hardware, including the structures described in this document and their structural equivalents, or in combinations of one or more thereof. The embodiments described, and others, may be implemented as one or more computer program products, that is, one or more modules of computer program instructions encoded on a computer-readable medium for execution. Petition 870220099106, dated 10 / 26 / 2022, pp. 126 / 161 121 / 123 by, or to control the operation of, a data processing apparatus. Computer-readable media may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that effects a machine-readable propagated signal, or a combination of one or more of these. The term “data processing apparatus” encompasses all apparatus, devices, and machines for data processing, including, by way of example, a programmable processor, a computer, or multiple processors or computers. The apparatus may include, in addition to hardware, code that creates an execution environment for the computer program in question, for example, code that constitutes embedded processor software, a protocol stack, a database management system, an operating system, or a combination of one or more of these.A propagated signal is an artificially generated signal, for example, an electrical, optical, or electromagnetic signal generated by a machine, which is generated to encode information for transmission to a suitable receiving device.
[00613] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and can be implemented in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that contains other programs or data (for example, one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (for example, files that store one or more modules, subprograms, or code snippets). A Petition 870220099106, dated 10 / 26 / 2022, pp. 127 / 161 122 / 123 A computer program can be implemented to run on one computer or on multiple computers that are located in one location or distributed across multiple locations and interconnected by a communication network.
[00614] The processes and logical flows described in this document can be performed by one or more programmable processors that execute one or more computer programs to perform functions by operating on input data and generating output. The processes and logical flows can also be performed by, and the device can also be implemented as, a set of special-purpose logic circuits, for example, an FPGA (field-programmable gate array) or an ASIC (application-specific integrated circuit).
[00615] Processors suitable for running a computer program include, by way of example, both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. In general, a processor will receive instructions and data from either read-only memory or random-access memory, or both. The essential elements of a computer are a processor to execute instructions and one or more memory devices to store instructions and data. In general, a computer will also include, or be operationally coupled to receive data from or transfer data to, or both, one or more mass storage devices to store data, for example, magnetic disks, magneto-optical disks, or optical disks. However, a computer does not need to have such devices.Computer-readable media suitable for storing computer program instructions and data includes all forms of non-volatile memory, media, and memory devices, including, by way of example, semiconductor memory devices, for example, EPROM, EEPROM, and flash memory devices; magnetic disks, for example, internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and memory may... Petition 870220099106, dated 10 / 26 / 2022, pp. 128 / 161 123 / 123 to be complemented by, or incorporated into, a set of special-purpose logic circuits.
[00616] Although this patent document contains many specifics, these should not be interpreted as limitations on the scope of any subject matter or what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of the particular techniques. Certain features that are described in this patent document in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, several features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features arising from the claimed combination may be excised from the combination, and the claimed combination may be directed toward a subcombination or variation of a subcombination.
[00617] Similarly, although operations are represented in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Furthermore, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.
[00618] Only a few implementations and examples are described, and other implementations, enhancements, and variations may be made based on what is described and illustrated in this patent document. Petition 870220099106, dated 10 / 26 / 2022, pp. 129 / 161
Claims
1 / 8 CLAIMS 1. A method for processing video data, characterized in that it comprises: determining, for a conversion between a current video block of a video image and a continuous bitstream of the video, whether a first encoding and / or decoding mode is applied to the current video block according to a first rule, wherein in the first encoding and / or decoding mode, reconstructed samples are represented by a set of representative color values and the set of representative color values comprises at least one of 1) palette predictors, 2) escaped samples, or 3) palette information included in the continuous bitstream; and performing the conversion at least based on the determination,wherein the first rule specifies that the first encoding and / or decoding mode is conditionally allowed for the current video block when the current video block has a mode type MODE_TYPE_ALL or a mode type MODE_TYPE_INTRA and that the first encoding and / or decoding mode is not allowed for the current video block when the current video block has a mode type MODE_TYPE_INTER, wherein a reconstructed image sample matrix of the video image is additionally obtained and an unblocking filter process is applied to at least one edge in the reconstructed image sample matrix, wherein a contour filtering intensity matrix is derived for the unblocking filter process according to a second rule which specifies that bS[ xDi ][ yDj ] equals 0 when a set of conditions is not met, the reconstructed image sample matrix is a reconstructed luma image sample matrix,a variable related to an edge flag is not equal to 2 and two mapping variables for two samples have different values, where bS[ xDi ][ yDj ] denotes an element in the contour filtering intensity matrix for xDi with i = 0..xN and yDj with j = 0..yN, where the two samples are samples from the reconstructed image sample matrix corresponding to bS[ xDi ][ yDj ], and where the two variables indicate prediction modes of two video blocks in the reconstructed image sample matrix containing the two samples, respectively, or the two variables indicate prediction modes of two video sub-blocks split from one or more video blocks in the reconstructed image sample matrix containing the two samples, respectively.
2. A method according to claim 1, characterized in that the mode type MODE_TYPE_ALL specifies whether intra modes, an intra-block copy mode, the first encoding and / or decoding mode, and inter modes are allowed for video blocks within an encoding and / or decoding tree node comprising the current video block, wherein the mode type MODE_TYPE_INTRA specifies that only intra modes, the intra-block copy mode, and the first encoding and / or decoding mode are allowed for video blocks within an encoding and / or decoding tree node comprising the current video block, and wherein the mode type MODE_TYPE_INTER specifies that only inter modes are allowed for video blocks within an encoding and / or decoding tree node comprising the current video block.
3. Method according to claim 1, characterized in that a variable QpPrimeTsMin indicating a minimum allowed quantization parameter and determined based on a value of a syntax element included in the continuous bitstream is additionally applied to determine the reconstructed samples of the current video block, where (QpPrimeTsMin - 4) / 6 is restricted to be within [0, K], where K is a positive integer.
4. Method according to claim 1, characterized in that a syntax element indicating a bit intensity of samples in the video image is included in the continuous bitstream and is restricted to being within [0, 2].
5. Method according to claim 1, characterized in that the second rule further specifies that bS[ xDi ][ yDj] is equal to 0 when the set of conditions is not satisfied, the reconstructed image sample matrix is a reconstructed chroma image sample matrix, and the two mapping variables for the two samples have different values.
6. Method according to claim 1, characterized in that the set of conditions comprises that the two samples are in a video block with ciip_flag equal to 1.
7. Method according to claim 1, characterized in that the set of conditions comprises that a prediction mode of a first sample located in the same video unit as one of the two samples is an intra mode.
8. Method according to claim 1, characterized in that a reconstructed chroma image sample matrix from the video image is additionally obtained and an unblocking filter process is applied to at least one edge in the reconstructed chroma image sample matrix, wherein a contour filtering intensity matrix is derived for the unblocking filter process according to a third rule specifying that bS[ xDi ][ yDj ] Petition 870260068404, dated 10 / 07 / 2026, page 16 / 132 4 / 8 corresponding to two samples of the reconstructed chroma image sample matrix is equal to 0 when the two samples are located on both sides of an edge and the two sides are encoded and / or decoded with the first encoding and / or decoding mode and an intra-block copy mode, respectively.
9. Method according to claim 1, characterized in that a syntax element indicating a bit intensity of samples in the video image is included in the continuous bit stream and is restricted to being within [0, M] in a bit profile (M+8), where M is a positive integer.
10. Method according to claim 1, characterized in that the conversion includes encoding the video in a continuous bitstream.
11. Method according to claim 1, characterized in that the conversion includes decoding the video from the continuous bitstream.
12. Apparatus for processing video data, characterized in that it comprises a processor and a non-transient memory with instructions therein, wherein the instructions, when executed by the processor, cause the processor to: determine, for a conversion between a current video block of a video image and a continuous bitstream of the video, whether a first encoding and / or decoding mode is applied to the current video block according to a first rule, wherein in the first encoding and / or decoding mode, reconstructed samples are represented by a set of representative color values and the set of representative color values comprises at least one of 1) palette predictors, 2) escaped samples or 3) palette information included in the continuous bitstream; and Petition 870260068404, dated 10 / 07 / 2026, page 17 / 132 5 / 8 perform the conversion at least based on the determination,wherein the first rule specifies that the first encoding and / or decoding mode is conditionally allowed for the current video block when the current video block has a mode type MODE_TYPE_ALL or a mode type MODE_TYPE_INTRA and that the first encoding and / or decoding mode is not allowed for the current video block when the current video block has a mode type MODE_TYPE_INTER, wherein a reconstructed image sample matrix of the video image is additionally obtained and an unblocking filter process is applied to at least one edge in the reconstructed image sample matrix, wherein a contour filtering intensity matrix is derived for the unblocking filter process according to a second rule which specifies that bS[ xDi ][ yDj ] equals 0 when a set of conditions is not met, the reconstructed image sample matrix is a reconstructed luma image sample matrix,a variable related to an edge flag is not equal to 2 and two mapping variables for two samples have different values, where bS[ xDi ][ yDj ] denotes an element in the contour filtering intensity matrix for xDi with i = 0..xN and yDj with j = 0..yN, where the two samples are samples from the reconstructed image sample matrix corresponding to bS[ xDi ][ yDj ], and where the two variables indicate prediction modes of two video blocks in the reconstructed image sample matrix containing the two samples, respectively, or the two variables indicate prediction modes of two video sub-blocks split from one or more video blocks in the reconstructed image sample matrix containing the two samples, respectively. Petition 870260068404, dated 10 / 07 / 2026, p. 18 / 132 6 / 8, 13. A non-transient, computer-readable storage medium characterized in that it stores instructions that cause the processor to: determine, for a conversion between a current video block of a video image and a continuous bitstream of the video, whether a first encoding and / or decoding mode is applied to the current video block according to a first rule, wherein in the first encoding and / or decoding mode, reconstructed samples are represented by a set of representative color values and the set of representative color values comprises at least one of 1) palette predictors, 2) escaped samples, or 3) palette information included in the continuous bitstream; and perform the conversion at least based on the determination,wherein the first rule specifies that the first encoding and / or decoding mode is conditionally allowed for the current video block when the current video block has a mode type MODE_TYPE_ALL or a mode type MODE_TYPE_INTRA and that the first encoding and / or decoding mode is not allowed for the current video block when the current video block has a mode type MODE_TYPE_INTER, wherein a reconstructed image sample matrix of the video image is additionally obtained and an unblocking filter process is applied to at least one edge in the reconstructed image sample matrix, wherein a contour filtering intensity matrix is derived for the unblocking filter process according to a second rule which specifies that bS[ xDi ][ yDj ] equals 0 when a set of conditions is not met, the reconstructed image sample matrix is a reconstructed luma image sample matrix,a variable related to an edge flag is not equal to 2 and two mapping variables for two samples have different values, where bS[ xDi ][ yDj ] denotes an element in the contour filtering intensity matrix for xDi with i = 0..xN and yDj with j = 0..yN, where the two samples are samples from the reconstructed image sample matrix corresponding to bS[ xDi ][ yDj ], and where the two variables indicate prediction modes of two video blocks in the reconstructed image sample matrix containing the two samples, respectively, or the two variables indicate prediction modes of two video sub-blocks split from one or more video blocks in the reconstructed image sample matrix containing the two samples, respectively.
14. A non-transient, computer-readable recording medium, characterized in that it stores a continuous bitstream generated by a method performed by a video processing device, wherein the method comprises: determining, for a current video block of a video image, whether a first encoding and / or decoding mode is applied to the current video block according to a first rule, wherein in the first encoding and / or decoding mode, reconstructed samples are represented by a set of representative color values and the set of representative color values comprises at least one of 1) palette predictors, 2) escaped samples, or 3) palette information included in the continuous bitstream; and generating the continuous bitstream at least based on the determination,wherein the first rule specifies that the first encoding and / or decoding mode is conditionally allowed for the current video block when the current video block has a mode type of Petition 870260068404, dated 10 / 07 / 2026, page 20 / 132 8 / 8 MODE_TYPE_ALL or MODE_TYPE_INTRA and that the first encoding and / or decoding mode is not allowed for the current video block when the current video block has a mode type of MODE_TYPE_INTER, wherein a reconstructed image sample matrix of the video image is additionally obtained and an unblocking filter process is applied to at least one edge in the reconstructed image sample matrix, wherein a contour filtering intensity matrix is derived for the unblocking filter process according to a second rule which specifies that bS[ xDi ][ yDj ] is equal to 0 when a set of conditions is not met,The reconstructed image sample matrix is a reconstructed luma image sample matrix, a variable related to an edge flag is not equal to 2, and two mapping variables for two samples have different values, where bS[xDi][yDj] denotes an element in the contour filtering intensity matrix for xDi with i = 0..xN and yDj with j = 0..yN, where the two samples are samples of the reconstructed image sample matrix corresponding to bS[xDi][yDj], and where the two variables indicate prediction modes of two video blocks in the reconstructed image sample matrix that contain the two samples, respectively, or the two variables indicate prediction modes of two video sub-blocks split from one or more video blocks in the reconstructed image sample matrix that contain the two samples, respectively. Petition 870260068404, dated 10 / 07 / 2026, p. 21 / 132,
