Method, device and storage medium for deriving a value of a first syntax element
By inferring the enable or disable flags of the deblocking filter in VVC, the problem of high bit rate cost and insufficient flexibility of the deblocking filter in VVC is solved, and lower bit rate consumption and higher control flexibility are achieved.
Patent Information
- Application Number
- CN202180025450.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-03-31
- Filing Date
- 2021-01-27
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2041-01-27
AI Technical Summary
In current VVC, the bit rate of deblocking filters is costly and lacks flexibility, so it is impossible to independently enable or disable deblocking filters of different color components, resulting in unnecessary bit rate consumption and control flexibility limited.
By inferring the value of the syntax element, especially when the deblocking offset is not signaled, the derivation method is used to determine the enable or disable flag of the deblocking filter, reducing the bit cost and increasing the flexibility of the deblocking filter control.
Effectively reduce the operating cost of deblocking filter on the decoder side, reduce unnecessary bit rate consumption, and improve flexibility in deblocking filter control.
Smart Images

Figure CN115349261B_ABST
Abstract
Description
Technical Field
[0001] Embodiments related to processing (eg, decoding) of video data are disclosed. Background Art
[0002] 1.HEVC and VVC
[0003] High Efficiency Video Coding (HEVC) is a block-based video codec standardized by ITU-T and MPEG, using temporal prediction and spatial prediction. Spatial prediction is achieved using intra (I) prediction from within the current picture. Temporal prediction is achieved using unidirectional inter (P) prediction or bidirectional inter (B) prediction at the block level based on previously decoded reference pictures. In the encoder, the difference between the original pixel data and the predicted pixel data (called the residual) is transformed into the frequency domain, quantized, and then entropy encoded before being sent together with necessary prediction parameters such as prediction mode and motion vector (which are also entropy encoded). The decoder performs entropy decoding, inverse quantization, and inverse transformation to obtain the residual, and then adds the residual to the intra prediction or inter prediction to reconstruct the picture.
[0004] MPEG and ITU-T are working on a successor technology to HEVC within the Joint Video Exploration Team (JVET). The name of this video codec under development is Versatile Video Coding (VVC). At the time of writing this article, the current version of the VVC draft specification is JVET-Q2001-vD.
[0005] 2. Quantity
[0006] A video (also called a video sequence) comprises a series of pictures (also called images), each of which comprises one or more components. Each component can be described as a two-dimensional rectangular array of sample values. Typically, a picture in a video sequence comprises three components: a luminance component Y, where the sample values are luminance values; and two chrominance components Cb and Cr, where the sample values are chrominance values. It is also common that the size of the chrominance component is half of the luminance component in each dimension. For example, the size of the luminance component of an HD picture will be 1920x1080, while the chrominance components will each have a size of 960x540. Components are sometimes referred to as color components.
[0007] 3. Blocks and Units
[0008] A block is a two-dimensional array of samples. In video coding, each component is divided into blocks, and the coded video bitstream includes a series of coded blocks. Typically, in video coding, a picture is divided into units covering a specific area of the picture. Each unit includes all blocks from all components that make up the specific area, and each block belongs entirely to one unit. Macroblocks in H.264 and coding units (CUs) in HEVC are examples of units.
[0009] Alternatively, a block may be defined as a two-dimensional array to which a transform used in decoding is applied. These blocks are referred to as "transform blocks". Alternatively, a block may be defined as a two-dimensional array to which a single prediction mode is applied. These blocks may be referred to as "prediction blocks". In this application, the word "block" is not tied to one of these definitions, but the description herein may apply to either definition.
[0010] 4. Residual, Transformation, and Quantization
[0011] The residual block may include samples representing the difference in sample values between the sample values of the original source block and the sample values of the predicted block. The residual block is processed using a spatial transform. In the encoder, the transform coefficients are quantized according to a quantization parameter (QP), which controls the precision of the quantization coefficients. The quantized coefficients may be referred to as residual coefficients. A high QP value will result in low precision of the coefficients and, therefore, low fidelity of the residual block. The decoder receives the residual coefficients and applies inverse quantization and inverse transform to derive the residual block.
[0012] 5.NAL Unit
[0013] Both HEVC and VVC define a network abstraction layer (NAL). All data in HEVC and VVC (i.e., both video coding layer (VCL) data and non-VCL data) are encapsulated in NAL units. VCL NAL units contain data representing picture sample values. Non-VCL NAL units contain additional associated data, such as parameter sets and supplementary enhancement information (SEI) messages. The NAL unit in HEVC starts with a header that specifies the NAL unit type, layer ID, and temporary ID to which the NAL unit belongs, where the NAL unit type identifies the type of data carried in the NAL unit. The NAL unit type is sent in the nal_unit_type codeword in the NAL unit header, and the type indicates and defines how the NAL unit should be parsed and decoded. The remaining bytes of the NAL unit are payloads of the type indicated by the NAL unit type. The bitstream may include a series of cascaded NAL units.
[0014] The syntax of the HEVC NAL unit header is shown in Table 1.
[0015] Table 1 HEVC NAL unit header syntax
[0016]
[0017] The syntax of the NAL unit header in the current version of the VVC draft is shown in Table 2.
[0018] Table 2 VVC NAL unit header syntax
[0019]
[0020] The NAL unit types for the current VVC draft are shown in Table 3. The decoding order is the order in which the NAL units should be decoded, which is the same as the order of the NAL units in the bitstream. The decoding order may be different from the output order, which is the order in which the decoded pictures are output by the decoder for example for display.
[0021] Table 3 NAL unit types in VVC
[0022]
[0023]
[0024]
[0025] 6. Slicing
[0026] The concept of slices in HEVC divides a picture into independently coded slices, where decoding of one slice in a picture is independent of other slices of the same picture. Different coding types can be used for slices of the same picture, i.e. a slice can be an I-slice, P-slice or B-slice. One purpose of slices is to enable resynchronization in case of data loss. In HEVC, a slice is a set of CTUs.
[0027] In the current version of VVC, a picture can be divided into raster scan slices or rectangular slices. A raster scan slice includes multiple complete tiles in raster scan order. A rectangular slice includes a group of tiles that together occupy a rectangular area in the picture or a continuously numbered CTU row within a tile. Each slice has a slice header that includes syntax elements. When decoding a slice, the decoded slice header values from these syntax elements are used. Each slice is carried in a VCL NAL unit. In the previous version of the VVC draft specification, slices were called tile groups.
[0028] 7. Picture header
[0029] The current VVC draft includes a picture header (PH), which is a non-VCL_NAL unit with nal_unit_type equal to PH_NUT. The picture header is similar to the slice header, but the values of the syntax elements in the picture header are used to decode all slices of a picture.
[0030] In the current version of VVC, the VCL NAL unit of the coded picture can be preceded by a picture header. The picture header contains parameters that are common to all slices of the associated picture. Some parameters can be signaled in the picture header or in the slice header of each slice in the picture, provided that the presence flag is signaled in the PPS. HEVC does not have a picture header. In the current version of VVC, either a picture header NAL unit exists for each picture, or the picture header syntax exists in the slice header. In the latter case, only one slice is allowed per picture. The picture header and picture header structure syntax in the current version of VVC are shown in Tables 4 and 5 below.
[0031] Table 4 Picture header syntax in VVC
[0032]
[0033] Table 5 Picture header structure syntax in VVC
[0034]
[0035]
[0036]
[0037]
[0038]
[0039]
[0040]
[0041] 8. Slice the header
[0042] Like HEVC, the current VVC draft includes a slice header (SH) for each slice. The slice header includes parameters that are common to all tiles or CTU rows within tiles represented in the slice. In the current version of VVC, some header parameters can be signaled in the picture header or in the slice header, provided that the presence flag is signaled in the picture parameter set. In the current version of VVC, picture header parameters can be signaled in the slice header, provided that the flag picture_header_in_slice_header_flag is signaled in the slice header. The slice header syntax in the current version of VVC is shown in Table 6 below.
[0043] Table 6 Slice header syntax in VVC
[0044]
[0045]
[0046]
[0047]
[0048]
[0049] 9. Parameter Set
[0050] HEVC specifies three types of parameter sets, picture parameter sets (PPS), sequence parameter sets (SPS), and video parameter sets (VPS). The PPS contains data common to the entire picture, the SPS contains data common to the coded video sequence (CVS), and the VPS contains data common to multiple CVSs. VVC also uses these parameter set types. In VVC, there are also adaptation parameter set (APS) and decoding capability information (DCI) NAL units. The APS can contain information that can be used for multiple slices, and two slices of the same picture can use different APSs. The DCI contains information that specifies the "worst case" in terms of profiles and levels that the decoder will encounter throughout the bitstream. The picture parameter set syntax in the current version of VVC is shown below.
[0051] Table 7 PPS syntax
[0052]
[0053]
[0054]
[0055]
[0056]
[0057] 2.1.10 VVC Block Structure
[0058] The VVC video coding standard draft uses a block structure called a quadtree plus binary tree plus ternary tree block structure (QTBT+TT), in which each picture is first divided into square blocks called coding tree units (CTUs). All CTU units are the same size. Each CTU is further divided into coding units (CUs) that can have a square or rectangular shape. The CTU is first divided by a quadtree structure, and then it can be further divided into partitions of equal size vertically or horizontally in a binary structure to form coding units (CUs). Therefore, the block can have a square or rectangular shape. The depth of the quadtree and binary tree can be set by the encoder in the bitstream. Figure 1An example of using QTBT to divide CTU is shown in FIG. Figure 1 The partitioning of a CTU into CUs using QTBT is shown. The ternary tree (TT) part adds the possibility to divide a CU into three partitions instead of two equal-sized partitions; this increases the possibility to use a block structure that better suits the content structure in the picture.
[0059] 11. Deblocking filter
[0060] After the blocks have been reconstructed, deblocking is applied to reduce boundary artifacts between coded blocks.
[0061] Deblocking is first applied to vertical boundaries and then to horizontal boundaries. The boundaries are either transform block boundaries or prediction block boundaries. A deblocking filter boundary strength parameter (bS) is set for each boundary. If the value of bS is greater than 0, deblocking can be applied. The greater the boundary strength, the stronger the filtering is applied. When it has been determined that a deblocking filter should be applied to a boundary, the deblocking process calculates the gradient on each side of the boundary to decide how many samples should be modified on the corresponding side. The decision is represented as a "strong", "weak" or "long tap" deblocking filter decision. For example, the VVC strong / weak filter decisions are shown in the table below and are checked for rows 0 and 3 when filtering the horizontal boundary between two blocks located above / below each other.
[0062] Table 8
[0063]
[0064]
[0065]
[0066] The deblocking filter strength parameter is determined from a specified table based on the quantization parameter Q as a table index. The quantization parameter Q is derived as follows: Q=Clip3(0,63,qP+(slice_beta_offset_div2<<1)), where slice_beta_offset_div2 is the value of the syntax element slice_beta_offset_div2 of the slice containing sample q0,0.
[0067] The deblocking filter strength parameter is determined from a specified table based on the quantization parameter Q as a table index.
[0068] Q=Clip3(0,65,qP+2*(bS-1)+(slice_tc_offset_div2<<1)), where slice_tc_offset_div2 is the value of the syntax element slice_tc_offset_div2 of the slice containing the sample q0,0.
[0069] In addition, qP specifies the average qp of the coding unit that includes the coding block containing samples q0,0 and p0,0. bS specifies the boundary filter strength.
[0070] The following table shows the derivation of threshold variables β′ and tC′ from input Q.
[0071] Table 9 Derivation of threshold variables β′ and tC′ from input Q
[0072] Q 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 <![CDATA[β ′ ]]> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 <![CDATA[t C ′]]> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Q 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 β′ 7 8 9 10 11 12 13 14 15 16 17 18 20 22 24 26 28 <![CDATA[t C ′]]> 0 3 4 4 4 4 5 5 5 5 7 7 8 9 10 10 11 Q 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 β′ 30 32 34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 <![CDATA[t C ′]]> 13 14 15 17 19 21 24 25 29 33 36 41 45 51 57 64 71 Q 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 β′ 64 66 68 70 72 74 76 78 80 82 84 86 88 - - <![CDATA[t C ′]]> 80 89 100 112 125 141 157 177 198 222 250 280 314 352 395
[0073] In HEVC, the deblocking filter parameter offsets of β and tC applied to the Cb and Cr components are not signaled in the bitstream but are set equal to the offset applied to the luma component.
[0074] In VVC, the deblocking filter parameter offsets of β and tC applied to the Y, Cb and Cr components are signaled separately in the bitstream. As shown in the table above, the threshold variables β' and tC' applied to the Cb and Cr components are derived by using the input Q as an index.
[0075] Here, Q applied to the Cb component is derived from β and tC respectively as follows:
[0076] Q=Clip3(0,63,qP+(slice_cb_beta_offset_div2<<1))
[0077] Q=Clip3(0,65,qP+2*(bS-1)+(slice_cb_tc_offset_div2<<1)).
[0078] Furthermore, Q applied to the Cr component is derived from β and tC respectively as follows:
[0079] Q=Clip3(0,63,qP+(slice_cr_beta_offset_div2<<1))
[0080] Q=Clip3(0,65,qP+2*(bS-1)+(slice_cr_tc_offset_div2<<1)). Summary of the invention
[0081] In this document, we use the syntax elements in the picture parameter set (PPS), picture header (PH), and slice header (SH) as examples. These syntax elements include: 1) deblocking parameter offsets of β and tC (divided by 2) applied to the three color components Y, Cb, and Cr (these syntax elements are called "deblocking offsets"); 2) deblocking parameter offsets of β and tC (divided by 2) applied to the Cb and Cr color components (these syntax elements are called "chroma deblocking offsets"); and 3) deblocking parameter offsets of β and tC (divided by 2) applied to the luma component (these syntax elements are called "luma deblocking offsets").
[0082] 1. General grammatical structure issues
[0083] In the current version of VVC, when the first syntax element (referred to as Syntax_A) is not signaled, the value of Syntax_A may be inferred to be equal to the first value. The first value may be a constant value or the value of the second syntax element (referred to as Syntax_B). In other words, when Syntax_A is not signaled, the value of Syntax_A may not be inferred to be equal to the value of the third syntax element (referred to as Syntax_C).
[0084] 2. Signaling issues with deblocking related syntax elements
[0085] In the current version of VVC, the deblocking filter can be enabled / disabled by the syntax elements pps_deblocking_filter_disable_flag, ph_deblocking_filter_disabled_flag, and slice_deblocking_filter_disabled_flag in PPS, PH, and SH, respectively. When one of the flags is signaled and the value is equal to 0, the deblocking offset is signaled accordingly in PPS, PH, and SH. When the deblocking offset is not signaled in the stream, the value of the deblocking offset is inferred as shown in the following table.
[0086] Table 10 Deblocking offset value inference
[0087]
[0088]
[0089] Question 1:
[0090] In the current version of VVC, the deblocking offset is signaled in the PPS when pps_deblocking_filter_disable_flag is present in the PPS and the value is equal to 0. However, when the video source represented by the bitstream consists of only luma samples (monochrome video) or is encoded using three separate color planes (separate_colour_plane_flag is equal to 1), the deblocking filter is not applied to the chroma components (Cb and Cr). The problem with the current version of VVC is that the chroma deblocking offsets must be signaled in the PPS in some cases even if they will not be used in the decoding process, which is an unnecessary bitrate cost.
[0091] Question 2:
[0092] In the current version of VVC, the deblocking offset is signaled separately for the three color components to provide flexibility in controlling the deblocking strength for each color component separately. However, a common deblocking filter setting uses the same deblocking strength for all color components. For example, this is the case with the Common Test Condition (CTC) used in the development of VVC, where the chroma deblocking offset has the same value as the luminance deblocking offset. For this setting, signaling the chroma deblocking offset separately will incur unnecessary bitrate costs. Assuming that the deblocking offset is a syntax element of a signed integer encoded by 0th order Exp-Golomb in the range [-12,12], the bitrate cost becomes as shown in the following table:
[0093] Table 11 Bit cost per deblocking offset
[0094] Bit cost The value of the syntax element 1 {0} 3 {-1,1} 5 {-3,-2,2,3} 7 {-7,-6,-5,-4,4,5,6,7} 9 {-12,-11,-10,-9,-8,8,9,10,11,12}
[0095] When the deblocking offset is signaled in PPS, PH or SH, the bit cost of the chroma deblocking offset is at least 4 bits and at most 36 bits. The bit cost here is calculated as the bit cost of the deblocking offset value shown in the table above multiplied by four, the number of chroma deblocking offset syntax elements.
[0096] Question 3:
[0097] In the current version of VVC, when the deblocking filter is enabled, it means that the deblocking filter is enabled for all color components (e.g., Y, Cb, and Cr). It is not possible to enable the deblocking filter for one or more color components and disable the deblocking filter for the remaining color components. For example, it is not possible to enable the deblocking filter for the luma component and disable the deblocking filter for the chroma components (Cb and Cr).
[0098] The present disclosure proposes solutions to the above-mentioned problems.
[0099] According to a first aspect of the present disclosure, a method for deriving a value of a first syntax element Syntax_A is provided. The method includes determining whether Syntax_A exists in a bitstream. The method includes: as a result of determining that Syntax_A does not exist in the bitstream, if a first condition is satisfied, deriving the value of Syntax_A to be equal to a first value B, or if a second condition is satisfied, deriving the value of Syntax_A to be equal to a second value C.
[0100] According to a second aspect of the present disclosure, there is provided a computer program comprising instructions which, when executed by a processing circuit, cause the processing circuit to perform the method according to the first aspect.
[0101] According to a third aspect of the present disclosure, there is provided a carrier comprising the computer program according to the second aspect, wherein the carrier is one of an electric signal, an optical signal, a radio signal and a computer-readable storage medium.
[0102] According to a fourth aspect of the present disclosure, a device is provided, which is suitable for executing the method according to the first aspect.
[0103] One advantage of an embodiment is the reduction of bit cost by inferring the value of syntax elements using the proposed inference method. Another advantage is the reduction of the operation cost of the deblocking filter at the decoder side by a deblocking filter enable / disable flag. Another advantage is the increased flexibility of the deblocking filter control. BRIEF DESCRIPTION OF THE DRAWINGS
[0104] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate various embodiments.
[0105] Figure 1 An example of partitioning a CTU is shown.
[0106] Figure 2 A system according to an example embodiment is shown.
[0107] Figure 3 is a schematic block diagram of an encoder according to an embodiment.
[0108] Figure 4 is a schematic block diagram of an encoder according to an embodiment.
[0109] Figure 5 is a flow chart illustrating a process according to an embodiment.
[0110] Figure 6 is a flow chart illustrating a process according to an embodiment.
[0111] Figure 7 is a flow chart illustrating a process according to an embodiment.
[0112] Figure 8 is a flow chart illustrating a process according to an embodiment.
[0113] Fig. 9 is a flow chart illustrating a process according to an embodiment.
[0114] Fig.10 is a flow chart illustrating a process according to an embodiment.
[0115] Fig.11 is a flow chart illustrating a process according to an embodiment.
[0116] Fig.12 is a block diagram of an apparatus according to an embodiment. DETAILED DESCRIPTION
[0117] Figure 2 A system 200 is shown according to an example embodiment. The system 200 includes an encoder 202 in communication with a decoder 204 via a network 210 (eg, the Internet or other network).
[0118] Figure 3is a schematic block diagram of an encoder 202 for encoding a block (hereinafter referred to as a "block") of pixel values in a video frame (picture) of a video sequence according to an embodiment. The current block is predicted by performing motion estimation from an already provided block in the same frame or a previous frame by a motion estimator 350. In the case of inter-frame prediction, the result of the motion estimation is a motion or displacement vector associated with a reference block. The motion vector is used by the motion compensator 350 for the inter-frame prediction of the output block. The intra-frame predictor 349 calculates the intra-frame prediction of the current block. The outputs from the motion estimator / compensator 350 and the intra-frame predictor 349 are input in a selector 351, which selects intra-frame prediction or inter-frame prediction for the current block. The output from the selector 351 is input to an error calculator in the form of an adder 341, which also receives the pixel value of the current block. The adder 341 calculates and outputs a residual as the difference in pixel values between the block and its prediction. The error is transformed in a transformer 342 (e.g., by a discrete cosine transform), quantized by a quantizer 343, and then encoded in an encoder 344 (e.g., by an entropy encoder). In inter-frame coding, the estimated motion vector is also taken to the encoder 344 to produce an encoded representation of the current block. The transformed and quantized residual of the current block is also provided to an inverse quantizer 345 and an inverse transformer 346 to retrieve the original residual. The error is added by an adder 347 to the block prediction output from the motion compensator 350 or the intra predictor 349 to create a reference block that can be used for prediction and encoding of the next block. This new reference block is first processed by a deblocking filter unit 330 according to an embodiment in order to perform deblocking filtering to cope with any blocking artifacts. The processed new reference block is then temporarily stored in a frame buffer 348, where it can be used by the intra predictor 349 and the motion estimator / compensator 350.
[0119] Figure 44 is a corresponding schematic block diagram of a decoder 204 according to some embodiments. The decoder 204 includes a decoder 461 (e.g., an entropy decoder) for decoding an encoded representation of a block to obtain a set of quantized and transformed residuals. These residuals are dequantized in an inverse quantizer 462 and inversely transformed by an inverse transformer 463 to obtain a set of residuals. These residuals are added to the pixel values of the reference block in an adder 464. Depending on whether inter-frame prediction or intra-frame prediction is performed, the reference block is determined by a motion estimator / compensator 467 or an intra-frame predictor 466. Thus, a selector 468 is interconnected to the adder 464 as well as the motion estimator / compensator 467 and the intra-frame predictor 466. The resulting decoded block output from the adder 464 is input to the deblocking filter unit 330 according to an embodiment to deblock filter any block artifacts. The filtered block is output from the decoder 504 and is further preferably temporarily provided to the frame buffer 465 and can be used as a reference block for a subsequent block to be decoded. The frame buffer 465 is thereby connected to the motion estimator / compensator 467 so that the stored pixel block can be used for the motion estimator / compensator 467. The output of the adder 464 is preferably also input to the intra predictor 466 to be used as an unfiltered reference block.
[0120] Example
[0121] In the following description, various embodiments are described that solve one or more of the above problems. It should be understood by those skilled in the art that two or more embodiments (or parts of embodiments) can be combined to form new solutions still covered by the present disclosure.
[0122] Embodiment 1 Method for inferring syntax element value
[0123] In a first embodiment, a method for determining a value of a syntax element Syntax_A is proposed. When Syntax_A does not exist, depending on a first condition, the value of Syntax_A is inferred to be equal to value B, wherein value B is derived from at least the value of syntax element Syntax_B, and depending on a second condition, the value of Syntax_A is inferred to be value C, wherein value C is derived from at least the value of syntax element Syntax_C. In other words, when Syntax_A does not exist, the value of Syntax_A can be inferred from the values of at least two different syntax elements.
[0124] Therefore, in one embodiment, the method comprises the following steps.
[0125] Determine the value of the first syntax element (ie, Syntax_C). Determine the value of the second syntax element (ie, Syntax_B). Determine the value of the third syntax element (ie, Syntax_D). Determine whether the fourth syntax element (ie, Syntax_A) is present in the bitstream.
[0126] When it is determined that Syntax_A is not present in the bitstream, then: if the determined value of Syntax_D is equal to a first value, then the value of Syntax_A is inferred to be value B, where value B is derived from at least the determined value of Syntax_B, and if the determined value of Syntax_D is equal to a second value, then the value of Syntax_A is inferred to be value C, where value C is derived from at least the value of Syntax_C.
[0127] In one embodiment, determining the values of Syntax_B and Syntax_C includes: determining whether the syntax element is present in the bitstream; and, if the syntax element is determined not to be present in the bitstream, inferring the value of the syntax element, otherwise, decoding the value of the syntax element.
[0128] In one embodiment, determining the value of Syntax_D includes determining whether the syntax element is present in the bitstream. If Syntax_D is determined to be present in the bitstream, the determined value of Syntax_D is a first value, wherein the first value is a condition (e.g., Syntax_D is present) or the first value is equal to a decoded value of Syntax_D (e.g., 0). If Syntax_D is not present in the bitstream, the determined value of Syntax_D is a second value, wherein the second value is a condition (e.g., Syntax_D is not present) or the second value is equal to an inferred value (e.g., 2).
[0129] The syntax elements Syntax_A, Syntax_B, Syntax_C and Syntax_D may be syntax elements in one or several headers or parameter sets.
[0130] Figure 5 is a flow chart illustrating a process 500 for deriving a value of a syntax element (Syntax_A) according to the above description. The process 500 may be performed by a decoder.
[0131] Step s502 includes deriving a value (D). In one embodiment, deriving D includes: i) if a certain syntax element (Syntax_D) is present in the bitstream and Syntax_D indicates that Syntax_A is included in the bitstream, setting D=X (e.g., 1), ii) if Syntax_D is present in the bitstream and Syntax_D indicates that Syntax_A is not included in the bitstream, setting D=Y (e.g., 0), or iii) otherwise, setting D so that D is not equal to X or Y (e.g., setting D equal to Z).
[0132] Step s504 includes determining whether D is equal to X. If D is equal to X, the process proceeds to step s506, otherwise the process proceeds to step s508.
[0133] Step s506 comprises setting the value of Syntax_A equal to ValueA, wherein ValueA is the decoded value of Syntax_A.
[0134] Step s508 comprises determining whether D is equal to Y. If D is equal to Y, the process proceeds to step s510, otherwise the process proceeds to step s512.
[0135] Step s510 comprises setting the value of Syntax_A equal to valueB, where valueB is a value associated with Syntax_B (eg, B may be equal to the decoded value of Syntax_B).
[0136] Step s512 comprises setting the value of Syntax_A equal to value C, where value C is the value associated with Syntax_C (eg, C may be equal to the decoded value of Syntax_C).
[0137] Figure 6 is a flow chart illustrating a process 600 for deriving a value for a syntax element (Syntax_A) (also referred to as the "sixth" syntax element). Process 600 may be performed by a decoder.
[0138] Step s602 comprises determining whether a first syntax element Syntax_C is present in the bitstream. If Syntax_C is present, the process proceeds to step s604, otherwise the process proceeds to step s606.
[0139] Step s604 (Syntax_C exists) comprises decoding the first syntax element Syntax_C and deriving a first value equal to the value of the decoded first syntax element Syntax_C.
[0140] Step s606 (Syntax_C does not exist) comprises deriving that the first value is equal to a second value, wherein the second value may be a constant value, or the second value may be a value of a second syntax element.
[0141] Step s608 comprises determining whether a third syntax element Syntax_B is present in the bitstream. If Syntax_B is present, the process proceeds to step s610, otherwise the process proceeds to step s612.
[0142] Step s610 (Syntax_B exists) comprises decoding the third syntax element Syntax_B and deriving a third value equal to the value of the decoded third syntax element Syntax_B.
[0143] Step s612 (Syntax_B does not exist) comprises deriving the third value to be equal to a fourth value, wherein the fourth value may be a constant value, or the fourth value may be a value of a fourth syntax element.
[0144] Step s614 comprises determining whether a fifth syntax element Syntax_D is present in the bitstream. If Syntax_D is present, the process proceeds to step s616, otherwise the process proceeds to step s624.
[0145] Step s616 (Syntax_D present) comprises decoding the fifth syntax element Syntax_D and deriving a fifth value equal to the value of the decoded fifth syntax element Syntax_D, wherein the fifth value indicates whether the sixth syntax element Syntax_A is present in the bitstream.
[0146] Step s618 comprises determining whether Syntax_A is present in the bitstream based on the fifth value. If Syntax_A is present, the process proceeds to step s620, otherwise the process proceeds to step s622.
[0147] Step s620 (Syntax_A exists) comprises decoding the sixth syntax element Syntax_A and deriving a sixth value equal to the value of the decoded sixth syntax element Syntax_A.
[0148] Step s622 (Syntax_A does not exist) comprises deriving the sixth value to be equal to the third value, wherein the third value is the value of the third syntax element Syntax_B.
[0149] Step s624 (Syntax_D does not exist) comprises deriving a sixth value equal to a first value, wherein the first value is the value of the first syntax element Syntax_C.
[0150] Step s626 comprises decoding the picture using the sixth value in the process, wherein Syntax_A, Syntax_B, Syntax_C, Syntax_D are four different syntax elements.
[0151] Figure 7 is a flow chart illustrating a process 700 for inferring a value of a syntax element (Syntax_A). The process 700 may be performed by a decoder.
[0152] Step s702 comprises determining whether a first syntax element Syntax_C is present in the bitstream. If Syntax_C is present, the process proceeds to step s704, otherwise the process proceeds to step s706.
[0153] Step s704 (Syntax_C exists) comprises decoding the first syntax element Syntax_C and deriving a first value equal to the value of the decoded first syntax element Syntax_C.
[0154] Step s706 (Syntax_C is not present) comprises deriving that the first value is equal to a second value, wherein the second value may be a constant value, or the second value may be a value of a second syntax element.
[0155] Step s708 comprises determining whether a third syntax element Syntax_B is present in the bitstream. If Syntax_B is present, the process proceeds to step s710, otherwise the process proceeds to step s712.
[0156] Step s710 (Syntax_B exists) comprises decoding the third syntax element Syntax_B and deriving a third value equal to the value of the decoded third syntax element Syntax_B.
[0157] Step s712 (Syntax_B does not exist) comprises deriving the third value to be equal to a fourth value, wherein the fourth value may be a constant value, or the fourth value may be a value of a fourth syntax element.
[0158] Step s714 comprises determining whether a fifth syntax element Syntax_D is present in the bitstream. If Syntax_D is present, the process proceeds to step s716, otherwise the process proceeds to step s718.
[0159] Step s716 (Syntax_D present) comprises decoding the fifth syntax element Syntax_D and deriving a fifth value equal to the value of the decoded fifth syntax element Syntax_D, wherein the fifth value indicates whether the sixth syntax element Syntax_A is present in the bitstream.
[0160] Step s718 (Syntax_D not present) comprises deriving the fifth value to be equal to the sixth value, wherein the sixth value may be a constant value, or the sixth value may be the value of a sixth syntax element.
[0161] Step s720 includes determining whether a seventh syntax element Syntax_A is present in the bitstream based on the fifth value (e.g., if the fifth value is equal to the value of X (e.g., X=1)), this specifies that Syntax_A is present in the bitstream. If Syntax_A is present, the process proceeds to step s722, otherwise the process proceeds to step s724.
[0162] Step s722 (Syntax_A exists) comprises decoding the seventh syntax element Syntax_A and deriving a seventh value equal to the value of the decoded seventh syntax element Syntax_A.
[0163] Step s724 (Syntax_A does not exist) includes determining whether the fifth value is equal to the ninth value (denoted as Y). If the fifth value is equal to Y, the value of the seventh syntax element Syntax_A should be inferred to be equal to the value of the third syntax element Syntax_B. If the fifth value is equal to Y, the process proceeds to step s726, otherwise the process proceeds to step s728.
[0164] Step s726 comprises deriving the seventh value to be equal to the third value, wherein the third value is the value of the third syntax element Syntax_B.
[0165] Step s728 comprises deriving the seventh value to be equal to the first value, wherein the first value is the value of the first syntax element Syntax_C.
[0166] Step s730 comprises decoding the picture using the seventh value in the process, wherein Syntax_A, Syntax_B, Syntax_C, Syntax_D are four different syntax elements.
[0167] Use Case 1( Figure 8 ) Infer the value of the chroma deblocking offset in PH
[0168] In this use case, a presence flag (which corresponds to the above-mentioned Syntax_D) is added to the PH, which indicates whether the chroma deblocking offsets (which corresponds to Syntax_A) are present in the PH. This flag may be referred to, for example, as ph_deblocking_chroma_offsets_present_flag. When the proposed flag is equal to a first value (e.g., 1), it is determined that the chroma deblocking offsets are signaled in the bitstream. When the proposed flag is present and the value of the flag is equal to a second value (e.g., 0), it is determined that the chroma deblocking offsets are not signaled but are set to the value equal to the luma deblocking offset in the PH. When the proposed flag is not present, it is determined that the chroma deblocking offsets are not signaled but should be set to the value equal to the chroma deblocking offset in the PPS.
[0169] The method proposed in this use case is based on Embodiment 1 in the following manner: when Syntax_A does not exist and the determined value of Syntax_D is equal to the first value (e.g., the first value is that Syntax_D exists), the value of Syntax_A is inferred to be the value of Syntax_B, and if the determined value of Syntax_D is equal to the second value (e.g., the second value is that Syntax_D does not exist), the value of Syntax_A is inferred to be the value of Syntax_C, where Syntax_A represents one of four syntax elements: ph_cb_beta_offset_div2, ph_cb_tc_offset_div2, ph_cr_beta_offset_div2, or ph_cr_tc_offset_div2. Below we take setting Syntax_A equal to the ph_cb_beta_offset_div2 syntax element as an example to show the syntax structure pseudo code:
[0170]
[0171]
[0172] In another version of this embodiment, at least one of Syntax_B, Syntax_C, and Syntax_D is a constant value
[0173] In another version of this embodiment, at least one of Syntax_B, Syntax_C, and Syntax_D is a value derived from one or more syntax elements in the bitstream.
[0174] Below is example syntax and semantics for use case 1.
[0175] Table 14
[0176]
[0177]
[0178] deblocking_filter_control_present_flag equal to 1 specifies that the deblocking filter control syntax element is present in the PPS. deblocking_filter_control_present_flag equal to 0 specifies that the deblocking filter control syntax element is not present in the PPS.
[0179] deblocking_filter_override_enabled_flag equal to 1 specifies that ph_deblocking_filter_override_flag is present in the PH referencing the PPS or slice_deblocking_filter_override_flag is present in the slice header referencing the PPS. deblocking_filter_override_enabled_flag equal to 0 specifies that ph_deblocking_filter_override_flag is not present in the PH referencing the PPS or slice_deblocking_filter_override_flag is not present in the slice header referencing the PPS. When not present, the value of deblocking_filter_override_enabled_flag is inferred to be equal to 0.
[0180] pps_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter should not be applied to slices that reference a PPS where slice_deblocking_filter_disabled_flag is not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter should be applied to slices that reference a PPS where slice_deblocking_filter_disabled_flag is not present. When not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0. In some embodiments, pps_deblocking_filter_disabled_flag is replaced with pps_deblocking_filter_enabled_flag, which is equivalent to !pps_deblocking_filter_disabled_flag. Thus, pps_deblocking_filter_enabled_flag equal to 0 specifies that the operation of the deblocking filter should not be applied to slices referencing a PPS where slice_deblocking_filter_disabled_flag is not present; pps_deblocking_filter_enabled_flag equal to 1 specifies that the operation of the deblocking filter should be applied to slices referencing a PPS where slice_deblocking_filter_disabled_flag is not present. When not present, the value of pps_deblocking_filter_enabled_flag is inferred to be equal to 1.
[0181] pps_beta_offset_div2 and pps_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the luma component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_beta_offset_div2 and pps_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of pps_beta_offset_div2 and pps_tc_offset_div2 are both inferred to be equal to 0.
[0182] pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the Cb component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or the slice header of the slice referencing the PPS. The values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are both inferred to be equal to 0.
[0183] pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 specify the default deblocking parameter offsets for beta and tC (divided by 2) applied to the Cr component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or the slice header of the slice referencing the PPS. The values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are both inferred to be equal to 0.
[0184] Table 15
[0185]
[0186]
[0187] ph_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in PH. ph_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in PH. When not present, the value of ph_deblocking_filter_override_flag is inferred to be equal to 0.
[0188] ph_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is not applied to the slices associated with the PH. ph_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is applied to the slices associated with the PH. When ph_deblocking_filter_disabled_flag is not present, it is inferred to be equal to pps_deblocking_filter_disabled_flag. In some embodiments, ph_deblocking_filter_disabled_flag is replaced by ph_deblocking_filter_enabled_flag, which is equivalent to !ph_deblocking_filter_disabled_flag. Therefore, ph_deblocking_filter_enabled_flag equal to 0 specifies that the operation of the deblocking filter is not applied to the slices associated with the PH; ph_deblocking_filter_enabled_flag equal to 1 specifies that the operation of the deblocking filter is applied to the slices associated with the PH. When ph_deblocking_filter_enabled_flag is not present, it is inferred to be equal to ! pps_deblocking_filter_disabled_flag or it is inferred to be equal to pps_deblocking_filter_enabled_flag.
[0189] ph_beta_offset_div2 and ph_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the luma component of the slice associated with the PH. The values of ph_beta_offset_div2 and ph_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of ph_beta_offset_div2 and ph_tc_offset_div2 are inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively.
[0190] ph_deblocking_chroma_offsets_present_flag equal to 1 specifies that deblocking parameter offsets of β and tC (divided by 2) applied to Cb and Cr components are present in the PH. ph_deblocking_chroma_offsets_present_flag equal to 0 specifies that deblocking parameter offsets of β and tC (divided by 2) applied to Cb and Cr components are not present in the PH. When not present, the value of ph_deblocking_chroma_offsets_present_flag is inferred to be equal to 0.
[0191] ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 specify the deblocking parameter offsets of β and tC (divided by 2) applied to the Cb component of the slice associated with the PH. The values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred as follows: 1) when ph_deblocking_chroma_offsets_present_flag is present, the values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred to be equal to ph_beta_offset_div2 and ph_tc_offset_div2, respectively; and 2) when ph_deblocking_chroma_offsets_present_flag is not present, the values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred to be equal to pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2, respectively.
[0192] ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cr components of the slice associated with the PH. The values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred as follows: 1) when ph_deblocking_chroma_offsets_present_flag is present, the values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred to be equal to ph_beta_offset_div2 and ph_tc_offset_div2, respectively; and 2) when ph_deblocking_chroma_offsets_present_flag is not present, the values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred to be equal to pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2, respectively.
[0193] This structure can be seen by referring to the syntax table above. Figure 8 The following decoding flowchart is shown for explanation.
[0194] Step s802 comprises determining the value of pps_cb_beta_offset_div2.
[0195] Step s804 includes determining whether ph_beta_offset_div2 is present in the bitstream. If so, the process 800 proceeds to step s806, otherwise to step s818. In an alternative embodiment, step s804 includes determining whether a certain flag (e.g., ph_deblocking_filter_disabled_flag or ph_deblocking_filter_enabled_flag) is equal to v1 or v2, wherein v1 is a first value and v2 is a second value, and v2 is not equal to v1. When the certain flag exists and has a value equal to v1, the process 800 proceeds to step s806, otherwise (the flag does not exist or exists but has a value equal to v2), the process 800 proceeds to step s818. In an embodiment where the certain flag is ph_deblocking_filter_disabled_flag, v1=0 and v2=1. In an embodiment where the certain flag is ph_deblocking_filter_enabled_flag, v1=1 and v2=0.
[0196] Step s806 includes decoding ph_beta_offset_div2.
[0197] Step s808 includes determining whether ph_deblocking_chroma_offsets_present_flag is present in the bitstream. If so, the process 800 proceeds to step s810, otherwise the process 800 proceeds to step s818. In an alternative embodiment, step s808 includes determining whether chromaArrayType is equal to 0. When chromaArrayType is equal to 0, the process 800 proceeds to step s818, otherwise (chromaArrayType is not equal to 0), the process 800 proceeds to step s810.
[0198] Step s810 comprises decoding ph_deblocking_chroma_offsets_present_flag.
[0199] Step s812 includes determining whether ph_deblocking_chroma_offsets_present_flag is equal to 1. If so, the process 800 proceeds to step s814, otherwise the process 800 proceeds to step s816.
[0200] Step s814 comprises decoding ph_cb_beta_offset_div2.
[0201] Step s816 comprises inferring ph_cb_beta_offset_div2 to be equal to the value of ph_beta_offset_div2.
[0202] Step s818 comprises inferring ph_cb_beta_offset_div2 to be equal to the value of pps_cb_beta_offset_div2.
[0203] Use Case 2 Fig. 9 ): Infer the value of the chroma deblocking offset in SH
[0204] It is proposed to add a presence flag to the SH, which indicates whether the chroma deblocking offsets are present in the SH. The flag may be called slice_deblocking_chroma_offsets_present_flag, for example. When the proposed flag is equal to a first value (e.g., 1), it is determined that the chroma deblocking offsets are signaled in the bitstream. When the proposed flag is present and the value of the flag is equal to a second value (e.g., 0), it is determined that the chroma deblocking offsets are not signaled but are set to the value of the luma deblocking offsets in the SH. When the proposed flag is not present, it is determined that the chroma deblocking offsets are not signaled but are set to the value of the chroma deblocking offsets in the PH.
[0205] The proposed method is based on Embodiment 1 in the following manner: when Syntax_A does not exist and the determined value of Syntax_D is equal to the first value (e.g., the first value is that Syntax_D exists), the value of Syntax_A is inferred to be the value of Syntax_B, and if the determined value of Syntax_D is equal to the second value (e.g., the second value is that Syntax_D does not exist), the value of Syntax_A is inferred to be the value of Syntax_C, where Syntax_A represents one of four syntax elements: slice_cb_beta_offset_div2, slice_cb_tc_offset_div2, slice_cr_beta_offset_div2, or slice_cr_tc_offset_div2. Here we use Syntax_A to represent slice_cb_beta_offset_div2 as an example to show the syntax structure pseudo code:
[0206]
[0207] In another version of this embodiment, at least one of Syntax_B, Syntax_C, and Syntax_D is a constant value or a value derived from one or more syntax elements in the bitstream. The following is an example syntax and semantics for this use case.
[0208] Table 16
[0209]
[0210]
[0211] deblocking_filter_control_present_flag equal to 1 specifies that the deblocking filter control syntax element is present in the PPS. deblocking_filter_control_present_flag equal to 0 specifies that the deblocking filter control syntax element is not present in the PPS.
[0212] deblocking_filter_override_enabled_flag equal to 1 specifies that ph_deblocking_filter_override_flag is present in the PH referencing the PPS or slice_deblocking_filter_override_flag is present in the slice header referencing the PPS. deblocking_filter_override_enabled_flag equal to 0 specifies that ph_deblocking_filter_override_flag is not present in the PH referencing the PPS or slice_deblocking_filter_override_flag is not present in the slice header referencing the PPS. When not present, the value of deblocking_filter_override_enabled_flag is inferred to be equal to 0.
[0213] pps_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter should not be applied to slices that reference a PPS in which slice_deblocking_filter_disabled_flag is not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter should be applied to slices that reference a PPS in which slice_deblocking_filter_disabled_flag is not present. When not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0. As described above, pps_deblocking_filter_disabled_flag can be replaced with pps_deblocking_filter_enbabled_flag. As described above, pps_deblocking_filter_disabled_flag can be replaced with pps_deblocking_filter_enbabled_flag.
[0214] pps_beta_offset_div2 and pps_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the luma component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_beta_offset_div2 and pps_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of pps_beta_offset_div2 and pps_tc_offset_div2 are both inferred to be equal to 0.
[0215] pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the Cb component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or the slice header of the slice referencing the PPS. The values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are both inferred to be equal to 0.
[0216] pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 specify the default deblocking parameter offsets for beta and tC (divided by 2) applied to the Cr component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or the slice header of the slice referencing the PPS. The values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are both inferred to be equal to 0.
[0217] Table 17
[0218]
[0219]
[0220] slice_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in the slice header. slice_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in the slice header. When not present, the value of slice_deblocking_filter_override_flag is inferred to be equal to ph_deblocking_filter_override_flag.
[0221] slice_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is not applied to the current slice. slice_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is applied to the current slice. When slice_deblocking_filter_disabled_flag is not present, it is inferred to be equal to ph_deblocking_filter_disabled_flag, or it is inferred to be equal to !ph_deblocking_filter_enabled_flag. slice_deblocking_filter_disabled_flag may be replaced by slice_deblocking_filter_enabled_flag which is equivalent to !slice_deblocking_filter_disabled_flag.
[0222] slice_beta_offset_div2 and slice_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the luma component of the current slice. The values of slice_beta_offset_div2 and slice_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of slice_beta_offset_div2 and slice_tc_offset_div2 are inferred to be equal to ph_beta_offset_div2 and ph_tc_offset_div2, respectively.
[0223] slice_deblocking_chroma_offsets_present_flag equal to 1 specifies that the deblocking parameter offsets of β and tC (divided by 2) applied to the Cb and Cr components are present in the slice header. slice_deblocking_chroma_offsets_present_flag equal to 0 specifies that the deblocking parameter offsets of β and tC (divided by 2) applied to the Cb and Cr components are not present in the slice header. When not present, the value of slice_deblocking_chroma_offsets_present_flag is inferred to be equal to 0.
[0224] slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cb component of the current slice. The values of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 are inferred as follows: i) when slice_deblocking_chroma_offsets_present_flag is present, the values of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 are inferred to be equal to slice_beta_offset_div2 and slice_tc_offset_div2, respectively; and 2) when slice_deblocking_chroma_offsets_present_flag is not present, the values of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 are inferred to be equal to ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2, respectively.
[0225] slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cr components of the current slice. The values of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 are inferred as follows: i) when slice_deblocking_chroma_offsets_present_flag is present, the values of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 are inferred to be equal to slice_beta_offset_div2 and slice_tc_offset_div2, respectively; and 2) when slice_deblocking_chroma_offsets_present_flag is not present, the values of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 are inferred to be equal to ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2, respectively.
[0226] This structure can be seen by referring to the syntax table above. Fig. 9 The following decoding flowchart is shown for explanation.
[0227] Step s902 comprises determining the value of ph_cb_beta_offset_div2.
[0228] Step s904 includes determining whether slice_beta_offset_div2 is present in the bitstream. If so, the process 900 proceeds to step s906, otherwise the process 900 proceeds to step s918. In an alternative embodiment, step s804 includes determining whether a certain flag (e.g., slice_deblocking_filter_disabled_flag or slice_deblocking_filter_enabled_flag) is equal to v1 or v2, where v1 is a first value and v2 is a second value, and v2 is not equal to v1. When the certain flag exists and has a value equal to v1 (e.g., 0), the process 900 proceeds to step s906, otherwise (the flag does not exist or exists but has a value equal to v2), the process 900 proceeds to step s918. In an embodiment where the certain flag is slice_deblocking_filter_disabled_flag, v1=0 and v2=1. In an embodiment where the certain flag is slice_deblocking_filter_enabled_flag, v1=1 and v2=0.
[0229] Step s906 includes decoding slice_beta_offset_div2.
[0230] Step s908 includes determining whether slice_deblocking_chroma_offsets_present_flag is present in the bitstream. If so, process 900 proceeds to step s910, otherwise process 900 proceeds to step s918. In an alternative embodiment, step s904 includes determining whether chromaArrayType is equal to 0 or equal to 1. When chromaArrayType is equal to 0, process 900 proceeds to step s918, otherwise (chromaArrayType is not equal to 0), process 900 proceeds to step s910.
[0231] Step s910 comprises decoding slice_deblocking_chroma_offsets_present_flag.
[0232] Step s912 includes determining whether slice_deblocking_chroma_offsets_present_flag is equal to 1. If so, the process 900 proceeds to step s914, otherwise the process 900 proceeds to step s916.
[0233] Step s914 comprises decoding slice_cb_beta_offset_div2.
[0234] Step s916 comprises inferring slice_cb_beta_offset_div2 to be equal to the value of slice_beta_offset_div2.
[0235] Step s918 comprises inferring slice_cb_beta_offset_div2 to be equal to the value of ph_cb_beta_offset_div2.
[0236] Use case 3: Inferring the value of chroma deblocking offset in PPS
[0237] It is proposed to add a presence flag to the PPS, which indicates whether the chroma deblocking offsets are present in the PPS. The flag may be called, for example, pps_deblocking_chroma_offsets_present_flag. When the proposed flag is equal to a first value (e.g., 1), it is determined that the chroma deblocking offsets are signaled in the bitstream. When the proposed flag is present and the value is equal to a second value (e.g., 0), it is determined that the chroma deblocking offsets are not signaled but are set to be equal to the value of the luma deblocking offset in the PPS. When the proposed flag is not present, it is determined that the chroma deblocking offsets are not signaled but are set to be equal to 0.
[0238] The following is an example syntax and semantics for this use case.
[0239] Table 18
[0240]
[0241]
[0242] deblocking_filter_control_present_flag equal to 1 specifies that the deblocking filter control syntax element is present in the PPS. deblocking_filter_control_present_flag equal to 0 specifies that the deblocking filter control syntax element is not present in the PPS.
[0243] deblocking_filter_override_enabled_flag equal to 1 specifies that ph_deblocking_filter_override_flag is present in the PH referencing the PPS or slice_deblocking_filter_override_flag is present in the slice header referencing the PPS. deblocking_filter_override_enabled_flag equal to 0 specifies that ph_deblocking_filter_override_flag is not present in the PH referencing the PPS or slice_deblocking_filter_override_flag is not present in the slice header referencing the PPS. When not present, the value of deblocking_filter_override_enabled_flag is inferred to be equal to 0.
[0244] pps_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter should not be applied to slices referencing a PPS where slice_deblocking_filter_disabled_flag is not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter should be applied to slices referencing a PPS where slice_deblocking_filter_disabled_flag is not present. When not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0.
[0245] pps_beta_offset_div2 and pps_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the luma component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_beta_offset_div2 and pps_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of pps_beta_offset_div2 and pps_tc_offset_div2 are both inferred to be equal to 0.
[0246] pps_deblocking_chroma_offsets_present_flag equal to 1 specifies that deblocking parameter offsets for β and tC (divided by 2) applied to the Cb and Cr components are present in the PPS. pps_deblocking_chroma_offsets_present_flag equal to 0 specifies that deblocking parameter offsets for β and tC (divided by 2) applied to the Cb and Cr components are not present in the PPS. When not present, the value of pps_deblocking_chroma_offsets_present_flag is inferred to be equal to 0. When ChromaArrayType is equal to 0, the value of pps_deblocking_chroma_offsets_present_flag shall be equal to 0.
[0247] pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 specify the default deblocking parameter offsets for beta and tC (divided by 2) applied to the Cb component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are inferred as follows: i) when pps_deblocking_chroma_offsets_present_flag is present, the values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively; and 2) when pps_deblocking_chroma_offsets_present_flag is not present, the values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are both inferred to be equal to 0.
[0248] pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 specify the default deblocking parameter offsets for beta and tC (divided by 2) applied to the Cr component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are inferred as follows: 1) when pps_deblocking_chroma_offsets_present_flag is present, the values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively; and 2) when pps_deblocking_chroma_offsets_present_flag is not present, the values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are both inferred to be equal to 0.
[0249] This embodiment discloses a novel syntax structure and method for inferring a value when a syntax element is not present. The novel element here is a way to infer the value of a syntax element that is not present in the bitstream. In short, if the syntax element is present, the value is derived to be equal to the value of the decoded syntax element. However, if the syntax element is not present, the value is set equal to value A or value B depending on whether another syntax element is present in the bitstream.
[0250] Although the novel structure is shown above in a picture parameter set (PPS), the structure is not limited to PPS. The structure can be used for example for a sequence parameter set, a picture parameter set, a slice header, a video parameter set, decoding capability information, an adaptation parameter set, supplemental enhancement information, or a picture header.
[0251] You can refer to the syntax table above. Fig.10 The following decoding method flow chart is shown to illustrate the structure. Fig.10 A process 1000 is shown according to an embodiment.
[0252] Step s1002 of process 1000 includes determining whether a luma deblocking offset is present in the PPS. In one embodiment, determining whether a luma deblocking offset is present in the PPS includes determining whether the value of pps_deblocking_filter_disabled_flag is equal to 0 or equal to 1. Here, 0 indicates that a luma deblocking offset is present, but the flag may alternatively be implemented in the opposite manner (where a value of 1 indicates that a luma deblocking offset is present). If a luma deblocking offset is present, the process proceeds to step s1004, otherwise the process proceeds to step s1014.
[0253] Step s1004 comprises decoding a luma deblocking offset from the bitstream and also decoding a presence flag.
[0254] Step s1008 comprises determining whether the presence flag specifies that a chroma deblocking offset is present. If the presence flag specifies that a chroma deblocking offset is present, the process proceeds to step s1010, otherwise the process proceeds to step s1012.
[0255] Step s1010 (ie, chroma deblocking offset exists) includes decoding the chroma deblocking offset (eg, decoding pps_cb_beta_offset_div2).
[0256] Step s1012 (ie, chroma deblocking offset is not present) comprises inferring the value of the chroma deblocking offset to be equal to the value of the luma deblocking offset (eg, inferring pps_cb_beta_offset_div2 to be equal to the value of pps_beta_offset_div2).
[0257] Step s1014 (ie, luma deblocking offset not present) comprises inferring that the chroma deblocking offset is equal to zero.
[0258] Step s1016 comprises using the chroma deblocking offsets in the process to decode the picture.
[0259] The novel structure can be used to signal other values than deblocking filter parameters. Fig.11 A general structure is shown in a flowchart of a process 1100 according to an embodiment. A decoder may perform all or a subset of the following steps in the general embodiment to decode a picture from a bitstream.
[0260] Step s1102 comprises determining whether a first syntax element S1 is present in the bitstream. If S1 is in the bitstream, the process proceeds to step s1104, otherwise the process proceeds to step s1112.
[0261] Step s1104 (ie S1 is determined to be present in the bitstream) comprises decoding the first syntax element S1 and deriving a first value equal to the value of the decoded first syntax element S1.
[0262] Step s1106 comprises decoding a first presence flag value from a second syntax element S2 in the bitstream, wherein the first presence flag value indicates whether a third syntax element S3 is present in the bitstream.
[0263] Step s1107 comprises using the first presence flag to determine whether S3 is present in the bitstream. If S3 is present, the process proceeds to step s1108, otherwise the process proceeds to step s1110.
[0264] Step s1108 (ie the first presence flag value indicates that the third syntax element S3 is present in the bitstream) comprises decoding the third syntax element S3 and deriving a third value equal to the value of the decoded third syntax element S3.
[0265] Step s1110 (ie the first presence flag value indicates that the third syntax element S3 is present in the bitstream) comprises deriving the third value to be equal to the second value.
[0266] Step s1112 (ie, S1 is determined not to be present in the bitstream) comprises deriving that the third value is equal to the fourth value.
[0267] Step s1114 comprises decoding the picture using the third value in the process, wherein the first syntax element (S1), the second syntax element (S2) and the third syntax element (S3) are three different syntax elements.
[0268] Use case 5: Alternative method for indicating the presence and inference of chroma deblocking offset
[0269] In other use cases described herein, the presence of chroma deblocking offsets is conditional, based on the values of pps_deblocking_chroma_offsets_present_flag, ph_deblocking_chroma_offsets_present_flag, and slice_deblocking_chroma_offsets_present_flag in PPS, PH, and SH, respectively.
[0270] In this use case, alternative methods to indicate the presence and inference of chroma deblocking offsets are proposed. It is proposed to add a syntax element to each of PPS, PH and SH indicating whether chroma deblocking offsets are present in PPS, PH, SH or not present at all.
[0271] The syntax elements may be referred to as pps_deblocking_chroma_offsets_present_idc, ph_deblocking_chroma_offsets_present_idc, and slice_deblocking_chroma_offsets_present_idc. When the proposed syntax element is equal to a first value (e.g., 1), it is determined that the chroma deblocking offsets are signaled in the corresponding syntax structure (PPS, PH, or SH). When the proposed syntax element is equal to a second value (e.g., 0), it is determined that the chroma deblocking offsets are not signaled but are set equal to the value of the luma deblocking offset of the corresponding syntax structure (PPS, PH, or SH). When the proposed syntax element is equal to a third value (e.g., 2), it is determined that the chroma deblocking offsets are not signaled, and the values of the chroma deblocking offsets are inferred as in the current VVC draft standard. This may mean that the value in SH is inferred from PH, and the value in PH is inferred from PPS. Alternatively, the value in SH is inferred from PPS. When the proposed syntax element is not present, we recommend that the value be inferred to be equal to 2.
[0272] The proposed method is based on Embodiment 1 in the following manner: when Syntax_A does not exist and the determined value of Syntax_D is equal to a first value (e.g., 0), the value of Syntax_A is inferred to be the value of Syntax_B, and if the determined value of Syntax_D is equal to a second value (e.g., 2), the value of Syntax_A is inferred to be the value of Syntax_C, where Syntax_A represents one of the chroma deblocking offsets. Here we use Syntax_A to represent ph_cb_beta_offset_div2 as an example to show the syntax structure pseudo code:
[0273]
[0274] In another version of this embodiment, at least one of Syntax_B, Syntax_C, and Syntax_D is a constant value.
[0275] In another version of this embodiment, at least one of Syntax_B, Syntax_C, and Syntax_D is a value derived from one or more syntax elements in the bitstream.
[0276] Below is the example syntax and semantics. Here we use PH as an example.
[0277] Table 19
[0278]
[0279] deblocking_filter_control_present_flag equal to 1 specifies that the deblocking filter control syntax element is present in the PPS. deblocking_filter_control_present_flag equal to 0 specifies that the deblocking filter control syntax element is not present in the PPS.
[0280] deblocking_filter_override_enabled_flag equal to 1 specifies that ph_deblocking_filter_override_flag is present in the PH referencing the PPS or slice_deblocking_filter_override_flag is present in the slice header referencing the PPS. deblocking_filter_override_enabled_flag equal to 0 specifies that ph_deblocking_filter_override_flag is not present in the PH referencing the PPS or slice_deblocking_filter_override_flag is not present in the slice header referencing the PPS. When not present, the value of deblocking_filter_override_enabled_flag is inferred to be equal to 0.
[0281] pps_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter should not be applied to slices referencing a PPS where slice_deblocking_filter_disabled_flag is not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter should be applied to slices referencing a PPS where slice_deblocking_filter_disabled_flag is not present. When not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0.
[0282] pps_beta_offset_div2 and pps_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the luma component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_beta_offset_div2 and pps_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of pps_beta_offset_div2 and pps_tc_offset_div2 are both inferred to be equal to 0.
[0283] pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the Cb component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or the slice header of the slice referencing the PPS. The values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are both inferred to be equal to 0.
[0284] pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 specify the default deblocking parameter offsets for beta and tC (divided by 2) applied to the Cr component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or the slice header of the slice referencing the PPS. The values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are both inferred to be equal to 0.
[0285] Table 20
[0286]
[0287] ph_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in PH. ph_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in PH. When not present, the value of ph_deblocking_filter_override_flag is inferred to be equal to 0.
[0288] ph_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is not applied to the slices associated with the PH. ph_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is applied to the slices associated with the PH. When ph_deblocking_filter_disabled_flag is not present, it is inferred to be equal to pps_deblocking_filter_disabled_flag. As described above, in some embodiments, ph_deblocking_filter_disabled_flag is replaced with ph_deblocking_filter_enabled_flag.
[0289] ph_beta_offset_div2 and ph_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the luma component of the slice associated with the PH. The values of ph_beta_offset_div2 and ph_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of ph_beta_offset_div2 and ph_tc_offset_div2 are inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively.
[0290] ph_deblocking_chroma_offsets_present_idc equal to 1 specifies that deblocking parameter offsets of β and tC (divided by 2) applied to Cb and Cr components are present in the PH. ph_deblocking_chroma_offsets_present_idc equal to 0 or 2 specifies that deblocking parameter offsets of β and tC (divided by 2) applied to Cb and Cr components are not present in the PH. When not present, the value of ph_deblocking_chroma_offsets_present_idc is inferred to be equal to 2.
[0291] ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 specify the deblocking parameter offsets of β and tC (divided by 2) applied to the Cb component of the slice associated with the PH. The values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred as follows: i) when ph_deblocking_chroma_offsets_present_idc is equal to 0, the values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred to be equal to ph_beta_offset_div2 and ph_tc_offset_div2, respectively; and 2) when ph_deblocking_chroma_offsets_present_idc is equal to 2, the values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred to be equal to pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2, respectively.
[0292] ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cr components of the slice associated with the PH. The values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred as follows: 1) when ph_deblocking_chroma_offsets_present_idc is equal to 0, the values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred to be equal to ph_beta_offset_div2 and ph_tc_offset_div2, respectively; and 2) when ph_deblocking_chroma_offsets_present_idc is equal to 2, the values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred to be equal to pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2, respectively.
[0293] Embodiment 2 Example of disabling the operation of the deblocking filter on the chrominance component and enabling the operation of the deblocking filter on the luminance component
[0294] It is proposed to add syntax elements in PPS, PH and SH to disable the operation of the deblocking filter on the chroma components and enable the operation of the deblocking filter on the luma components. Embodiment 2 can be combined with Embodiment 1.
[0295] The following are example syntax and semantics in Example 2.
[0296] Table 21
[0297]
[0298]
[0299] deblocking_filter_control_present_flag equal to 1 specifies that the deblocking filter control syntax element is present in the PPS. deblocking_filter_control_present_flag equal to 0 specifies that the deblocking filter control syntax element is not present in the PPS.
[0300] deblocking_filter_override_enabled_flag equal to 1 specifies that ph_deblocking_filter_override_flag is present in the PH referencing the PPS or slice_deblocking_filter_override_flag is present in the slice header referencing the PPS. deblocking_filter_override_enabled_flag equal to 0 specifies that ph_deblocking_filter_override_flag is not present in the PH referencing the PPS or slice_deblocking_filter_override_flag is not present in the slice header referencing the PPS. When not present, the value of deblocking_filter_override_enabled_flag is inferred to be equal to 0.
[0301] pps_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter should not be applied to slices that reference a PPS where slice_deblocking_filter_disabled_flag is not present. pps_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter should be applied to slices that reference a PPS where slice_deblocking_filter_disabled_flag is not present. When not present, the value of pps_deblocking_filter_disabled_flag is inferred to be equal to 0. As described above, pps_deblocking_filter_diabled_flag can be replaced with pps_deblocking_filter_enabled_flag.
[0302] pps_chroma_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter on the chroma components should not be applied to slices referencing a PPS in which slice_chroma_deblocking_filter_disabled_flag is not present. pps_chroma_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter on the chroma components should be applied to slices referencing a PPS in which slice_chroma_deblocking_filter_disabled_flag is not present. When not present, the value of pps_chroma_deblocking_filter_disabled_flag is inferred to be equal to 0. pps_chroma_deblocking_filter_disabled_flag may be replaced by pps_chroma_deblocking_filter_enabled_flag.
[0303] pps_beta_offset_div2 and pps_tc_offset_div2 specify the default deblocking parameter offsets for beta and tc (divided by 2) applied to the luma component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_beta_offset_div2 and pps_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of pps_beta_offset_div2 and pps_tc_offset_div2 are both inferred to be equal to 0.
[0304] pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 specify the default deblocking parameter offsets for beta and tC (divided by 2) applied to the Cb component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or slice header of the slice referencing the PPS. The values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2 are both inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively.
[0305] pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 specify the default deblocking parameter offsets for beta and tC (divided by 2) applied to the Cr component of the slice referencing the PPS, unless the default deblocking parameter offsets are overridden by the deblocking parameter offsets present in the picture header or the slice header of the slice referencing the PPS. The values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2 are both inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively.
[0306] Table 22
[0307]
[0308] ph_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in PH. ph_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in PH. When not present, the value of ph_deblocking_filter_override_flag is inferred to be equal to 0.
[0309] ph_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is not applied to the slices associated with the PH. ph_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is applied to the slices associated with the PH. When ph_deblocking_filter_disabled_flag is not present, it is inferred to be equal to pps_deblocking_filter_disabled_flag. As described above, in some embodiments, ph_deblocking_filter_disabled_flag is replaced with ph_deblocking_filter_enabled_flag.
[0310] ph_chroma_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter on the chroma components is not applied to the slices associated with the PH. ph_chroma_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter on the chroma components is applied to the slices associated with the PH. When ph_chroma_deblocking_filter_disabled_flag is not present, it is inferred to be equal to pps_chroma_deblocking_filter_disabled_flag. In some embodiments, ph_chroma_deblocking_filter_disabled_flag is replaced by ph_chroma_deblocking_filter_enabled_flag.
[0311] ph_beta_offset_div2 and ph_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the luma component of the slice associated with the PH. The values of ph_beta_offset_div2 and ph_tc_offset_div2 shall both be in the range of -12 to 12, inclusive. When not present, the values of ph_beta_offset_div2 and ph_tc_offset_div2 are inferred to be equal to pps_beta_offset_div2 and pps_tc_offset_div2, respectively.
[0312] ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cb component of the slice associated with the PH. The values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2 are inferred to be equal to pps_cb_beta_offset_div2 and pps_cb_tc_offset_div2, respectively.
[0313] ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cr components of the slice associated with the PH. The values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2 are inferred to be equal to pps_cr_beta_offset_div2 and pps_cr_tc_offset_div2, respectively.
[0314] Table 23
[0315]
[0316]
[0317] slice_deblocking_filter_override_flag equal to 1 specifies that deblocking parameters are present in the slice header. slice_deblocking_filter_override_flag equal to 0 specifies that deblocking parameters are not present in the slice header. When not present, the value of slice_deblocking_filter_override_flag is inferred to be equal to ph_deblocking_filter_override_flag.
[0318] slice_deblocking_filter_disabled_flag equal to 1 specifies that the operation of the deblocking filter is not applied to the current slice. slice_deblocking_filter_disabled_flag equal to 0 specifies that the operation of the deblocking filter is applied to the current slice. When slice_deblocking_filter_disabled_flag is not present, it is inferred to be equal to ph_deblocking_filter_disabled_flag or !ph_deblocking_filter_enabled_flag. In some embodiments, slice_deblocking_filter_disabled_flag is replaced with slice_deblocking_filter_enabled_flag.
[0319] slice_chroma_deblocking_filter_disabled_flag equal to 1 indicates that the operation of the deblocking filter on the chroma components is not applied to the current slice. slice_chroma_deblocking_filter_disabled_flag equal to 0 indicates that the operation of the deblocking filter on the chroma components is applied to the current slice. When slice_chroma_deblocking_filter_disabled_flag is not present, it is inferred to be equal to ph_chroma_deblocking_filter_disabled_flag. In some embodiments, slice_chroma_deblocking_filter_disabled_flag is replaced by slice_chroma_deblocking_filter_enabled_flag.
[0320] slice_beta_offset_div2 and slice_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the luma component of the current slice. The values of slice_beta_offset_div2 and slice_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of slice_beta_offset_div2 and slice_tc_offset_div2 are inferred to be equal to ph_beta_offset_div2 and ph_tc_offset_div2, respectively.
[0321] slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cb component of the current slice. The values of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 are inferred to be equal to ph_cb_beta_offset_div2 and ph_cb_tc_offset_div2, respectively.
[0322] slice_cb_beta_offset_div2 and slice_cb_tc_offset_div2 specify the deblocking parameter offsets of beta and tc (divided by 2) applied to the Cr components of the current slice. The values of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 should both be in the range of -12 to 12, inclusive. When not present, the values of slice_cr_beta_offset_div2 and slice_cr_tc_offset_div2 are inferred to be equal to ph_cr_beta_offset_div2 and ph_cr_tc_offset_div2, respectively.
[0323] Example 3
[0324] As indicated above, the presence of syntax elements that apply to both chroma components may be controlled by a 1-bit syntax element. In other words, in some embodiments, the presence of Cr follows the presence of Cb.
[0325] In this embodiment, a first 1-bit syntax element is used for the Cb component and a second 1-bit syntax element is used for the Cr component to control the presence of syntax elements applied to the Cb component and applied to the Cr component, respectively.
[0326] In a variation of this embodiment, a 2-bit syntax element is used to jointly control the presence of syntax elements that apply to the Cb component and to the Cr component, as described below.
[0327] If the value of the 2-bit syntax element is equal to 0, it specifies that there is no syntax element applied to the Cb component and the Cr component.
[0328] If the value of the 2-bit syntax element is equal to 1, it specifies that there are syntax elements applicable to the Cb component and there are no syntax elements applicable to the Cr component.
[0329] If the value of the 2-bit syntax element is equal to 2, it specifies that there are no syntax elements applicable to the Cb component and there are syntax elements applicable to the Cr component.
[0330] If the value of the 2-bit syntax element is equal to 3, it specifies that there is a syntax element that applies to both the Cb component and the Cr component.
[0331] Embodiment 4 Distinguishing Based on Inferring as X and Signaling as X In this embodiment, a conditional method is proposed, which distinguishes between inferring the value of syntax element A as value X and explicitly signaling that syntax element A is equal to value X. In one example of the current embodiment, control of the Cb component and the Cr component can be defined as follows.
[0332] If the value of the syntax element A is signaled as the first value, it specifies that there is no syntax element applied to the Cb component and the Cr component.
[0333] If the value of the syntax element A is inferred to be the first value, it specifies that there are syntax elements applicable to the Cb component and there are no syntax elements applicable to the Cr component.
[0334] If the value of the syntax element A is signaled as the second value, it specifies that there are no syntax elements applied to the Cb component and there are syntax elements applied to the Cr component.
[0335] If the value of the syntax element A is inferred to be the second value, it specifies that there is a syntax element applied to the Cb component and the Cr component.
[0336] Fig.12 1 is a block diagram of an apparatus 1200 for implementing the decoder 204 and / or the encoder 202 according to some embodiments. When the apparatus 1200 implements the decoder, the apparatus 1200 may be referred to as a "decoding apparatus 1200", and when the apparatus 1200 implements the encoder, the apparatus 1200 may be referred to as an "encoding apparatus 1200". Fig.12As shown, the device 1200 may include: a processing circuit (PC) 1202, which may include one or more processors (P) 1255 (e.g., a general-purpose microprocessor and / or one or more other processors, such as an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), which may be co-located in a single housing or a single data center, or may be geographically distributed (i.e., the device 1200 may be a distributed computing device); at least one network interface 1248, which includes a transmitter (Tx); 1245 and a receiver (Rx) 1247 for enabling the apparatus 1200 to send data to and receive data from other nodes connected to a network 110 (e.g., an Internet Protocol (IP) network), a network interface 1248 connected (directly or indirectly) to the network 110 (e.g., the network interface 1248 may be wirelessly connected to the network 110, in which case the network interface 1248 is connected to an antenna arrangement); and a storage unit (also known as a "data storage system") 1208, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments where the PC 1202 includes a programmable processor, a computer program product (CPP) 1241 may be provided. The CPP 1241 includes a computer readable medium (CRM) 1242 storing a computer program (CP) 1243, the computer program (CP) 1243 including computer readable instructions (CRI) 1244. CRM 1242 can be a non-transitory computer-readable medium, such as a magnetic medium (e.g., a hard disk), an optical medium, a memory device (e.g., a random access memory, a flash memory), etc. In some embodiments, CRI 1244 of computer program 1243 is configured so that when executed by PC 1202, CRI causes device 1200 to perform the steps described herein (e.g., the steps described herein with reference to the flowcharts). In other embodiments, device 1200 can be configured to perform the steps described herein without the need for code. That is, for example, PC 1202 can consist of only one or more ASICs. Therefore, the features of the embodiments described herein can be implemented in hardware and / or software.
[0337] Although various embodiments are described herein, it should be understood that they are presented by way of example only and not limitation. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above exemplary embodiments. In addition, any combination of the above elements with all possible variations thereof is included in the present disclosure, unless otherwise indicated or otherwise clearly conflicting with the context.
[0338] Additionally, although the processes described above and shown in the accompanying drawings are shown as a series of steps, this is for illustrative purposes only. Therefore, it is contemplated that some steps may be added, some steps may be omitted, the order of steps may be rearranged, and some steps may be performed in parallel.
Claims
1. A method, performed by a decoder, for deriving a value of a first syntax element Syntax_A, the method comprising: Determine whether Syntax_A is present in the bitstream; deriving the value D from at least the value of the fourth syntax element Syntax_D; As a result of determining that Syntax_A is not present in the bitstream, deriving the value B from at least the value of the second syntax element Syntax_B; If D is equal to the first value indicating the presence of Syntax_D, then the value of Syntax_A is deduced to be equal to the value B, or deriving the value C from at least the value of the third syntax element Syntax_C; If D is equal to a second value indicating that Syntax_D is not present, the value of Syntax_A is deduced to be equal to the value C; and The derived value of Syntax_A is used to decode a picture from the bitstream.
2. The method according to claim 1, wherein: At least one of B, C and D is equal to the value of the syntax elements Syntax_B, Syntax_C and Syntax_D, respectively.
3. The method according to any one of claims 1 to 2, wherein: At least one of Syntax_B, Syntax_C, and Syntax_D is decoded from the bitstream.
4. The method according to any one of claims 1 to 2, wherein: Deriving the value B includes: determining whether the second syntax element Syntax_B is present in the bitstream; and As a result of determining that Syntax_B is not present in the bitstream, the value B is inferred, otherwise the value B is decoded from Syntax_B.
5. The method according to any one of claims 1 to 2, wherein: Deriving the value D includes: determining whether the fourth syntax element Syntax_D is present in the bitstream; and If Syntax_D is determined to be present in the bitstream, D is set equal to a third value, wherein the third value is a predetermined value or the third value is equal to a decoded value of Syntax_D.
6. The method according to claim 5, wherein: Deriving the value D includes setting D equal to a fourth value if Syntax_D is determined not to be present in the bitstream, wherein the fourth value is a predetermined value or the fourth value is equal to an inferred value of Syntax_D.
7. The method according to any one of claims 1 to 2, wherein: At least one of Syntax_A, Syntax_B, Syntax_C, or Syntax_D is a deblocking parameter.
8. The method according to any one of claims 1 to 2, wherein: All existing syntax elements Syntax_A, Syntax_B, Syntax_C and Syntax_D are in one header or parameter set.
9. The method according to any one of claims 1 to 2, wherein: All existing syntax elements Syntax_A, Syntax_B, Syntax_C and Syntax_D are in several headers or parameter sets.
10. A computer program product comprising instructions which, when executed by a processing circuit, cause the processing circuit to perform the method according to any one of claims 1 to 9.
11. A computer-readable storage medium storing a computer program comprising instructions which, when executed by a processing circuit, cause the processing circuit to perform the method according to any one of claims 1 to 9.
12. An apparatus for deriving a value of a first syntax element Syntax_A, the apparatus comprising: Processing circuit; as well as A memory containing instructions executable by the processing circuit, whereby the apparatus is operable to perform a method according to any one of claims 1 to 9.
