This patent document relates to video processing techniques, devices and systems.
In spite of the advances in video compression, digital video still accounts for the largest bandwidth use on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, it is expected that the bandwidth demand for digital video usage will continue to grow.
Devices, systems and methods related to digital video processing. The described methods may be applied to both the existing video coding standards (e.g., High Efficiency Video Coding (HEVC)) and future video coding standards or video codecs.
In one representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes generating a prediction block for a current video block of a video using an affine mode motion compensation that is performed at a sub-block level of the current video block; performing a gradient calculation for a region of the current video block to refine the prediction block using a prediction refinement with optical flow (PROF) procedure, wherein a size of the region, (M×N), is different from a size of a sub-block of the current video block, wherein M and N are positive integers; and performing, based on the gradient calculation, a conversion between the current video block and a coded representation of the video.
In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes deriving, for a current video block of a video having a first size, a final prediction block that is computed by refining one or more intermediate prediction blocks using a gradient calculation performed on video regions having a second size according to a rule, wherein the refining uses an optical flow procedure; and performing a conversion between the current video block and a coded representation of the video using the final prediction block.
In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes deriving, for a current video block of a video, motion information using a bidirectional optical flow (BDOF) or a prediction refinement with optical flow (PROF); performing a gradient calculation for samples in a region of the current video block such that at least one sample in the region is omitted from the gradient calculation; and performing, based on the gradient calculation, a conversion between the current video block and a coded representation of a video comprising the current video block, wherein one or more initial predictions for the current video block are computed at a sub-block level and refined using an optical flow calculation during the PROF or the one or more initial predictions are refined using a spatial and a temporal gradient during the BDOF.
In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes determining, for a current video block of a video, a final prediction block for the current video block by refining one or more initial predictions for the current video block using an optical flow calculation based on a gradient of initial prediction samples according to a precision rule; and performing a conversion between the current video block and a coded representation using the final prediction block, wherein the optical flow calculation includes a prediction refinement with optical flow (PROF) procedure or a bi-directional optical flow (BDOF) procedure, wherein the precision rule specifies to use a same precision for representing the gradient for both the PROF procedure and the BDOF procedure.
In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes determining, for conversion between a current video block of a video and a coded representation of the video, a final prediction block for the current video block by refining one or more initial predictions for the current video block using an optical flow calculation; and performing the conversion using the final prediction block, wherein the optical flow calculation includes a prediction refinement with optical flow (PROF) procedure and/or a bi-directional optical flow (BDOF) procedure, wherein the optical flow calculation further includes a padding operation applicable to at least one of the PROF procedure or the BDOF procedure according to a rule to derive padding samples.
In yet another representative aspect, the above-described method is embodied in the form of processor-executable code and stored in a computer-readable program medium.
In yet another representative aspect, a device that is configured or operable to perform the above-described method is disclosed. The device may include a processor that is programmed to implement this method.
In yet another representative aspect, a video decoder apparatus may implement a method as described herein.
The above and other aspects and features of the disclosed technology are described in greater detail in the drawings, the description and the claims.
Due to the increasing demand of higher resolution video, video processing methods and techniques are ubiquitous in modern technology. Video codecs typically include an electronic circuit or software that compresses or decompresses digital video, and are continually being improved to provide higher coding efficiency. A video codec converts uncompressed video to a compressed format or vice versa. There are complex relationships between the video quality, the amount of data used to represent the video (determined by the bit rate), the complexity of the encoding and decoding algorithms, sensitivity to data losses and errors, ease of editing, random access, and end-to-end delay (latency). The compressed format usually conforms to a standard video compression specification, e.g., the High Efficiency Video Coding (HEVC) standard (also known as H.265 or MPEG-H Part 2), the Versatile Video Coding standard to be finalized, or other current and/or future video coding standards.
Embodiments of the disclosed technology may be applied to existing video coding standards (e.g., HEVC, H.265) and future standards to improve compression performance. Section headings are used in the present document to improve readability of the description and do not in any way limit the discussion or the embodiments (and/or implementations) to the respective sections only.
1. Examples of Inter-Prediction in HEVC/H.265
Video coding standards have significantly improved over the years, and now provide, in part, high coding efficiency and support for higher resolutions. Recent standards such as HEVC and H.265 are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized.
1.1 Examples of Prediction Modes
Each inter-predicted PU (prediction unit) has motion parameters for one or two reference picture lists. In some embodiments, motion parameters include a motion vector and a reference picture index. In other embodiments, the usage of one of the two reference picture lists may also be signaled using inter_pred_idc. In yet other embodiments, motion vectors may be explicitly coded as deltas relative to predictors.
When a CU is coded with skip mode, one PU is associated with the CU, and there are no significant residual coefficients, no coded motion vector delta or reference picture index. A merge mode is specified whereby the motion parameters for the current PU are obtained from neighboring PUs, including spatial and temporal candidates. The merge mode can be applied to any inter-predicted PU, not only for skip mode. The alternative to merge mode is the explicit transmission of motion parameters, where motion vector, corresponding reference picture index for each reference picture list and reference picture list usage are signaled explicitly per each PU.
When signaling indicates that one of the two reference picture lists is to be used, the PU is produced from one block of samples. This is referred to as ‘uni-prediction’. Uni-prediction is available both for P-slices and B-slices.
When signaling indicates that both of the reference picture lists are to be used, the PU is produced from two blocks of samples. This is referred to as ‘bi-prediction’. Bi-prediction is available for B-slices only.
1.1.1 Embodiments of Constructing Candidates for Merge Mode
When a PU is predicted using merge mode, an index pointing to an entry in the merge candidates list is parsed from the bitstream and used to retrieve the motion information. The construction of this list can be summarized according to the following sequence of steps:
1.1.2 Constructing Spatial Merge Candidates
In the derivation of spatial merge candidates, a maximum of four merge candidates are selected among candidates located in the positions depicted in
To reduce computational complexity, not all possible candidate pairs are considered in the mentioned redundancy check. Instead only the pairs linked with an arrow in
1.1.3 Constructing Temporal Merge Candidates
In this step, only one candidate is added to the list. Particularly, in the derivation of this temporal merge candidate, a scaled motion vector is derived based on co-located PU belonging to the picture which has the smallest POC difference with current picture within the given reference picture list. The reference picture list to be used for derivation of the co-located PU is explicitly signaled in the slice header.
In the co-located PU (Y) belonging to the reference frame, the position for the temporal candidate is selected between candidates C0 and C1, as depicted in
1.1.4 Constructing Additional Types of Merge Candidates
Besides spatio-temporal merge candidates, there are two additional types of merge candidates: combined bi-predictive merge candidate and zero merge candidate. Combined bi-predictive merge candidates are generated by utilizing spatio-temporal merge candidates. Combined bi-predictive merge candidate is used for B-Slice only. The combined bi-predictive candidates are generated by combining the first reference picture list motion parameters of an initial candidate with the second reference picture list motion parameters of another. If these two tuples provide different motion hypotheses, they will form a new bi-predictive candidate.
Zero motion candidates are inserted to fill the remaining entries in the merge candidates list and therefore hit the MaxNumMergeCand capacity. These candidates have zero spatial displacement and a reference picture index which starts from zero and increases every time a new zero motion candidate is added to the list. The number of reference frames used by these candidates is one and two for uni- and bi-directional prediction, respectively. In some embodiments, no redundancy check is performed on these candidates.
1.1.5 Examples of Motion Estimation Regions for Parallel Processing
To speed up the encoding process, motion estimation can be performed in parallel whereby the motion vectors for all prediction units inside a given region are derived simultaneously. The derivation of merge candidates from spatial neighborhood may interfere with parallel processing as one prediction unit cannot derive the motion parameters from an adjacent PU until its associated motion estimation is completed. To mitigate the trade-off between coding efficiency and processing latency, a motion estimation region (MER) may be defined. The size of the MER may be signaled in the picture parameter set (PPS) using the “log 2_parallel_merge_level_minus2” syntax element. When a MER is defined, merge candidates falling in the same region are marked as unavailable and therefore not considered in the list construction.
1.2 Embodiments of Advanced Motion Vector Prediction (AMVP)
AMVP exploits spatio-temporal correlation of motion vector with neighboring PUs, which is used for explicit transmission of motion parameters. It constructs a motion vector candidate list by firstly checking availability of left, above temporally neighboring PU positions, removing redundant candidates and adding zero vector to make the candidate list to be constant length. Then, the encoder can select the best predictor from the candidate list and transmit the corresponding index indicating the chosen candidate. Similarly with merge index signaling, the index of the best motion vector candidate is encoded using truncated unary. The maximum value to be encoded in this case is 2 (see
1.2.1 Examples of Constructing Motion Vector Prediction Candidates
In motion vector prediction, two types of motion vector candidates are considered: spatial motion vector candidate and temporal motion vector candidate. For spatial motion vector candidate derivation, two motion vector candidates are eventually derived based on motion vectors of each PU located in five different positions as previously shown in
For temporal motion vector candidate derivation, one motion vector candidate is selected from two candidates, which are derived based on two different co-located positions. After the first list of spatio-temporal candidates is made, duplicated motion vector candidates in the list are removed. If the number of potential candidates is larger than two, motion vector candidates whose reference picture index within the associated reference picture list is larger than 1 are removed from the list. If the number of spatio-temporal motion vector candidates is smaller than two, additional zero motion vector candidates is added to the list.
1.2.2 Constructing Spatial Motion Vector Candidates
In the derivation of spatial motion vector candidates, a maximum of two candidates are considered among five potential candidates, which are derived from PUs located in positions as previously shown in
The no-spatial-scaling cases are checked first followed by the cases that allow spatial scaling. Spatial scaling is considered when the POC is different between the reference picture of the neighbouring PU and that of the current PU regardless of reference picture list. If all PUs of left candidates are not available or are intra coded, scaling for the above motion vector is allowed to help parallel derivation of left and above V candidates. Otherwise, spatial scaling is not allowed for the above motion vector.
As shown in the example in
1.2.3 Constructing Temporal Motion Vector Candidates
Apart from the reference picture index derivation, all processes for the derivation of temporal merge candidates are the same as for the derivation of spatial motion vector candidates (as shown in the example in
2. Example of Inter Prediction Methods in Joint Exploration Model (JEM)
In some embodiments, future video coding technologies are explored using a reference software known as the Joint Exploration Model (JEM). In JEM, sub-block based prediction is adopted in several coding tools, such as affine prediction, alternative temporal motion vector prediction (ATMVP), spatial-temporal motion vector prediction (STMVP), bi-directional optical flow (BIO), Frame-Rate Up Conversion (FRUC), Locally Adaptive Motion Vector Resolution (LAMVR), Overlapped Block Motion Compensation (OBMC), Local Illumination Compensation (LIC), and Decoder-side Motion Vector Refinement (DMVR).
2.1 Examples of Sub-CU Based Motion Vector Prediction
In the JEM with quadtrees plus binary trees (QTBT), each CU can have at most one set of motion parameters for each prediction direction. In some embodiments, two sub-CU level motion vector prediction methods are considered in the encoder by splitting a large CU into sub-CUs and deriving motion information for all the sub-CUs of the large CU. Alternative temporal motion vector prediction (ATMVP) method allows each CU to fetch multiple sets of motion information from multiple blocks smaller than the current CU in the collocated reference picture. In spatial-temporal motion vector prediction (STMVP) method motion vectors of the sub-CUs are derived recursively by using the temporal motion vector predictor and spatial neighbouring motion vector. In some embodiments, and to preserve more accurate motion field for sub-CU motion prediction, the motion compression for the reference frames may be disabled.
2.1.1 Examples of Alternative Temporal Motion Vector Prediction (ATMVP)
In the ATMVP method, the temporal motion vector prediction (TMVP) method is modified by fetching multiple sets of motion information (including motion vectors and reference indices) from blocks smaller than the current CU.
In the first step, a reference picture 1050 and the corresponding block is determined by the motion information of the spatial neighboring blocks of the current CU 1000. To avoid the repetitive scanning process of neighboring blocks, the first merge candidate in the merge candidate list of the current CU 1000 is used. The first available motion vector as well as its associated reference index are set to be the temporal vector and the index to the motion source picture. This way, the corresponding block may be more accurately identified, compared with TMVP, wherein the corresponding block (sometimes called collocated block) is always in a bottom-right or center position relative to the current CU.
In the second step, a corresponding block of the sub-CU 1051 is identified by the temporal vector in the motion source picture 1050, by adding to the coordinate of the current CU the temporal vector. For each sub-CU, the motion information of its corresponding block (e.g., the smallest motion grid that covers the center sample) is used to derive the motion information for the sub-CU. After the motion information of a corresponding N×N block is identified, it is converted to the motion vectors and reference indices of the current sub-CU, in the same way as TMVP of HEVC, wherein motion scaling and other procedures apply. For example, the decoder checks whether the low-delay condition (e.g. the POCs of all reference pictures of the current picture are smaller than the POC of the current picture) is fulfilled and possibly uses motion vector MVx (e.g., the motion vector corresponding to reference picture list X) to predict motion vector MVy (e.g., with X being equal to 0 or 1 and Y being equal to 1−X) for each sub-CU.
2.1.2 Examples of Spatial-Temporal Motion Vector Prediction (STMVP)
In the STMVP method, the motion vectors of the sub-CUs are derived recursively, following raster scan order.
The motion derivation for sub-CU A starts by identifying its two spatial neighbors. The first neighbor is the N×N block above sub-CU A 1101 (block c 1113). If this block c (1113) is not available or is intra coded the other N×N blocks above sub-CU A (1101) are checked (from left to right, starting at block c 1113). The second neighbor is a block to the left of the sub-CU A 1101 (block b 1112). If block b (1112) is not available or is intra coded other blocks to the left of sub-CU A 1101 are checked (from top to bottom, staring at block b 1112). The motion information obtained from the neighboring blocks for each list is scaled to the first reference frame for a given list. Next, temporal motion vector predictor (TMVP) of sub-block A 1101 is derived by following the same procedure of TMVP derivation as specified in HEVC. The motion information of the collocated block at block D 1104 is fetched and scaled accordingly. Finally, after retrieving and scaling the motion information, all available motion vectors are averaged separately for each reference list. The averaged motion vector is assigned as the motion vector of the current sub-CU.
2.1.3 Examples of Sub-CU Motion Prediction Mode Signaling
In some embodiments, the sub-CU modes are enabled as additional merge candidates and there is no additional syntax element required to signal the modes. Two additional merge candidates are added to merge candidates list of each CU to represent the ATMVP mode and STMVP mode. In other embodiments, up to seven merge candidates may be used, if the sequence parameter set indicates that ATMVP and STMVP are enabled. The encoding logic of the additional merge candidates is the same as for the merge candidates in the HM, which means, for each CU in P or B slice, two more RD checks may be needed for the two additional merge candidates. In some embodiments, e.g., JEM, all bins of the merge index are context coded by CABAC (Context-based Adaptive Binary Arithmetic Coding). In other embodiments, e.g., HEVC, only the first bin is context coded and the remaining bins are context by-pass coded.
2.2 Examples of Adaptive Motion Vector Difference Resolution
In some embodiments, motion vector differences (MVDs) (between the motion vector and predicted motion vector of a PU) are signalled in units of quarter luma samples when use_integer_mv_flag is equal to 0 in the slice header. In the JEM, a locally adaptive motion vector resolution (LAMVR) is introduced. In the JEM, MVD can be coded in units of quarter luma samples, integer luma samples or four luma samples. The MVD resolution is controlled at the coding unit (CU) level, and MVD resolution flags are conditionally signalled for each CU that has at least one non-zero MVD components.
For a CU that has at least one non-zero MVD components, a first flag is signalled to indicate whether quarter luma sample MV precision is used in the CU. When the first flag (equal to 1) indicates that quarter luma sample MV precision is not used, another flag is signalled to indicate whether integer luma sample MV precision or four luma sample MV precision is used.
When the first MVD resolution flag of a CU is zero, or not coded for a CU (meaning all MVDs in the CU are zero), the quarter luma sample MV resolution is used for the CU. When a CU uses integer-luma sample MV precision or four-luma-sample MV precision, the MVPs in the AMVP candidate list for the CU are rounded to the corresponding precision.
In the encoder, CU-level RD checks are used to determine which MVD resolution is to be used for a CU. That is, the CU-level RD check is performed three times for each MVD resolution. To accelerate encoder speed, the following encoding schemes are applied in the JEM:
In HEVC, motion vector accuracy is one-quarter pel (one-quarter luma sample and one-eighth chroma sample for 4:2:0 video). In the JEM, the accuracy for the internal motion vector storage and the merge candidate increases to 1/16 pel. The higher motion vector accuracy ( 1/16 pel) is used in motion compensation inter prediction for the CU coded with skip/merge mode. For the CU coded with normal AMVP mode, either the integer-pel or quarter-pel motion is used.
SHVC up sampling interpolation filters, which have same filter length and normalization factor as HEVC motion compensation interpolation filters, are used as motion compensation interpolation filters for the additional fractional pel positions. The chroma component motion vector accuracy is 1/32 sample in the JEM, the additional interpolation filters of 1/32 pel fractional positions are derived by using the average of the filters of the two neighbouring 1/16 pel fractional positions.
2.4 Examples of Overlapped Block Motion Compensation (OBMC)
In the JEM, OBMC can be switched on and off using syntax at the CU level. When OBMC is used in the JEM, the OBMC is performed for all motion compensation (MC) block boundaries except the right and bottom boundaries of a CU. Moreover, it is applied for both the luma and chroma components. In the JEM, an MC block corresponds to a coding block. When a CU is coded with sub-CU mode (includes sub-CU merge, affine and FRUC mode), each sub-block of the CU is a MC block. To process CU boundaries in a uniform fashion, OBMC is performed at sub-block level for all MC block boundaries, where sub-block size is set equal to 4×4, as shown in
When OBMC applies to the current sub-block, besides current motion vectors, motion vectors of four connected neighboring sub-blocks, if available and are not identical to the current motion vector, are also used to derive prediction block for the current sub-block. These multiple prediction blocks based on multiple motion vectors are combined to generate the final prediction signal of the current sub-block.
Prediction block based on motion vectors of a neighboring sub-block is denoted as PN, with N indicating an index for the neighboring above, below, left and right sub-blocks and prediction block based on motion vectors of the current sub-block is denoted as PC. When PN is based on the motion information of a neighboring sub-block that contains the same motion information to the current sub-block, the OBMC is not performed from PN. Otherwise, every sample of PN is added to the same sample in PC, i.e., four rows/columns of PN are added to PC. The weighting factors {¼, ⅛, 1/16, 1/32} are used for PN and the weighting factors {¾, ⅞, 15/16, 31/32} are used for PC. The exception are small MC blocks, (i.e., when height or width of the coding block is equal to 4 or a CU is coded with sub-CU mode), for which only two rows/columns of PN are added to PC. In this case weighting factors {¼, ⅛} are used for PN and weighting factors {¾, ⅞} are used for PC. For PN generated based on motion vectors of vertically (horizontally) neighboring sub-block, samples in the same row (column) of PN are added to PC with a same weighting factor.
In the JEM, for a CU with size less than or equal to 256 luma samples, a CU level flag is signaled to indicate whether OBMC is applied or not for the current CU. For the CUs with size larger than 256 luma samples or not coded with AMVP mode, OBMC is applied by default. At the encoder, when OBMC is applied for a CU, its impact is taken into account during the motion estimation stage. The prediction signal formed by OBMC using motion information of the top neighboring block and the left neighboring block is used to compensate the top and left boundaries of the original signal of the current CU, and then the normal motion estimation process is applied.
2.5 Examples of Local Illumination Compensation (LIC)
LIC is based on a linear model for illumination changes, using a scaling factor a and an offset b. And it is enabled or disabled adaptively for each inter-mode coded coding unit (CU).
When LIC applies for a CU, a least square error method is employed to derive the parameters a and b by using the neighboring samples of the current CU and their corresponding reference samples.
When a CU is coded with merge mode, the LIC flag is copied from neighboring blocks, in a way similar to motion information copy in merge mode; otherwise, an LIC flag is signaled for the CU to indicate whether LIC applies or not.
When LIC is enabled for a picture, an additional CU level RD check is needed to determine whether LIC is applied or not for a CU. When LIC is enabled for a CU, the mean-removed sum of absolute difference (MR-SAD) and mean-removed sum of absolute Hadamard-transformed difference (MR-SATD) are used, instead of SAD and SATD, for integer pel motion search and fractional pel motion search, respectively.
To reduce the encoding complexity, the following encoding scheme is applied in the JEM:
In HEVC, only a translation motion model is applied for motion compensation prediction (MCP). However, the camera and objects may have many kinds of motion, e.g. zoom in/out, rotation, perspective motions, and/or other irregular motions. JEM, on the other hand, applies a simplified affine transform motion compensation prediction.
As shown in
Here, MvPre is the motion vector fraction accuracy (e.g., 1/16 in JEM). (v2x, v2y) is motion vector of the bottom-left control point, calculated according to Eq. (1). M and N can be adjusted downward if necessary to make it a divisor of w and h, respectively.
2.6.1 Embodiments of the AF_INTER Mode
In the JEM, there are two affine motion modes: AF_INTER mode and AF_MERGE mode. For CUs with both width and height larger than 8, AF_INTER mode can be applied. An affine flag in CU level is signaled in the bitstream to indicate whether AF_INTER mode is used. In the AF_INTER mode, a candidate list with motion vector pair {(v0,v1)|v0={vA, vB, vC}, v1{vD,vE}} is constructed using the neighboring blocks.
2.6.3 Embodiments of the AF_MERGE Mode
When a CU is applied in AF_MERGE mode, it gets the first block coded with an affine mode from the valid neighboring reconstructed blocks.
After the CPMV of the current CU v0 and v1 are computed according to the affine motion model in Eq. (1), the MVF of the current CU can be generated. In order to identify whether the current CU is coded with AF_MERGE mode, an affine flag can be signaled in the bitstream when there is at least one neighboring block is coded in affine mode.
2.7 Examples of Pattern Matched Motion Vector Derivation (PMMVD)
The PMMVD mode is a special merge mode based on the Frame-Rate Up Conversion (FRUC) method. With this mode, motion information of a block is not signaled but derived at decoder side.
A FRUC flag can be signaled for a CU when its merge flag is true. When the FRUC flag is false, a merge index can be signaled and the regular merge mode is used. When the FRUC flag is true, an additional FRUC mode flag can be signaled to indicate which method (e.g., bilateral matching or template matching) is to be used to derive motion information for the block.
At the encoder side, the decision on whether using FRUC merge mode for a CU is based on RD cost selection as done for normal merge candidate. For example, multiple matching modes (e.g., bilateral matching and template matching) are checked for a CU by using RD cost selection. The one leading to the minimal cost is further compared to other CU modes. If a FRUC matching mode is the most efficient one, FRUC flag is set to true for the CU and the related matching mode is used.
Typically, motion derivation process in FRUC merge mode has two steps: a CU-level motion search is first performed, then followed by a Sub-CU level motion refinement. At CU level, an initial motion vector is derived for the whole CU based on bilateral matching or template matching. First, a list of MV candidates is generated and the candidate that leads to the minimum matching cost is selected as the starting point for further CU level refinement. Then a local search based on bilateral matching or template matching around the starting point is performed. The MV results in the minimum matching cost is taken as the MV for the whole CU. Subsequently, the motion information is further refined at sub-CU level with the derived CU motion vectors as the starting points.
For example, the following derivation process is performed for a W×H CU motion information derivation. At the first stage, MV for the whole W×H CU is derived. At the second stage, the CU is further split into M×M sub-CUs. The value of M is calculated as in Eq. (3), D is a predefined splitting depth which is set to 3 by default in the JEM. Then the MV for each sub-CU is derived.
The MV candidate set at CU level can include the following: (1) original AMVP candidates if the current CU is in AMVP mode, (2) all merge candidates, (3) several MVs in the interpolated MV field (described later), and top and left neighboring motion vectors.
When using bilateral matching, each valid MV of a merge candidate can be used as an input to generate a MV pair with the assumption of bilateral matching. For example, one valid MV of a merge candidate is (MVa, refa) at reference list A. Then the reference picture refb of its paired bilateral MV is found in the other reference list B so that refa and refb are temporally at different sides of the current picture. If such a refb is not available in reference list B, refb is determined as a reference which is different from refa and its temporal distance to the current picture is the minimal one in list B. After refb is determined, MVb is derived by scaling MVa based on the temporal distance between the current picture and refa, refb.
In some implementations, four MVs from the interpolated MV field can also be added to the CU level candidate list. More specifically, the interpolated MVs at the position (0, 0), (W/2, 0), (0, H/2) and (W/2, H/2) of the current CU are added. When FRUC is applied in AMVP mode, the original AMVP candidates are also added to CU level MV candidate set. In some implementations, at the CU level, 15 MVs for AMVP CUs and 13 MVs for merge CUs can be added to the candidate list.
The MV candidate set at sub-CU level includes an MV determined from a CU-level search, (2) top, left, top-left and top-right neighboring MVs, (3) scaled versions of collocated MVs from reference pictures, (4) one or more ATMVP candidates (e.g., up to four), and (5) one or more STMVP candidates (e.g., up to four). The scaled MVs from reference pictures are derived as follows. The reference pictures in both lists are traversed. The MVs at a collocated position of the sub-CU in a reference picture are scaled to the reference of the starting CU-level MV. ATMVP and STMVP candidates can be the four first ones. At the sub-CU level, one or more MVs (e.g., up to 17) are added to the candidate list.
Generation of an interpolated MV field. Before coding a frame, interpolated motion field is generated for the whole picture based on unilateral ME. Then the motion field may be used later as CU level or sub-CU level MV candidates.
In some embodiments, the motion field of each reference pictures in both reference lists is traversed at 4×4 block level.
Interpolation and matching cost. When a motion vector points to a fractional sample position, motion compensated interpolation is needed. To reduce complexity, bi-linear interpolation instead of regular 8-tap HEVC interpolation can be used for both bilateral matching and template matching.
The calculation of matching cost is a bit different at different steps. When selecting the candidate from the candidate set at the CU level, the matching cost can be the absolute sum difference (SAD) of bilateral matching or template matching. After the starting MV is determined, the matching cost C of bilateral matching at sub-CU level search is calculated as follows:
C=SAD+w·(|MVx−MVxs|+|MVy−MVys|) Eq. (4)
Here, w is a weighting factor. In some embodiments, w can be empirically set to 4. MV and MVs indicate the current MV and the starting MV, respectively. SAD may still be used as the matching cost of template matching at sub-CU level search.
In FRUC mode, MV is derived by using luma samples only. The derived motion will be used for both luma and chroma for MC inter prediction. After MV is decided, final MC is performed using 8-taps interpolation filter for luma and 4-taps interpolation filter for chroma.
MV refinement is a pattern based MV search with the criterion of bilateral matching cost or template matching cost. In the JEM, two search patterns are supported—an unrestricted center-biased diamond search (UCBDS) and an adaptive cross search for MV refinement at the CU level and sub-CU level, respectively. For both CU and sub-CU level MV refinement, the MV is directly searched at quarter luma sample MV accuracy, and this is followed by one-eighth luma sample MV refinement. The search range of MV refinement for the CU and sub-CU step are set equal to 8 luma samples.
In the bilateral matching merge mode, bi-prediction is applied because the motion information of a CU is derived based on the closest match between two blocks along the motion trajectory of the current CU in two different reference pictures. In the template matching merge mode, the encoder can choose among uni-prediction from list0, uni-prediction from list1, or bi-prediction for a CU. The selection ca be based on a template matching cost as follows:
If costBi<=factor*min (cost0, cost1)
Otherwise, if cost0<=cost1
Otherwise,
Here, cost0 is the SAD of list0 template matching, cost1 is the SAD of list1 template matching and costBi is the SAD of bi-prediction template matching. For example, when the value of factor is equal to 1.25, it means that the selection process is biased toward bi-prediction. The inter prediction direction selection can be applied to the CU-level template matching process.
2.8 Examples of Generalized Bi-Prediction Improvement (GBi)
Generalized Bi-prediction improvement (GBi) proposed in JVET-L0646 is adopted into VTM-3.0. GBi applies unequal weights to predictors from L0 and L1 in bi-prediction mode. In inter prediction mode, multiple weight pairs including the equal weight pair (½, ½) are evaluated based on rate-distortion optimization (RDO), and the GBi index of the selected weight pair is signaled to the decoder. In merge mode, the GBi index is inherited from a neighboring CU. The predictor generation formula is shown as in Equation (5).
PGBi=(w0×PL0+w1×PL1+RoundingOffset)>>shiftNumGBi Eq. (5)
Herein, PGBi is the final predictor of GBi, w0 and w1 are the selected GBi weights applied to predictors (PL0 and PL1) of list 0 (L0) and list 1 (L1), respectively. RoundingOffsetGBi and shiftNumGBi are used to normalize the final predictor in GBi. The supported wl weight set is {−¼, ⅜, ½, ⅝, 5/4}, in which the five weights correspond to one equal weight pair and four unequal weight pairs. The blending gain, i.e., sum of w1 and w0, is fixed to 1.0. Therefore, the corresponding w0 weight set is {5/4, ⅝, ½, ⅜, −¼}. The weight pair selection is at CU-level.
For non-low delay pictures, the weight set size is reduced from five to three, where the w1 weight set is {⅜, ½, ⅝} and the w0 weight set is {⅝, ½, ⅜}. The weight set size reduction for non-low delay pictures is applied to the BMS2.1 GBi and all the GBi tests in this contribution.
2.8.1 GBi Encoder Bug Fix
To reduce the GBi encoding time, in current encoder design, the encoder will store uni-prediction motion vectors estimated from GBi weight equal to 4/8, and reuse them for uni-prediction search of other GBi weights. This fast encoding method is applied to both translation motion model and affine motion model. In VTM2.0, 6-parameter affine model was adopted together with 4-parameter affine model. The BMS2.1 encoder does not differentiate 4-parameter affine model and 6-parameter affine model when it stores the uni-prediction affine MVs when GBi weight is equal to 4/8. Consequently, 4-parameter affine MVs may be overwritten by 6-parameter affine MVs after the encoding with GBi weight 4/8. The stored 6-parameter affine MVs may be used for 4-parameter affine ME for other GBi weights, or the stored 4-parameter affine MVs may be used for 6-parameter affine ME. The proposed GBi encoder bug fix is to separate the 4-parameter and 6-parameter affine MVs storage. The encoder stores those affine MVs based on affine model type when GBi weight is equal to 4/8, and reuse the corresponding affine MVs based on the affine model type for other GBi weights.
2.8.2 GBi Encoder Speed Up
In this existing implementation, five encoder speed-up methods are proposed to reduce the encoding time when GBi is enabled.
(1) Skipping Affine Motion Estimation for Some GBi Weights Conditionally
In BMS2.1, affine ME including 4-parameter and 6-parameter affine ME is performed for all GBi weights. We propose to skip affine ME for those unequal GBi weights (weights unequal to 4/8) conditionally. Specifically, affine ME will be performed for other GBi weights if and only if the affine mode is selected as the current best mode and it is not affine merge mode after evaluating the GBi weight of 4/8. If current picture is non-low-delay picture, the bi-prediction ME for translation model will be skipped for unequal GBi weights when affine ME is performed. If affine mode is not selected as the current best mode or if affine merge is selected as the current best mode, affine ME will be skipped for all other GBi weights.
(2) Reducing the Number of Weights for RD Cost Checking for Low-Delay Pictures in the Encoding for 1-Pel and 4-Pel MVD Precision
For low-delay pictures, there are five weights for RD cost checking for all MVD precisions including ¼-pel, 1-pel and 4-pel. The encoder will check RD cost for ¼-pel MVD precision first. We propose to skip a portion of GBi weights for RD cost checking for 1-pel and 4-pel MVD precisions. We order those unequal weights according to their RD cost in ¼-pel MVD precision. Only the first two weights with the smallest RD costs, together with GBi weight 4/8, will be evaluated during the encoding in 1-pel and 4-pel MVD precisions. Therefore, three weights at most will be evaluated for 1-pel and 4-pel MVD precisions for low delay pictures.
(3) Conditionally Skipping Bi-Prediction Search when the L0 and L1 Reference Pictures are the Same
For some pictures in RA, the same picture may occur in both reference picture lists (list-0 and list-1). For example, for random access coding configuration in CTC, the reference picture structure for the first group of pictures (GOP) is listed as follows.
Note that pictures 16, 8, 4, 2, 1, 12, 14 and 15 have the same reference picture(s) in both lists. For bi-prediction for these pictures, it is possible that the L0 and L1 reference pictures are the same. We propose that the encoder skips bi-prediction ME for unequal GBi weights when 1) two reference pictures in bi-prediction are the same and 2) temporal layer is greater than 1 and 3) the MVD precision is ¼-pel. For affine bi-prediction ME, this fast skipping method is only applied to 4-parameter affine ME.
(4) Skipping RD Cost Checking for Unequal GBi Weight Based on Temporal Layer and the POC Distance Between Reference Picture and Current Picture
We propose to skip those RD cost evaluations for those unequal GBi weights when the temporal layer is equal to 4 (highest temporal layer in RA) or the POC distance between reference picture (either list-0 or list-1) and current picture is equal to 1 and coding QP is greater than 32.
(5) Changing Floating-Point Calculation to Fixed-Point Calculation for Unequal GBi Weight During ME
For existing bi-prediction search, the encoder will fix the MV of one list and refine MV in another list. The target is modified before ME to reduce the computation complexity. For example, if the MV of list-1 is fixed and encoder is to refine MV of list-0, the target for list-0 MV refinement is modified with Equation (6). O is original signal and P1 is the prediction signal of list-1. w is GBi weight for list-1.
T=((O<<3)−w*P1)*(1/(8−w)) Eq. (6)
Herein, the term (1/(8−w)) is stored in floating point precision, which increases computation complexity. We propose to change Equation (6) to fixed-point as in Equation (7).
T=(O*a1−P1*a2+round)>>N Eq. (7)
where a1 and a2 are scaling factors and they are calculated as:
γ=(1<<N)/(8−w); a1=γ<<3, a2=γ*w; round=1<<(N−1)
2.8.3 CU Size Constraint for GBi
In this method, GBi is disabled for small CUs. In inter prediction mode, if bi-prediction is used and the CU area is smaller than 128 luma samples, GBi is disabled without any signaling.
2.9 Examples of Bi-Directional Optical Flow (BDOF or BIO)
2.9.1 Overview of BDOF
In BIO, motion compensation is first performed to generate the first predictions (in each prediction direction) of the current block. The first predictions are used to derive the spatial gradient, the temporal gradient and the optical flow of each sub-block or pixel within the block, which are then used to generate the second prediction, e.g., the final prediction of the sub-block or pixel. The details are described as follows.
The bi-directional optical flow (BIO) method is a sample-wise motion refinement performed on top of block-wise motion compensation for bi-prediction. In some implementations, the sample-level motion refinement does not use signaling.
Let I(k) be the luma value from reference k (k=0, 1) after block motion compensation, and denote ∂I(k)/∂x and ∂I(k)/∂y as the horizontal and vertical components of the I(k) gradient, respectively. Assuming the optical flow is valid, the motion vector field (vx, vy) is given by:
∂I(k)/∂t+vx∂I(k)/∂x+vy∂I(k)/∂y=0 Eq. (8)
Combining this optical flow equation with Hermite interpolation for the motion trajectory of each sample results in a unique third-order polynomial that matches both the function values I(k) and derivatives ∂I(k)/∂x and ∂I(k)/∂y at the ends. The value of this polynomial at t=0 is the BIO prediction:
predBIO=½·(I(0)+I(1)+vx/2·(τ1∂I(1)/∂x−τ0∂I(0)/∂x)+vy/2·(τ1∂I(1)/∂y−τ0∂I(0)/∂y)). Eq. (9)
The motion vector field (vx, vy) is determined by minimizing the difference Δ between values in points A and B.
Δ=(I(0)−I(1)0+vx(τ1∂I(1)/∂x+τ0∂I(0)/∂x)+vy(τ1∂I(1)/∂y+τ0I(0)/∂y)) Eq. (10)
All values in the above equation depend on the sample location, denoted as (i′,j′). Assuming the motion is consistent in the local surrounding area, Δ can be minimized inside the (2M+1)×(2M+1) square window Ω centered on the currently predicted point (i,j), where M is equal to 2:
For this optimization problem, the JEM uses a simplified approach making first a minimization in the vertical direction and then in the horizontal direction. This results in the following:
where,
In order to avoid division by zero or a very small value, regularization parameters r and m can be introduced in Eq. (12) and Eq. (13), where:
r=500·4d-8 Eq. (15)
m=700·4d-8 Eq. (16)
Here, d is bit depth of the video samples.
In order to keep the memory access for BIO the same as for regular bi-predictive motion compensation, all prediction and gradients values, I(k), ∂I(k)/∂x, ∂I(k)/∂y, are calculated for positions inside the current block.
With BIO, it is possible that the motion field can be refined for each sample. To reduce the computational complexity, a block-based design of BIO is used in the JEM. The motion refinement can be calculated based on a 4×4 block. In the block-based BIO, the values of sn in Eq. (12) of all samples in a 4×4 block can be aggregated, and then the aggregated values of sn in are used to derived BIO motion vectors offset for the 4×4 block. More specifically, the following formula can used for block-based BIO derivation:
Here, bk denotes the set of samples belonging to the k-th 4×4 block of the predicted block. sn in Eq. (12) and Eq. (13) are replaced by ((sn,bk)>>4) to derive the associated motion vector offsets.
In some scenarios, MV regiment of BIO may be unreliable due to noise or irregular motion. Therefore, in BIO, the magnitude of MV regiment is clipped to a threshold value. The threshold value is determined based on whether the reference pictures of the current picture are all from one direction. For example, if all the reference pictures of the current picture are from one direction, the value of the threshold is set to 12×214-d; otherwise, it is set to 12×213-d.
Gradients for BIO can be calculated at the same time with motion compensation interpolation using operations consistent with HEVC motion compensation process (e.g., 2D separable Finite Impulse Response (FIR)). In some embodiments, the input for the 2D separable FIR is the same reference frame sample as for motion compensation process and fractional position (fracX,fracY) according to the fractional part of block motion vector. For horizontal gradient ∂I/∂x, a signal is first interpolated vertically using BIOfilterS corresponding to the fractional position fracY with de-scaling shift d−8. Gradient filter BIOfilterG is then applied in horizontal direction corresponding to the fractional position fracX with de-scaling shift by 18-d. For vertical gradient ∂I/∂y, a gradient filter is applied vertically using BIOfilterG corresponding to the fractional position fracY with de-scaling shift d−8. The signal displacement is then performed using BIOfilterS in horizontal direction corresponding to the fractional position fracX with de-scaling shift by 18-d. The length of interpolation filter for gradients calculation BIOfilterG and signal displacement BIOfilterF can be shorter (e.g., 6-tap) in order to maintain reasonable complexity. Table 1 shows example filters that can be used for gradients calculation of different fractional positions of block motion vector in BIO. Table 2 shows example interpolation filters that can be used for prediction signal generation in BIO.
In the JEM, BIO can be applied to all bi-predicted blocks when the two predictions are from different reference pictures. When Local Illumination Compensation (LIC) is enabled for a CU, BIO can be disabled.
In some embodiments, OBMC is applied for a block after normal MC process. To reduce the computational complexity, BIO may not be applied during the OBMC process. This means that BIO is applied in the MC process for a block when using its own MV and is not applied in the MC process when the MV of a neighboring block is used during the OBMC process.
2.9.2 Examples of BIO in VTM-3.0 as Proposed in JVET-L0256
Step 1: Judge whether BIO is applicable (W/H are width/height of current block)
BIO is not applicable if
BIO is not used if total SAD between the two reference blocks (denoted as R0 and R1) is smaller than a threshold, wherein
Step 2: Data Preparation
For a W×H block, (W+2)×(H+2) samples are interpolated.
The inner W×H samples are interpolated with the 8-tap interpolation filter as in normal motion compensation.
The four side outer lines of samples (black circles in
For each position, gradients are calculated on the two reference blocks (R0 and R1).
Gx0(x,y)=(R0(x+1,y)−R0(x−1,y))>>4
Gy0(x,y)=(R0(x,y+1)−R0(x,y−1))>>4
Gx1(x,y)=(R1(x+1,y)−R1(x−1,y))>>4
Gy1(x,y)=(R1(x,y+1)−R1(x,y−1))>>4
For each position, internal values are calculated as:
T1=(R0(x,y)>>6)−(R1(x,y)>>6),T2=(Gx0(x,y)+Gx1(x,y))>>3,T3=(Gy0(x,y)+Gy1(x,y))>>3; and
B1(x,y)=T2*T2,B2(x,y)=T2*T3,B3(x,y)=−T1*T2,B5(x,y)=T3*T3,B6(x,y)=−T1*T3
Step 3: Calculate Prediction for Each Block
BIO is skipped for a 4×4 block if SAD between the two 4×4 reference blocks is smaller than a threshold.
Calculate Vx and Vy.
Calculate the final prediction for each position in the 4×4 block:
b(x,y)(Vx(Gx0(x,y)−Gx1(x,y))+Vy(Gy0(x,y)−Gy1(x,y))+1)>>1
P(x,y)(R0(x,y)+R1(x,y)+b(x,y)+offset)>>shift
Herein, b(x,y) is known as a correction item.
2.9.3 BIO in VTM-4.0
JVET-M0063, which proposed to round the results of calculation in BDOF depending on bit-depth was adopted into VTM-4.0.
JVET-M0487 was adopted into VTM-4.0, which removed the bi-linear filtering and fetched the nearest integer pixel of the reference block to pad the four side outer lines of samples (black circles in
The working draft related to BIO in VTM-4.0 are shown as below (from JVET-M1001)
2.9.4 Fractional Sample Interpolation Process
General
Inputs to this process are:
In a bi-prediction operation, for the prediction of one block region, two prediction blocks, formed using a motion vector (MV) of list0 and a MV of list1, respectively, are combined to form a single prediction signal. In the decoder-side motion vector refinement (DMVR) method, the two motion vectors of the bi-prediction are further refined by a bilateral template matching process. The bilateral template matching applied in the decoder to perform a distortion-based search between a bilateral template and the reconstruction samples in the reference pictures in order to obtain a refined MV without transmission of additional motion information.
In DMVR, a bilateral template is generated as the weighted combination (i.e. average) of the two prediction blocks, from the initial MV0 of list0 and MV1 of list1, respectively, as shown in
DMVR is applied for the merge mode of bi-prediction with one MV from a reference picture in the past and another from a reference picture in the future, without the transmission of additional syntax elements. In the JEM, when LIC, affine motion, FRUC, or sub-CU merge candidate is enabled for a CU, DMVR is not applied.
2.11 JVET-N0236
This contribution proposes a method to refine the sub-block based affine motion compensated prediction with optical flow. After the sub-block based affine motion compensation is performed, prediction sample is refined by adding a difference derived by the optical flow equation, which is referred as prediction refinement with optical flow (PROF). The proposed method can achieve inter prediction in pixel level granularity without increasing the memory access bandwidth.
To achieve a finer granularity of motion compensation, this contribution proposes a method to refine the sub-block based affine motion compensated prediction with optical flow. After the sub-block based affine motion compensation is performed, luma prediction sample is refined by adding a difference derived by the optical flow equation. The proposed PROF (prediction refinement with optical flow) is described as following four steps.
Step 3) The luma prediction refinement (denoted ΔI) as is calculated by the optical flow equation.
ΔI(i,j)=gx(i,j)*Δvx(i,j)+gy(i,j)*Δvy(i,j)
where the delta MV (denoted as Δv(i,j)) is the difference between pixel MV computed for sample location (i,j), denoted by v(i,j), and the sub-block MV of the sub-block to which pixel (i,j) belongs, as shown in
Since the affine model parameters and the pixel location relative to the sub-block center are not changed from sub-block to sub-block, Δv(i,j) can be calculated for the first sub-block, and reused for other sub-blocks in the same CU. Let x and y be the horizontal and vertical offset from the pixel location to the center of the sub-block, Δv(x,y) can be derived by the following equation,
For 4-parameter affine model,
For 6-parameter affine model
where (v0x, v0y), (v1x, v1y), (v2x, v2y) are the top-left, top-right and bottom-left control point motion vectors, w and h are the width and height of the CU.
Step 4) Finally, the luma prediction refinement is added to the sub-block prediction I(i,j). The final prediction I′ is generated as the following equation.
I′(i,j)=I(i,j)+ΔI(i,j)
Some Details in JVET-N0236
In JVET-N0510, phase-variant affine subblock motion compensation (MC) is proposed. The conventional two stage horizontal-vertical interpolation is applied. However, unlike the phase-invariant block-based MC that uses the same horizontal filter for all sample rows and the same vertical filter for all sample columns, different phases of filters can be applied to different sample rows and different sample columns in the affine subblock.
To better approximate the affine motion model in an affine subblock, phase-variant MC is applied to the subblock. In the proposed method, the affine coded block is also divided into 4×4 subblocks, and a subblock MV is derived for each subblock as done in VTM4.0. The MC of each subblock is divided into two stages. The first stage is to filter an (4+L−1)×(4+L−1) reference block window with (4+L−1) rows of horizontal filtering, where the L is the filter tap length of the interpolation filer. However, different from the translational MC, in the proposed phase-variant affine subblock MC, the filter phase of each sample row is different. For each sample row, MVx is derived as follows.
MVx=(subblockMVx<<7+dMvVerX×(rowIdx−L/2−2))>>7
The filter phase of each sample row is derived from the MVx. The subblockMVx is the x component of the MV of the derived subblockMV as done in VTM4.0. The rowIdx is the sample row index. The dMvVerX is (cuBottomLeftCPMVx−cuTopLeftCPMVx)<<(7−log 2LumaCbHeight), where cuBottomLeftCPMVx is the x component of the CU bottom left control point MV, cuTopLeftCPMVx is the x component of the CU top left control point MV, and LumaCbHeight is the log 2 of the height of the luma coding block (CB).
After the horizontal filtering, a 4×(4+L−1) horizontally filtered samples are generated.
In the second stage, the 4×(4+L−1) horizontally filtered samples (orange samples in
MVy=(subblockMVy<<7+dMvHorY×(columnIdx−2))>>7 (Equation 2)
The filter phase of each sample column is derived from the MVy. The subblockMVy is the y component of the MV of the derived subblock MV as done in VTM4.0. The columnIdx is the sample column index. The dMvHorY is (cuTopRightCPMVy−cuTopLeftCPMVy)<<(7−log 2LumaCbWidth), where cuTopRightCPMVy is the y component of the CU top right control point MV, cuTopLeftCPMVy is the y component of the CU top left control point MV, and log 2LumaCbWidth is the log 2 of the width of the luma CB.
After the vertical filtering, 4×4 affine subblock prediction samples are generated.
In this proposal, the used interpolation filter sets are the same as those in VTM4.0. The only difference is that the horizontal filter phases on one sample row are different and the vertical filter phases on one sample column are different. As for the number of filtering operations for each affine subblock in the proposed method, it is the same as that in VTM4.0.
3. Drawbacks of Existing Implementations
Some existing implementations suffer from the following drawbacks:
Embodiments of the presently disclosed technology overcome the drawbacks of existing implementations, thereby providing video coding with higher coding efficiencies. The methods for prediction refinement with optical flow, based on the disclosed technology, may enhance both existing and future video coding standards, is elucidated in the following examples described for various implementations. The examples of the disclosed technology provided below explain general concepts, and are not meant to be interpreted as limiting. In an example, unless explicitly indicated to the contrary, the various features described in these examples may be combined.
Denote reference picture of current picture from list 0 and list 1 by Ref0 and Ref1 respectively, denote τ0=POC(current)−POC(Ref0), τ1=POC(Ref1)−POC(current), and denote reference block of the current block from Ref0 and Ref1 by refblk0 and refblk1 respectively. For a subblock in current block, MV of its corresponding subblock in refblk0 pointing to refblk1 is denoted by (vx, vy). MVs of the subblock in Ref0 and Ref1 are denoted by (mvL0x, mvL0y) and (mvL1x, mvL1y) respectively.
Shift(x, s) is defined as Shift(x, s)=(x+off)>>s
SignShift(x, s) is defined as
In an example, offset0 and/or offset1 are set to (1<<n)>>1 or (1<<(n−1)). In another example, offset0 and/or offset1 are set to 0. In yet another example, offset0=offset1=((1<<n)>>1)−1 or ((1<<(n−1)))−1.
Clip3(x, min, max) is defined as
Herein, Max (a, b)=a>=b?a: b, and Min (a, b)=a<=b?a: b.
In the following discussion, an operation between two motion vectors means the operation will be applied to both the two components of the motion vector. For example, MV3=MV1+MV2 is equivalent to MV3x=MV1x+MV2x and MV3y=MV1y+MV2y. alternatively, the operation may be only applied to the horizontal or vertical component of the two motion vectors. The term “absolute value” of a MV (MVx, MVy) may refer to abs(MVx), or abs(MVy), or max(abs(MVx), abs(MVy)) or abs(MVx)+abs(MVy), wherein function abs(x) returns absolute value of x, and function max(x, y) returns the larger one of x and y.
In the following discussion, the left neighboring block, left-bottom neighboring block, above neighboring block, right-above neighboring block and left-above neighboring block are denoted as block A1, A0, B1, B0 and B2 as shown in
The examples described above may be incorporated in the context of the methods described below, e.g., methods 2910 to 2950, which may be implemented at a video decoder or a video encoder.
5. Example Implementations of the Disclosed Technology
The system 4100 may include a coding component 4104 that may implement the various coding or encoding methods described in the present document. The coding component 4104 may reduce the average bitrate of video from the input 4102 to the output of the coding component 4104 to produce a coded representation of the video. The coding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the coding component 4104 may be either stored, or transmitted via a communication connected, as represented by the component 4106. The stored or communicated bitstream (or coded) representation of the video received at the input 4102 may be used by the component 4108 for generating pixel values or displayable video that is sent to a display interface 4110. The process of generating user-viewable video from the bitstream representation is sometimes called video decompression. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be appreciated that the coding tools or operations are used at an encoder and corresponding decoding tools or operations that reverse the results of the coding will be performed by a decoder.
Examples of a peripheral bus interface or a display interface may include universal serial bus (USB) or high definition multimedia interface (HDMI) or Displayport, and so on. Examples of storage interfaces include SATA (serial advanced technology attachment), PCI, IDE interface, and the like. The techniques described in the present document may be embodied in various electronic devices such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and/or video display.
Some embodiments of the disclosed technology include making a decision or determination to enable a video processing tool or mode. In an example, when the video processing tool or mode is enabled, the encoder will use or implement the tool or mode in the processing of a block of video, but may not necessarily modify the resulting bitstream based on the usage of the tool or mode. That is, a conversion from the block of video to the bitstream representation of the video will use the video processing tool or mode when it is enabled based on the decision or determination. In another example, when the video processing tool or mode is enabled, the decoder will process the bitstream with the knowledge that the bitstream has been modified based on the video processing tool or mode. That is, a conversion from the bitstream representation of the video to the block of video will be performed using the video processing tool or mode that was enabled based on the decision or determination.
Some embodiments of the disclosed technology include making a decision or determination to disable a video processing tool or mode. In an example, when the video processing tool or mode is disabled, the encoder will not use the tool or mode in the conversion of the block of video to the bitstream representation of the video. In another example, when the video processing tool or mode is disabled, the decoder will process the bitstream with the knowledge that the bitstream has not been modified using the video processing tool or mode that was disabled based on the decision or determination.
In the present document, the term “video processing” may refer to video encoding video decoding, video compression or video decompression. For example, video compression algorithms may be applied during conversion from pixel representation of a video to a corresponding bitstream representation or vice versa. The bitstream representation of a current video block may, for example, correspond to bits that are either co-located or spread in different places within the bitstream, as is defined by the syntax. For example, a macroblock may be encoded in terms of transformed and coded error residual values and also using bits in headers and other fields in the bitstream.
It will be appreciated that the disclosed methods and techniques will benefit video encoder and/or decoder embodiments incorporated within video processing devices such as smartphones, laptops, desktops, and similar devices by allowing the use of the techniques disclosed in the present document.
Various techniques and embodiments may be described using the following clause-based format.
The first set of clauses describe certain features and aspects of the disclosed techniques in the previous section.
The second set of clauses describe certain features and aspects of the disclosed techniques in the previous section, including for example, Example Implementations 1 to 4.
The third set of clauses describe certain features and aspects of the disclosed techniques in the previous section, including for example, Example Implementations 5 and 6.
From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the presently disclosed technology is not limited except as by the appended claims.
Implementations of the subject matter and the functional operations described in this patent document can be implemented in various systems, digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible and non-transitory computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term “data processing unit” or “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
It is intended that the specification, together with the drawings, be considered exemplary only, where exemplary means an example. As used herein, the use of “or” is intended to include “and/or”, unless the context clearly indicates otherwise.
While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.
Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.
Number | Date | Country | Kind |
---|---|---|---|
PCT/2019/083434 | Apr 2019 | WO | international |
PCT/2019/092762 | Jun 2019 | WO | international |
This application is a continuation of U.S. patent application Ser. No. 17/392,719, filed on Aug. 3, 2021, which is a continuation of International Application No. PCT/CN2020/085662, filed on Apr. 20, 2020, which claims the priority to and benefits of International Patent Application No. PCT/CN2019/083434, filed on Apr. 19, 2019, and International Patent Application No. PCT/CN2019/092762, filed on Jun. 25, 2019. The entire disclosures of the aforementioned applications are incorporated by reference as part of the disclosure of this application.
Number | Name | Date | Kind |
---|---|---|---|
10390029 | Ye et al. | Aug 2019 | B2 |
10448010 | Chen et al. | Oct 2019 | B2 |
10523964 | Chuang et al. | Dec 2019 | B2 |
10560712 | Zou et al. | Feb 2020 | B2 |
10757417 | Zhang et al. | Aug 2020 | B2 |
10778999 | Li et al. | Sep 2020 | B2 |
10819891 | Wang et al. | Oct 2020 | B2 |
10841609 | Liu et al. | Nov 2020 | B1 |
10904565 | Chuang et al. | Jan 2021 | B2 |
11356697 | Zhang et al. | Jun 2022 | B2 |
11368711 | Zhang et al. | Jun 2022 | B2 |
11516497 | Liu et al. | Nov 2022 | B2 |
11570462 | Zhang et al. | Jan 2023 | B2 |
20130107958 | Shimada et al. | May 2013 | A1 |
20130259122 | Sugio et al. | Oct 2013 | A1 |
20150016550 | Kim et al. | Jan 2015 | A1 |
20170134750 | Ikai et al. | May 2017 | A1 |
20170332095 | Zou et al. | Nov 2017 | A1 |
20180098066 | Lee et al. | Apr 2018 | A1 |
20180103257 | Zheng et al. | Apr 2018 | A1 |
20180199057 | Chuang et al. | Jul 2018 | A1 |
20180241998 | Chen et al. | Aug 2018 | A1 |
20180262773 | Chuang et al. | Sep 2018 | A1 |
20180270500 | Li et al. | Sep 2018 | A1 |
20180278950 | Chen et al. | Sep 2018 | A1 |
20180316929 | Li | Nov 2018 | A1 |
20180376166 | Chuang et al. | Dec 2018 | A1 |
20190014342 | Li et al. | Jan 2019 | A1 |
20190020895 | Liu et al. | Jan 2019 | A1 |
20190045214 | Ikai et al. | Feb 2019 | A1 |
20190045215 | Chen et al. | Feb 2019 | A1 |
20190089960 | Chen et al. | Mar 2019 | A1 |
20190104323 | Baylon et al. | Apr 2019 | A1 |
20190387250 | Boyce et al. | Dec 2019 | A1 |
20200045310 | Chen et al. | Feb 2020 | A1 |
20200084457 | Abe et al. | Mar 2020 | A1 |
20200145688 | Zou et al. | May 2020 | A1 |
20200213594 | Liu et al. | Jul 2020 | A1 |
20200213612 | Liu et al. | Jul 2020 | A1 |
20200221122 | Ye et al. | Jul 2020 | A1 |
20200296405 | Huang et al. | Sep 2020 | A1 |
20200304805 | Li et al. | Sep 2020 | A1 |
20200304826 | Li et al. | Sep 2020 | A1 |
20200314443 | Huang et al. | Oct 2020 | A1 |
20200359029 | Liu et al. | Nov 2020 | A1 |
20200382771 | Liu et al. | Dec 2020 | A1 |
20200382795 | Zhang et al. | Dec 2020 | A1 |
20200396453 | Zhang et al. | Dec 2020 | A1 |
20200396465 | Zhang et al. | Dec 2020 | A1 |
20200404255 | Zhang et al. | Dec 2020 | A1 |
20210067783 | Liu et al. | Mar 2021 | A1 |
20210092390 | Chen et al. | Mar 2021 | A1 |
20210227211 | Liu et al. | Jul 2021 | A1 |
20210266530 | Liu et al. | Aug 2021 | A1 |
20210281855 | Skupin et al. | Sep 2021 | A1 |
20210368198 | Zhang et al. | Nov 2021 | A1 |
20210368199 | Zhang et al. | Nov 2021 | A1 |
20210368203 | Zhang et al. | Nov 2021 | A1 |
20210377558 | Xiu et al. | Dec 2021 | A1 |
20210385482 | Liu et al. | Dec 2021 | A1 |
20220329842 | Liu et al. | Oct 2022 | A1 |
Number | Date | Country |
---|---|---|
102754444 | Oct 2012 | CN |
102939753 | Feb 2013 | CN |
104170381 | Nov 2014 | CN |
104396248 | Mar 2015 | CN |
105409221 | Mar 2016 | CN |
107113424 | Aug 2017 | CN |
107211151 | Sep 2017 | CN |
107431822 | Dec 2017 | CN |
107710762 | Feb 2018 | CN |
107925772 | Apr 2018 | CN |
107925773 | Apr 2018 | CN |
108293118 | Jul 2018 | CN |
108432250 | Aug 2018 | CN |
108541375 | Sep 2018 | CN |
108781294 | Nov 2018 | CN |
108886619 | Nov 2018 | CN |
109076237 | Dec 2018 | CN |
109155855 | Jan 2019 | CN |
109417639 | Mar 2019 | CN |
109479130 | Mar 2019 | CN |
109496430 | Mar 2019 | CN |
3413563 | Dec 2018 | EP |
201821156 | Feb 2019 | GB |
20180128955 | Dec 2018 | KR |
201832557 | Sep 2018 | TW |
2010027457 | Mar 2010 | WO |
2015165030 | Nov 2015 | WO |
2015179898 | Dec 2015 | WO |
2016072750 | May 2016 | WO |
2016130801 | Aug 2016 | WO |
2017142939 | Aug 2017 | WO |
2017184970 | Oct 2017 | WO |
2017192898 | Nov 2017 | WO |
2017197146 | Nov 2017 | WO |
2018048265 | Mar 2018 | WO |
2018061563 | Apr 2018 | WO |
2018105579 | Jun 2018 | WO |
2018128417 | Jul 2018 | WO |
2018130206 | Jul 2018 | WO |
2018166357 | Sep 2018 | WO |
2018169989 | Sep 2018 | WO |
2018199468 | Nov 2018 | WO |
2018237303 | Dec 2018 | WO |
2019040075 | Feb 2019 | WO |
2020190896 | Sep 2020 | WO |
Entry |
---|
“Optical Flow” USPTO Library Search Query, 2020, retrieved Mar. 25, 2022. |
Office Action from Indian Patent Application No. 202147046022 dated Apr. 13, 2022. |
Final Office Action from U.S. Appl. No. 17/392,658 dated Mar. 16, 2022. |
Notice of Allowance from U.S. Appl. No. 17/405,374 dated Apr. 14, 2022. |
Li et al. “CE4-Related: Alignment of BDOF Refinement Process with PROF,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O0123, 2019. |
Bross et al. “Versatile Video Coding (Draft 4),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA Jan. 9-18, 2019, document JVET-M1001, 2019. |
Bross et al. “Versatile Video Coding (Draft 5),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH. Mar. 19-27, 2019, document JVET-N1001, 2019. |
Bross et al. “Versatile Video Coding (Draft 6),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O2001, 2019. |
Chen et al. “Algorithm Description of Joint Exploration Test Model 7 (JEM 7),” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 7th Meeting: Torino, IT, Jul. 13-21, 2017, document JVET-G1001, 2017. |
Chen et al. “BoG Report on CE2 Sub-Block Based Motion Prediction-Related Contributions,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0776, 2019. |
Chuang et al. “CE2-Related: Phase-Variant Affine Subblock Motion Compensation,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting Geneva, CH, Mar. 19-27, 2019, document JVET-N0510, 2019. |
Chujoh et al. “Non-CE9: An Improvement of BDOF,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0063, 2019. |
He et al. “Unified Syntax for JVET-O0184/O0250/O0504 on DMVR and BDOF Flag,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, Se, Jul. 3-12, 2019, document JVET-O1140, 2019. |
Henkel et al. “Non-CE4: Switched Half-Pel Interpolation Filter,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0309, 2019. |
Henkel et al. “CE4: Switchable Interpolaton Filter (CE4-1.1, CE4-1.2, CE4-1.3, CE4-1.4, CE4-1.5, CE4-1.6, CE4-1.7),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE Jul. 3-12, 2019, document JVET-O0057, 2019. |
“Information Technology—High Efficiency Coding and Media Delivery in Heterogeneous Environments—Part 2: High Efficiency Video Coding” Apr. 20, 2018, ISO/DIS 23008, 4th Edition. |
Kim et al. “Non-CE3: Determination of Wide-Angle Mode Using the Size of a Coding Block,” JVET-N0216, Mar. 2019. |
Li et al. “Non-CE-2: Combination of Affine MV Clip and Prediction Refinement with Optical Flow,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0737, 2019. |
Luo et al. “CE2-Related: Prediction Refinement with Optical Flow for Affine Mode,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0236, 2019. |
Luo et al. “CE4: Prediction Refinement with Optical Flow for Affine Mode (Test 2.1),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gothenburg, SE, Jul. 3-12, 2019, document JVET-O0070, 2019. |
Rosewarne et al. “High Efficiency Video Coding (HEVC) Test Model 16 (HM 16) Improved Encoder Description Update 7,” Joint Collaborative Team on Video Coding (JCT-VC) ITU-T SG 16 WP3 and ISO/IEC JTC1/SC29/WG11, 25th Meeting, Chengdu, CN, Oct. 14-21, 2016, document JCTVC-Y1002, 2016. |
Su et al. “CE4.4.1: Generalized Bi-Prediction for Intercoding,” Joint Video Exploration Team of ISO/IEC JTC 1/SC 29/WG 11 and ITU-T SG 16, Ljubljana, Jul. 10-18, 2018, document No. JVET-K0248, 2018. |
Su et al. “CE4-Related: Generalized Bi-Prediction Improvements Combined from JVET-L0197 and JVET-L0296,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0646, 2018. |
Xiu et al. “CE9-Related: Complexity Reduction and Bit-Width Control for Bi-Directional Optical Flow (BIO),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L0256, 2018. |
Xiu et al. “Simplifications on Bi-Directional Optical Flow (BDOF),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting: Marrakech, MA Jan. 9-18, 2019, document JVET-M0487, 2019. |
Zhang et al. “CE2-5.5: History-Parameter-based Affine Model Inheritance,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0263, 2019. |
JEM-7.0: https://jvet.hhi.fraunhofer.de/svn/svn_HMJEMSoftware/tags/ HM-16.6-JEM-7.0. |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/085658 dated Jul. 20, 2020 (9 pages). |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/085662 dated Jul. 21, 2020 (9 pages). |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/085663 dated Jul. 14, 2020 (10 pages). |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/085666 dated Jul. 7, 2020 (9 pages). |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/094156 dated Sep. 2, 2020 (10 pages). |
Notice of Allowance from U.S. Appl. No. 17/392,719 dated Oct. 14, 2021. |
Bross et al. “Versatile Video Coding (Draft 3),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC ITC 1/SC 29/WG 11 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-L1001, 2018. |
Huang et al. “CE2-Related: Affine Motion Compensation Using 2x2 Subblock,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0273, 2019. |
Huang et al. “CE2-Related: Simplified Prediction Refinement for Affine Motion Compensation,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0504, 2019. |
Karczewicz et al. “Geometry Tranformation-based Adaptive In-Loop Filter,” 2016, IEEE Qualcomm Technologies Inc. San Diego, CA, USA. |
Li et al. “Non-CE4: On Prediction Refinement with Optical Flow,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 15th Meeting, Gotehnburg, SE, Jul. 3-12, 2019, document JVET-00553, 2019. |
Lim et al. “CE2: Subsampled Laplacian Calculation (Test 6.1, 6.2, 6.3, and 6.4),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting, Macao, CN, Oct. 3-12, 2018, document JVET-0147, 2018. |
Lu et al. “CE12: Mapping Functions (Test CE12-1 and CE12-2),” Joint Video Experts Team (JVET) of ITU-t SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0427, 2019. |
Seregin et al. “CE5: Summary Report on Adaptive Loop Filter,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0025, 2019. |
Taquet et al. “Non-Linear Adaptive Loop Filter,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 13th Meeting, Marrakech, MA, Jan. 9-18, 2019, document JVET-M0385, 2019. |
Taquet et al. “CE5: Results of Tests CE5-3.1 to CE5-3.4 on Non-Linear Adaptive Filter,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, Mar. 19-27, 2019, document JVET-N0242, 2019. |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/082941 dated Jun. 30, 2020 (12 pages). |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/082976 dated Jul. 1, 2020 (11 pages). |
Non Final Office Action from U.S. Appl. No. 17/392,658 dated Nov. 26, 2021. |
Non Final Office Action from U.S. Appl. No. 17/392,778 dated Nov. 26, 2021. |
Non Final Office Action from U.S. Appl. No. 17/405,374 dated Dec. 2, 2021. |
Xiu et al. “CE9-Related: Improvements on Bi-Directional Optical Flow (BDOF),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 14th Meeting, Geneva, CH, 19-278 Mar. 2019, document JVET-N0325, 2019. |
Extended European Search Report from European Patent Application No. 20782029.1 dated Jul. 15, 2022 (8 pages). |
Extended European Search Report from European Patent Application No. 20790449.1 dated Jun. 15, 2022 (7 pages). |
Zhang et al. “CE4: History-based Motion Vector Prediction (Test 4.4.7)” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 12th Meeting: Macao, CN, Oct. 3-12, 2018, document JVET-L0266, 2018. |
Non Final Office Action from U.S. Appl. No. 17/838,498 dated Sep. 1, 2023. |
Number | Date | Country | |
---|---|---|---|
20220070490 A1 | Mar 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17392719 | Aug 2021 | US |
Child | 17523232 | US | |
Parent | PCT/CN2020/085662 | Apr 2020 | US |
Child | 17392719 | US |