This document is related to video coding and decoding technologies.
Digital video 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.
The disclosed techniques may be used by video decoder or encoder embodiments for allowing a flexible signaling and use of motion vector precision for bi-predictive encoding in which up to two lists of reference frames are used by motion vectors. In one example aspect, different precisions may be allowed for different reference lists. The precision used for each reference frame may be content dependent or defined by an a priori set of rules.
In one example aspect, a method of processing a video bitstream includes determining a motion precision set based on coding information of a current block. A conversion between a video block and a coded representation of the video block is performed based on the motion precision set. The conversion corresponds to a reconstruction of the current block.
In another example aspect, a MVD precision of a current block from a motion precision set is determined based on a selected motion precision set and a signaled motion vector difference (MVD) precision index. A conversion between a video block and a coded representation of the video block using a MVD is performed based on the MVD precision. The MVD represents a difference between a predicted motion vector and an actual motion vector used during motion compensation processing.
In another example aspect, the above-described method may be implemented by a video decoder apparatus that comprises a processor.
In another example aspect, the above-described method may be implemented by a video encoder apparatus comprising a processor for decoding encoded video during video encoding process.
In yet another example aspect, these methods may be embodied in the form of processor-executable instructions and stored on a computer-readable program medium.
These, and other, aspects are further described in the present document.
The present document provides various techniques that can be used by a decoder of video bitstreams to improve the quality of decompressed or decoded digital video. Furthermore, a video encoder may also implement these techniques during the process of encoding in order to reconstruct decoded frames used for further encoding.
Section headings are used in the present document for ease of understanding and do not limit the embodiments and techniques to the corresponding sections. As such, embodiments from one section can be combined with embodiments from other sections.
Furthermore, while certain embodiments are described with reference to Versatile Video Coding or other specific video codecs, the disclosed techniques are applicable to other video coding technologies also. Furthermore, while some embodiments describe video coding steps in detail, it will be understood that corresponding steps decoding that undo the coding will be implemented by a decoder. Furthermore, the term video processing encompasses video coding or compression, video decoding or decompression and video transcoding in which video pixels are represented from one compressed format into another compressed format or at a different compressed bitrate.
Video coding standards have evolved primarily through the development of the well-known ITU-T and ISO/IEC standards. The ITU-T produced H.261 and H.263, ISO/IEC produced MPEG-1 and MPEG-4 Visual, and the two organizations jointly produced the H.262/MPEG-2 Video and H.264/MPEG-4 Advanced Video Coding (AVC) and H.265/HEVC standards. Since H.262, the video coding standards are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized. To explore the future video coding technologies beyond HEVC, Joint Video Exploration Team (JVET) was founded by VCEG and MPEG jointly in 2015. Since then, many new methods have been adopted by JVET and put into the reference software named Joint Exploration Model (JEM). In April 2018, the Joint Video Expert Team (JVET) between VCEG (Q6/16) and ISO/IEC JTC1 SC29/WG11 (MPEG) was created to work on the VVC standard targeting at 50% bitrate reduction compared to HEVC.
Each inter-predicted PU has motion parameters for one or two reference picture lists. Motion parameters include a motion vector and a reference picture index. Usage of one of the two reference picture lists may also be signaled using inter_pred_idc. 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 (to be more precise, motion vector difference compared to a motion vector predictor), corresponding reference picture index for each reference picture list and reference picture list usage are signaled explicitly per each PU. Such a mode is named Advanced motion vector prediction (AMVP) in this document.
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.
The following text provides the details on the inter prediction modes specified in HEVC Verson 1. The description will start with the 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 is specified in the HEVC standard and can be summarized according to the following sequence of steps:
These steps are also schematically depicted in
In the following, the operations associated with the aforementioned steps are detailed.
In the derivation of spatial merge candidates, a maximum of four merge candidates are selected among candidates located in the positions depicted in
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 signalled in the slice header. The scaled motion vector for temporal merge candidate is obtained as illustrated by the dotted line in
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
Besides spatial and 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 spatial and 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. As an example,
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. Finally, no redundancy check is performed on these candidates.
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 neighbourhood 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, HEVC defines the motion estimation region (MER) whose size is signalled in the picture parameter set using the “log2_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.
AMVP (advanced motion vector prediction) exploits spatio-temporal correlation of motion vector with neighbouring PUs, which is used for explicit transmission of motion parameters. For each reference picture list, a motion vector candidate list is constructed by firstly checking availability of left, above temporally neighbouring 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 signalling, 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
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 depicted 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.
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 depicted in
The no-spatial-scaling cases are checked first followed by the spatial scaling. Spatial scaling is considered when the POC is different between the reference picture of the neighboring 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 MV candidates. Otherwise, spatial scaling is not allowed for the above motion vector.
In a spatial scaling process, the motion vector of the neighbouring PU is scaled in a similar manner as for temporal scaling, as depicted as
Apart for 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 (see
In the JEM with QTBT (Quadtree plus Binary Tree), each CU can have at most one set of motion parameters for each prediction direction. 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.
To preserve more accurate motion field for sub-CU motion prediction, the motion compression for the reference frames is currently disabled.
In the alternative temporal motion vector prediction (ATMVP) method, the motion vectors temporal motion vector prediction (TMVP) is modified by fetching multiple sets of motion information (including motion vectors and reference indices) from blocks smaller than the current CU. As shown in
ATMVP predicts the motion vectors of the sub-CUs within a CU in two steps. The first step is to identify the corresponding block in a reference picture with a so-called temporal vector. The reference picture is called the motion source picture. The second step is to split the current CU into sub-CUs and obtain the motion vectors as well as the reference indices of each sub-CU from the block corresponding to each sub-CU, as shown in
In the first step, a reference picture and the corresponding block is determined by the motion information of the spatial neighbouring blocks of the current CU. To avoid the repetitive scanning process of neighbouring blocks, the first merge candidate in the merge candidate list of the current CU 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, in ATMVP, 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 is identified by the temporal vector in the motion source picture, by adding to the coordinate of the current CU the temporal vector. For each sub-CU, the motion information of its corresponding block (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 (i.e. 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 (the motion vector corresponding to reference picture list X) to predict motion vector MVy (with X being equal to 0 or 1 and Y being equal to 1-X) for each sub-CU.
In this 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 neighbours. The first neighbour is the N×N block above sub-CU A (block c). If this block c is not available or is intra coded the other N×N blocks above sub-CU A are checked (from left to right, starting at block c). The second neighbour is a block to the left of the sub-CU A (block b). If block b is not available or is intra coded other blocks to the left of sub-CU A are checked (from top to bottom, staring at block b). The motion information obtained from the neighbouring 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 is derived by following the same procedure of TMVP derivation as specified in HEVC. The motion information of the collocated block at location D is fetched and scaled accordingly. Finally, after retrieving and scaling the motion information, all available motion vectors (up to 3) are averaged separately for each reference list. The averaged motion vector is assigned as the motion vector of the current sub-CU.
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. Up to seven merge candidates are 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 is needed for the two additional merge candidates.
In the JEM, all bins of merge index is context coded by CABAC. While in HEVC, only the first bin is context coded and the remaining bins are context by-pass coded.
In HEVC, 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, as described in section 3.2.2.
SHVC upsampling 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.
Overlapped Block Motion Compensation (OBMC) has previously been used in H.263. In the JEM, unlike in H.263, 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, a MC block is corresponding 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 illustrated in
When OBMC applies to the current sub-block, besides current motion vectors, motion vectors of four connected neighbouring 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 neighbouring sub-block is denoted as PN, with N indicating an index for the neighbouring 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 neighbouring 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 {3/4, 7/8, 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) neighbouring 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 signalled 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 neighbouring block and the left neighbouring 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.
Local Illumination Compensation (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 neighbouring samples of the current CU and their corresponding reference samples. More specifically, as illustrated in
When a CU is coded with merge mode, the LIC flag is copied from neighbouring blocks, in a way similar to motion information copy in merge mode; otherwise, an LIC flag is signalled for the CU to indicate whether LIC applies or not.
When LIC is enabled for a pciture, addtional CU level RD check is needed to determine whether LIC is applied or not for a CU. When LIC is enabled for a CU, 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.
LIC is disabled for the entire picture when there is no obvious illumination change between a current picture and its reference pictures. To identify this situation, histograms of a current picture and every reference picture of the current picture are calculated at the encoder. If the histogram difference between the current picture and every reference picture of the current picture is smaller than a given threshold, LIC is disabled for the current picture; otherwise, LIC is enabled for the current picture.
In HEVC, only translation motion model is applied for motion compensation prediction (MCP). While in the real world, there are many kinds of motion, e.g. zoom in/out, rotation, perspective motions and he other irregular motions. In the JEM, a simplified affine transform motion compensation prediction is applied. As shown
The motion vector field (MVF) of a block is described by the following equation:
where (v0x, v0y) is motion vector of the top-left corner control point, and (v1y, v1y) is motion vector of the top-right corner control point.
In order to further simplify the motion compensation prediction, sub-block based affine transform prediction is applied. The sub-block size M×N is derived as in Equation 2, where MvPre is the motion vector fraction accuracy ( 1/16 in JEM), (v2x, v2y) is motion vector of the bottom-left control point, calculated according to Equation 1.
After derived by Equation 2, M and N should be adjusted downward if necessary to make it a divisor of w and h, respectively.
To derive motion vector of each M×N sub-block, the motion vector of the center sample of each sub-block, as shown in
After MCP, the high accuracy motion vector of each sub-block is rounded and saved as the same accuracy as the normal motion vector.
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 signalled in the bitstream to indicate whether AF_INTER mode is used. In this mode, a candidate list with motion vector pair {(v0, v1)|v0={vA, vB, vC}, v1={vD,vE}} is constructed using the neighbour blocks. As shown in
When a CU is applied in AF_MERGE (affine merge) mode, it gets the first block coded with affine mode from the valid neighbour reconstructed blocks. And the selection order for the candidate block is from left, above, above right, left bottom to above left as shown in
After the CPMV of the current CU v0 and v1 are derived, according to the simplified affine motion model Equation 1, the MVF of the current CU is generated. In order to identify whether the current CU is coded with AF_MERGE mode, an affine flag is signalled in the bitstream when there is at least one neighbour block is coded in affine mode.
Pattern matched motion vector derivation (PMMVD) mode is a special merge mode based on Frame-Rate Up Conversion (FRUC) techniques. With this mode, motion information of a block is not signalled but derived at decoder side.
A FRUC (Frame-Rate Up Conversion) flag is signalled for a CU when its merge flag is true. When the FRUC flag is false, a merge index is signalled and the regular merge mode is used. When the FRUC flag is true, an additional FRUC mode flag is signalled to indicate which method (bilateral matching or template matching) is to be used to derive motion information for the block.
At 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. That is the two matching modes (bilateral matching and template matching) are both 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.
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 which 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 and 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, where W is a width of the CU and H is a height of the CU. 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 (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.
As shown in the
As shown in
The MV candidate set at CU level consists of:
When using bilateral matching, each valid MV of a merge candidate is 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.
Four MVs from the interpolated MV field are also 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.
At the CU level, up to 15 MVs for AMVP CUs and up to 13 MVs for merge CUs are added to the candidate list.
The MV candidate set at sub-CU level consists of:
The scaled MVs from reference pictures are derived as follows. All 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 are limited to the four first ones.
At the sub-CU level, up to 17 MVs are added to the candidate list.
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.
First, the motion field of each reference pictures in both reference lists is traversed at 4×4 block level. For each 4×4 block, if the motion associated to the block passing through a 4x4 block in the current picture (as shown in
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 is 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 is 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|) (4)
where w is a weighting factor which is empirically set to 4, MV and MVs indicate the current MV and the starting MV, respectively. SAD is still 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 always applied since 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. There is no such limitation for the template matching merge mode. 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 is based on a template matching cost as follows:
The inter prediction direction selection is only applied to the CU-level template matching process.
Bi-directional Optical flow (BIO) is sample-wise motion refinement which is performed on top of block-wise motion compensation for bi-prediction. The sample-level motion refinement doesn't use signalling.
Let I(k) be the luma value from reference k (k=0, 1) after block motion compensation, and ∂I(k)/∂x, ∂I(k)/∂y are 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 an equation
∂I(k)/∂t+vx∂I(k)/∂x+vy∂I(k)/∂y=0 . (5)
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, ∂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)) (6)
Here, τ0 and τ1 denote the distances to the reference frames as shown on a
(MVx0/MVx1=MVy0/MVy1=−τ0/τ1).
The motion vector field (vx, vy) is determined by minimizing the difference Δ between values in points A and B (intersection of motion trajectory and reference frame planes on
Δ=(I(0)−I(1)0+vx(τ1∂I(1)/∂x+τ0∂I(0)/∂x)+vy(τ1∂I(1)/∂y+τ0∂I(0)/∂y)) (7)
All values in Equation 7 depend on the sample location (i′, j′), which was omitted from the notation so far. Assuming the motion is consistent in the local surrounding area, we minimize Δ 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
In order to avoid division by zero or a very small value, regularization parameters r and m are introduced in Equations 9 and 10.
r=500·4d-8 (12)
m=700·4d-8 (13)
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 only for positions inside the current block. In Equation 11, (2M+1)×(2M+1) square window Ω centered in currently predicted point on a boundary of predicted block needs to accesses positions outside of the block (as shown in
With BIO, it's 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 is calculated based on 4×4 block. In the block-based BIO, the values of sn in Equation 11 of all samples in a 4×4 block are 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 is used for block-based BIO derivation:
where bk denotes the set of samples belonging to the k-th 4×4 block of the predicted block. sn in Equations 9 and 10 are replaced by ((sn,bk)>>4) to derive the associated motion vector offsets.
In some cases, MV regiment of BIO might be unreliable due to noise or irregular motion. Therefore, in BIO, the magnitude of MV regiment is clipped to a threshold value thBIO. The threshold value is determined based on whether the reference pictures of the current picture are all from one direction. 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 are calculated at the same time with motion compensation interpolation using operations consistent with HEVC motion compensation process (2D separable FIR). The input for this 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. In case of horizontal gradient ∂I/∂x signal first interpolated vertically using BIOfilterS corresponding to the fractional position fracY with de-scaling shift d-8, then gradient filter BIOfilterG is applied in horizontal direction corresponding to the fractional position fracX with de-scaling shift by 18-d. In case of vertical gradient ∂I/∂y first gradient filter is applied vertically using BIOfilterG corresponding to the fractional position frac Y with de-scaling shift d-8, then signal displacement is 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 is shorter (6-tap) in order to maintain reasonable complexity. Table 1 shows the filters used for gradients calculation for different fractional positions of block motion vector in BIO. Table 2 shows the interpolation filters used for prediction signal generation in BIO.
In the JEM, BIO is applied to all bi-predicted blocks when the two predictions are from different reference pictures. When LIC is enabled for a CU, BIO is disabled.
In the JEM, OBMC is applied for a block after normal MC process. To reduce the computational complexity, BIO is not applied during the OBMC process. This means that BIO is only 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.
In 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.
In the JEM, CABAC contains the following three major changes compared to the design in HEVC:
Modified context modeling for transform coefficients
Multi-hypothesis probability estimation with context-dependent updating speed
Adaptive initialization for context models
In HEVC, transform coefficients of a coding block are coded using non-overlapped coefficient groups (CGs), and each CG contains the coefficients of a 4×4 block of a coding block. The CGs inside a coding block, and the transform coefficients within a CG, are coded according to pre-defined scan orders. The coding of transform coefficient levels of a CG with at least one non-zero transform coefficient may be separated into multiple scan passes. In the first pass, the first bin (denoted by bin0, also referred as significant_coeff_flag, which indicates the magnitude of the coefficient is larger than 0) is coded. Next, two scan passes for context coding the second/third bins (denoted by bin1 and bin2, respectively, also referred as coeff_abs_greater1_flag and coeff_abs_greater2_flag) may be applied. Finally, two more scan passes for coding the sign information and the remaining values (also referred as coeff_abs_level_remaining) of coefficient levels are invoked, if necessary. Only bins in the first three scan passes are coded in a regular mode and those bins are termed regular bins in the following descriptions.
In the JEM, the context modeling for regular bins is changed. When coding bin i in the i-th scan pass (i being 0, 1, 2), the context index is dependent on the values of the i-th bins of previously coded coefficients in the neighbourhood covered by a local template. More specifically, the context index is determined based on the sum of the i-th bins of neighbouring coefficients. As depicted in
Instead of using fixed tables for context model initialization in HEVC, the initial probability states of context models for inter-coded slices can be initialized by copying states from previously coded pictures. More specifically, after coding a centrally-located CTU of each picture, the probability states of all context models are stored for potential use as the initial states of the corresponding context models on later pictures. In the JEM, the set of initial states for each inter-coded slice is copied from the stored states of a previously coded picture that has the same slice type and the same slice-level QP as the current slice. This lacks loss robustness, but is used in the current JEM scheme for coding efficiency experiment purposes.
Extended LAMVR was proposed in JVET-J0024, wherein supported motion vector resolutions range from ¼-pel to 4-pel (¼-pel, ½-pel, 1-pel, 2-pel and 4-pel). Information about the motion vector resolution is signaled at the CU level when MVD information is signaled.
Depending on the resolution of CU, both motion vector (MV) and motion vector predictor (MVP) of the CU are adjusted. If applied motion vector resolution is denoted as R (R could be ¼, ½, 1, 2, 4), MV (MVx, MVy) and MVP (MVPx, MVPy) are represented as follows:
(MVx, MVy)=(Round(MVx/(R*4))*(R*4), Round(MVy/(R*4))*(R*4)) (17)
(MVPx, MVPy)=(Round(MVPx/(R*4))*(R*4), Round(MVPy/(R*4))*(R*4)) (18)
Since the motion vector predictor and MV are both adjusted by an adaptive resolution, MVD (MVDx, MVDy) is also aligned to the resolution and, is signaled according to the resolution as follows:
(MVDx, MVDy)=((MVx−MVPx)/(R*4), (MVy−MVPy)/R*4)) (19)
In this proposal, motion vector resolution index (MVR index) indicates MVP index as well as the motion vector resolution. As result, the proposed method has no MVP index signaling. Below table shows what each value of MVR index represents.
In case of bi-prediction, AMVR has 3 modes for every resolution. AMVR Bi-Index indicates whether MVDx, MVDy of each reference list (list 0 or list 1) are signaled or not. AMVR Bi-Index in this proposal is defined as below table.
In LAMVR related methods, the allowable MVD resolutions are restricted to be integral multiple of ¼ pel precision, which is not necessary. Generalized MVD resolutions may be helpful.
On the other hand, in LAMVR related methods, one index is signaled to indicate the selected MVD resolution, which is applied to both reference lists in bi-prediction case. This maybe inefficient because a coarse MVD resolution in one reference list plus a fine MVD resolution in the other reference list may be a better tradeoff in many cases.
Meanwhile, if a MVD precision is selected, the MVP is also rounded to the same precision even if MVP has a higher precision, this maybe inefficient.
To tackle the problems, we propose generalized MVD resolutions, and separate MVD resolution control for the two reference lists in bi-prediction case.
The example solutions below should be considered as examples to explain general concepts. These solutions should not be interpreted in a narrow way. Furthermore, these solutions can be combined in any manner to produce bitstream representations, and use bitstreams to produce decoded video.
Denote prec0 and prec1 as the MVD precision (or resolution) of reference list 0 and reference list 1 respectively. When prec1 is equal to N, it means the MVD in reference list i is with N pel precision. Denote MRSet0 and MRSet1 as the candidate MVD resolution set of reference list 0 and reference list 1 respectively.
The method 2500 includes determining (2502) a coding mode of a current block, wherein the coding mode of the current block is an affine mode. The method 2500 includes determining (2504), for motion information of the current block, a motion precision from a motion precision set comprising multiple motion precisions; wherein the motion precision set is based on the coding mode. The method 2500 includes performing (2506) a conversion between the current block and a bitstream using the determined mode and the determined motion precision.
In addition to the above described method, the method 2500 may further includes some of the following features.
Example 1: A method of video bitstream processing, comprising: determining, based on coding information of a current block, a motion precision set; and performing, based on the motion precision set, a conversion between a video block and a coded representation of the video block; wherein the conversion corresponds to a reconstruction of the current block.
Example 2: The method of Example 1, wherein the motion precision set corresponds to a precision set of motion vector difference (MVD).
Example 3: The method of Example 1, wherein motion precision set corresponds to a precision set of motion vector predictors (MVPs).
Example 4: The method of Example 1, wherein motion precision set corresponds to a precision set of motion vectors (MVs).
Example 5: The method of Example 1, wherein the coding information includes a quantization level of the current block.
Example 6: The method of Example 5, wherein a set of coarser MVD precision values is selected for a larger quantization level.
Example 7: The method of Example 5, wherein a set of finer MVD precision values is selected for a smaller quantization level.
Example 8: The method of Example 1, wherein the coding information includes a coding mode of the current block.
Example 9: The method of Example 8, wherein the coding mode comprises an affine mode.
Example 10: The method of Example 9, wherein the motion precision set for affine coded blocks are different from a non-affine mode coded block.
Example 11: The method of Example 8, wherein the coding mode comprises intra-block copy (IBC) mode.
Example 12: The method of Example 11, the motion precision set for IBC coded blocks are different from a non-IBC mode coded block.
Example 13: A method of video bitstream processing, comprising: determining, based on a selected motion precision set and a signaled motion vector difference (MVD) precision index, a MVD precision of a current block from a motion precision set; and performing, based on the MVD precision, a conversion between a video block and a coded representation of the video block using a MVD; and wherein the MVD represents a difference between a predicted motion vector and an actual motion vector used during motion compensation processing.
Example 14: A video decoding apparatus comprising a processor configured to implement a method recited in one or more of Examples 1 to 13.
Example 15: A video encoding apparatus comprising a processor configured to implement a method recited in one or more of Examples 1 to 13.
Example 16: A computer program product having computer code stored thereon, the code, when executed by a processor, causes the processor to implement a method recited in one or more of Examples 1 to 13.
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.
The disclosed and other solutions, examples, embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a 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 them. The term “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 propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
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 document 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 non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
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/CN2018/091792 | Jun 2018 | WO | international |
This application is a continuation of U.S. application Ser. No. 16/940,959 filed on Jul. 28, 2020, which is a continuation of International Application No. PCT/IB2019/055135 filed on Jun. 19, 2019 which claims the priority to and benefit of International Patent Application No. PCT/CN2018/091792, filed on Jun. 19, 2018. The aforementioned applications are incorporated by reference as part of the disclosure of this application.
Number | Name | Date | Kind |
---|---|---|---|
5761343 | Haruma et al. | Jun 1998 | A |
8891608 | Lin et al. | Nov 2014 | B2 |
9930358 | Kim et al. | Mar 2018 | B2 |
10306240 | Xiu et al. | May 2019 | B2 |
10448010 | Chen et al. | Oct 2019 | B2 |
10455231 | Xu et al. | Oct 2019 | B2 |
10523964 | Chuang et al. | Dec 2019 | B2 |
10560712 | Zou et al. | Feb 2020 | B2 |
10609384 | Chen et al. | Mar 2020 | B2 |
10757417 | Zhang et al. | Aug 2020 | B2 |
10778999 | Li et al. | Sep 2020 | B2 |
10841609 | Liu | Nov 2020 | B1 |
10880547 | Xu et al. | Dec 2020 | B2 |
10979732 | Chen et al. | Apr 2021 | B2 |
11109055 | Liu et al. | Aug 2021 | B2 |
11245921 | Robert | Feb 2022 | B2 |
11265573 | Liu | Mar 2022 | B2 |
11330289 | Liu et al. | May 2022 | B2 |
11431965 | Liu | Aug 2022 | B2 |
11477458 | Liu et al. | Oct 2022 | B2 |
11653020 | Liu et al. | May 2023 | B2 |
20070025442 | Okada et al. | Feb 2007 | A1 |
20090092189 | Tsuchiya et al. | Apr 2009 | A1 |
20090168868 | Jahanghir | Jul 2009 | A1 |
20110176611 | Huang et al. | Jul 2011 | A1 |
20120093226 | Chien et al. | Apr 2012 | A1 |
20120300839 | Sze et al. | Nov 2012 | A1 |
20130177084 | Wang et al. | Jul 2013 | A1 |
20130287116 | Helle et al. | Oct 2013 | A1 |
20150124882 | Yu et al. | May 2015 | A1 |
20150195562 | Li et al. | Jul 2015 | A1 |
20150264348 | Zou et al. | Sep 2015 | A1 |
20150373358 | Pang et al. | Dec 2015 | A1 |
20160100189 | Pang et al. | Apr 2016 | A1 |
20160323600 | Ma | Nov 2016 | A1 |
20160337649 | Chuang et al. | Nov 2016 | A1 |
20160337662 | Pang et al. | Nov 2016 | A1 |
20160353110 | Zhang et al. | Dec 2016 | A1 |
20170099495 | Rapaka et al. | Apr 2017 | A1 |
20170332095 | Zou et al. | Nov 2017 | A1 |
20170347116 | Lin et al. | Nov 2017 | A1 |
20180070102 | Zhang et al. | Mar 2018 | A1 |
20180091816 | Chien et al. | Mar 2018 | A1 |
20180098063 | Chen et al. | Apr 2018 | A1 |
20180098089 | Chen | Apr 2018 | A1 |
20180131940 | Misra et al. | May 2018 | A1 |
20180160134 | Zhang et al. | Jun 2018 | A1 |
20180192053 | Zhou | Jul 2018 | A1 |
20180324464 | Zhang et al. | Jul 2018 | A1 |
20180359483 | Chen et al. | Dec 2018 | A1 |
20180359485 | Liu et al. | Dec 2018 | A1 |
20190045193 | Socek et al. | Feb 2019 | A1 |
20190045214 | Ikai et al. | Feb 2019 | A1 |
20190058896 | Huang | Feb 2019 | A1 |
20190075293 | Lim et al. | Mar 2019 | A1 |
20190082191 | Chuang et al. | Mar 2019 | A1 |
20190089960 | Chen et al. | Mar 2019 | A1 |
20190089974 | Lee | Mar 2019 | A1 |
20190110076 | Lim et al. | Apr 2019 | A1 |
20190191167 | Drugeon et al. | Jun 2019 | A1 |
20190215534 | Kondo | Jul 2019 | A1 |
20190222865 | Zhang et al. | Jul 2019 | A1 |
20190238864 | Xiu et al. | Aug 2019 | A1 |
20190246143 | Zhang et al. | Aug 2019 | A1 |
20190349588 | Chen et al. | Nov 2019 | A1 |
20190373280 | Abe et al. | Dec 2019 | A1 |
20190387247 | Huang et al. | Dec 2019 | A1 |
20190387250 | Boyce | Dec 2019 | A1 |
20200021837 | Ikai et al. | Jan 2020 | A1 |
20200029091 | Chien et al. | Jan 2020 | A1 |
20200045310 | Chen et al. | Feb 2020 | A1 |
20200137398 | Zhao et al. | Apr 2020 | A1 |
20200145688 | Zou et al. | May 2020 | A1 |
20200177877 | Chen et al. | Jun 2020 | A1 |
20200186802 | Chuang et al. | Jun 2020 | A1 |
20200213594 | Liu et al. | Jul 2020 | A1 |
20200213612 | Liu et al. | Jul 2020 | A1 |
20200221117 | Liu | Jul 2020 | A1 |
20200259045 | Kim et al. | Aug 2020 | A1 |
20200267408 | Lee et al. | Aug 2020 | A1 |
20200275094 | Lee et al. | Aug 2020 | A1 |
20200275117 | Jeong et al. | Aug 2020 | A1 |
20200288141 | Chono | Sep 2020 | A1 |
20200304805 | Li et al. | Sep 2020 | A1 |
20200351513 | Lee et al. | Nov 2020 | A1 |
20200359029 | Liu et al. | Nov 2020 | A1 |
20200374551 | Chiang 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 |
20200396477 | Furht et al. | Dec 2020 | A1 |
20200404253 | Chen et al. | Dec 2020 | A1 |
20200404255 | Zhang et al. | Dec 2020 | A1 |
20200404260 | Zhang et al. | Dec 2020 | A1 |
20200413040 | Lim et al. | Dec 2020 | A1 |
20200413048 | Zhang et al. | Dec 2020 | A1 |
20200413078 | Li et al. | Dec 2020 | A1 |
20210092366 | Liu et al. | Mar 2021 | A1 |
20210127112 | Choi et al. | Apr 2021 | A1 |
20210136390 | Chuang et al. | May 2021 | A1 |
20210195200 | Chen et al. | Jun 2021 | A1 |
20210211707 | Liu et al. | Jul 2021 | A1 |
20210266588 | Liu et al. | Aug 2021 | A1 |
20210289225 | Liu | Sep 2021 | A1 |
20210314596 | Wang et al. | Oct 2021 | A1 |
20210314623 | Chang et al. | Oct 2021 | A1 |
20210360256 | Liu et al. | Nov 2021 | A1 |
20210360279 | Liu et al. | Nov 2021 | A1 |
20210368198 | Zhang et al. | Nov 2021 | A1 |
20220150505 | Luo et al. | May 2022 | A1 |
20220248048 | Zeng | Aug 2022 | A1 |
20220264144 | Liu et al. | Aug 2022 | A1 |
Number | Date | Country |
---|---|---|
1550110 | Nov 2004 | CN |
102291581 | Dec 2011 | CN |
102783149 | Nov 2012 | CN |
103561263 | Feb 2014 | CN |
103621099 | Mar 2014 | CN |
103797799 | May 2014 | CN |
104221374 | Dec 2014 | CN |
104303506 | Jan 2015 | CN |
104335586 | Feb 2015 | CN |
104363451 | Feb 2015 | CN |
104521237 | Apr 2015 | CN |
104620576 | May 2015 | CN |
104662906 | May 2015 | CN |
104768016 | Jul 2015 | CN |
105163116 | Dec 2015 | CN |
105556964 | May 2016 | CN |
105874789 | Aug 2016 | CN |
105900420 | Aug 2016 | CN |
106165419 | Nov 2016 | CN |
106303543 | Jan 2017 | CN |
106471806 | Mar 2017 | CN |
103733625 | Apr 2017 | CN |
106797229 | May 2017 | CN |
106797476 | May 2017 | CN |
107113424 | Aug 2017 | CN |
107113442 | Aug 2017 | CN |
107257480 | Oct 2017 | CN |
107431820 | Dec 2017 | CN |
107979756 | May 2018 | CN |
108235007 | Jun 2018 | CN |
108353176 | Jul 2018 | CN |
108432250 | Aug 2018 | CN |
108781284 | Nov 2018 | CN |
107710761 | Dec 2018 | CN |
109417631 | Mar 2019 | CN |
1469682 | Oct 2004 | EP |
3203743 | Aug 2017 | EP |
3291557 | Mar 2018 | EP |
2539212 | Dec 2016 | GB |
2012060208 | Mar 2012 | JP |
2018524918 | Aug 2018 | JP |
2021526340 | Sep 2021 | JP |
201739252 | Nov 2017 | TW |
201818719 | May 2018 | TW |
2007003340 | Jan 2007 | WO |
2013168407 | Nov 2013 | WO |
2015131388 | Sep 2015 | WO |
2017052000 | Mar 2017 | WO |
2017082443 | May 2017 | WO |
2017156705 | Sep 2017 | WO |
2017194773 | Nov 2017 | WO |
2018002021 | Jan 2018 | WO |
2018064524 | Apr 2018 | WO |
2018065296 | Apr 2018 | WO |
2018067672 | Apr 2018 | WO |
2018095313 | May 2018 | WO |
2018117546 | Jun 2018 | WO |
2018175720 | Sep 2018 | WO |
2019235896 | Dec 2019 | WO |
2020009446 | Jan 2020 | WO |
2020047132 | Mar 2020 | WO |
2020131659 | Jun 2020 | WO |
2020132272 | Jun 2020 | WO |
Entry |
---|
Li et al. “Adaptive Motion Vector Resolution for Screen Content,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG 16 WP 3 and ISO IEC JTC 1/SC 29/WG 11, 19th Meeting, Strasbourg, FR, Oct. 17-24, 2014, document JCTVC-S0085, 2014. |
Non-Final Office Action from U.S. Appl. No. 17/204,448 dated Mar. 1, 2022. |
Notice of Allowance from U.S. Appl. No. 17/229,064 dated Mar. 16, 2022. |
Corrected Notice of Allowability from U.S. Appl. No. 16/940,959 dated Feb. 25, 2022. |
Certified Foreign Priority: PCT/IB2019/055135. |
Non-Final Office Action from U.S. Appl. No. 16/940,959 dated Sep. 24, 2020. |
Notice of Allowance from U.S. Appl. No. 16/940,959 dated Jun. 23, 2021. |
Akula et al. “Description of SDR, HDR and 360° video coding technology proposal considering mobile application scenario by Samsung, Huawei, GoPro, and HiSilicon” (JVET)of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 1110th Meeting: San Diego, US, (JVET-J0024), (Apr. 2018). |
An et al. “Progressive MV Resolution” (JCT-VC) of ITU-T SG16 WP3 and ISO/IEC JTC1/SC29/WG11, 6th Meeting: Torino, IT, (JCTVC-F125), (Jul. 2011). |
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. |
Chen et al. “CE4: Symmetrical Mode for Bi-Prediction (Test 3.2)” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting: Ljubljana, SI, Jul. 10-18, 2018, Document JVET-K0188, Jul. 18, 2018. |
“Chen, et al. ““CE4: Symmetrical MVD mode (Test 4.4.3)”” (JVET)of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 1113th Meeting: Marrakech, MA, (JVET-M0481), (Jan. 2019).” |
Han et al. “CE4.1.3: Affine Motion Compensation Prediction” (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting: Ljubljana, SI, (JVET-K0337), (Jul. 2018). |
He et al. “CE4-related: Adaptive precision for affine MVD coding” (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting: Macao, CN, (JVET-L0259), (Oct. 2018). |
Huang et al. “Control-Point Representation and Differential Coding Affine-Motion Compensation,” IEEE Transactions on Circuits and Systems for Video Technology, Oct. 2013, 23(10):1651-1660. |
Lai et al. “CE4.3.4: Removal of AMVR flag constraint” (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting: Ljubljana, SI, (JVET-K0247), (Jul. 2018). |
Li et al. “An Efficient Four-Parameter Affine Motion Model For Video Coding” IEEE Transactions On Circuits And Systems For Video Technology, (2018), vol. 28, No. 8, pp. 1934-1948. |
Liu et al. “CE4-related: Adaptive Motion Vector Resolution for Affine InterMode” (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting: Macao, CN, (JVET-L0332), (Oct. 2018). (is there a version 2 from ISR). |
Liu et al. “CE2: Adaptive Motion Vector Resolution for Affine Inter Mode (Test 2.1.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 No. JVET-M0246. |
“Luo et al. ““CE2-related: Symmetric MVD for Affine Bi-prediction Coding”” 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-M0467, Jan. 2019.” |
Luo et al. “CE4-related: Simplified Symmetric MVD based on CE4.4.3,” 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-M0444, Jan. 18, 2019. |
Zhang et al. “Adaptive Motion Vector Resolution Rounding Align,” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 12th Meeting: Macao, Oct. 2018, Document No. JVET-L0377. |
Zhu et al. “Simplified HMVP” 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-M0473, Jan. 2019. |
Specification of U.S. Appl. No. 62/724,500 supporting WO2020/047132 (2018). |
International Search Report and Written Opinion from PCT/IB2019/057892 dated Feb. 25, 2020 (21 pages). |
International Search Report and Written Opinion from PCT/IB2019/057895 dated Jan. 2, 2020 (18 pages). |
International Search Report and Written Opinion from PCT/IB2019/057897 dated Jan. 2, 2020 (21 pages). |
International Search Report and Written Opinion from PCT/CN2020/074122 dated Apr. 1, 2020(10 pages). |
International Search Report and Written Opinion from PCT/CN2020/074123 dated Apr. 30, 2020(9 pages). |
International Search Report and Written Opinion from PCT/CN2020/074135 dated Apr. 22, 2020(10 pages). |
International Search Report and Written Opinion from International Patent Application No. PCT/CN2020/081575 dated Jun. 22, 2020(10 pages). |
International Search Report and Written Opinion from PCT/CN2020/081580 dated Jun. 22, 2020(11 pages). |
Non-Final Office Action from U.S. Appl. No. 16/814,840 dated Sep. 29, 2020. |
Notice of Allowance from U.S. Appl. No. 16/814,832 dated Oct. 28, 2020. |
Final Office Action from U.S. Appl. No. 16/814,840 dated Jan. 21, 2021. |
Non-Final Office Action from U.S. Appl. No. 16/814,832 dated Apr. 15, 2021. |
Non-Final Office Action from U.S. Appl. No. 17/229,064 dated Jun. 15, 2021. |
Alshin A et al. “Description of SDR, HDR and 360 degree video coding technology proposal by considering mobile application sceniario by Samsung, Huawei, GoPro, and HiSilicon,” 10, JVET Meeting; Apr. 10-20, 2018; San Diego, the Joint Video Exploration Team of ISO/IEC JTC1/SC29/WG11 and ITU-T SG.16; URL: http://phenix.int-evry.fr/jvet/ . . . , No. JVET-J0024-v2; Apr. 14, 2018. |
Alshin A et al. “Description of SDR, HDR and 360 degree video coding technology proposal by Samsung, Huawei, GoPro, and HiSilicon ‘Mobile Application Scenario’”, 10 JVET Meeting; Apr. 10-20, 2018; San Diego, the Joint Video Exploration Team of ISO/IEC JTC1/SC29/WG11 and ITU-T SG.16; URL: http://phenix.int-evry.fr/jvet/ . . . , No. JVET-J0024-v5; Apr. 14, 2018. |
Chen et al. Algorithm Description of Joint Exploration Test Model 7 (JEM 7), Joint Video Exploration Team (JVET) of ITU-T SG 16 WP3 and ISO/IEC HTC 1/SC 29/WG 11, 7th Meeting, Torino, IT, Jul. 13-21, 2017, Document JVET-G1001-v1. |
Guo et al. “Adaptive Motion Vector Resolution with Implicit Signaling,” 2010 17th IEEE International Conference on Image Processing (ICIP 2010); Sep. 26-29, 2010; Hong Kong, China, Sep. 1, 2010, pp. 2057-2060, XP055564982, Piscataway, JN, USA. |
Rosewarne C et al. “High Efficiency Video Coding (HEVC) Test Model 16 (HM16) Encoder Description Update 9”, 28, JCT-VC Meeting; Jul. 15-21, 2017; Torino, Joint Collaborative Team on Video Coding of ISO-IEC JTC1/SC29/ WG11 and ITU-T SG.16, JCTVC-AB1002, Jul. 21, 2017, Retrieved from the internet: URL:http://wftp3.itu.int/av-arch/jctvc-site/. |
Rosewarne C et al. “High Efficiency Video Coding (HEVC) Test Model 16 (HM16) Improved Encoder Description Update 7”, 25th meeting, JCT-VC Meeting; Oct. 14-21, 2016; Chengdu, CN, Joint Collaborative Team on Video Coding of ITU-T SG 16 WP3 and ISO/IEC JTC1/SC29/WG11, document JCTVC-Y1002. |
Wang et al. “Adaptive Motion Vector Resolution Prediction in Block-based Video Coding,” 2015 Visual Communications and Image Processing (VCIP), IEEE, Dec. 13, 2015, pp. 1-4, XP032894127. |
Xu et al. “Intra Block Copy in HEVC Screen Content Coding Extensions,” IEEE Journal on Emerging and Selected Topics in Circuts and Systems, IEEE, Piscataway, NJ, USA, 6(4):409-419; Dec. 1, 2016. |
“High Efficiency Video Coding,” Series H: Audiovisual Media Systems: Infrastructure of Audiovisual Services—Coding of moving video, ITU-Tand ISO/IEC, ITU-T H.265, ISO/IEC 23008-2, Feb. 2018. |
JEM-7.0:—https://jvet.hhi.fraunhofer.de/svn/svn_HMJEMSoftware/tags/ HM-16.6-38JEM-7.0 (Accessed on Apr. 21, 2020). |
International Search Report and Written Opinion from PCT/IB2019/055131 dated Nov. 25, 2019, (18 pages). |
International Search Report and Written Opinion from PCT/IB2019/055132 dated Nov. 25, 2019, (19 pages). |
International Search Report and Written Opinion from PCT/IB2019/055134 dated Nov. 20, 2019, (18 pages). |
International Search Report and Written Opinion from PCT/IB2019/055135 dated Nov. 20, 2019, (18 pages). |
International Search Report and Written Opinion from PCT/IB2019/055141 dated Nov. 25, 2019, (19 pages). |
Chen et al. “EE4: Enhanced Motion Vector Difference Coding,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 5th Meeting: Geneva, CH, Jan. 12-20, 2017, document JVET-E0076, 2017. |
Chen et al. “Description of SDR, HDR and 360° Video Coding Technology Proposal by Qualcomm and Technicolor—Low and High Complexity Versions,” Joint Video Exploration Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11 10th Meeting: San Diego, US, Apr. 10-20, 2018, document JVET-J0021, 2018. |
Extended European Search Report from European Patent Application No. 20749576.3 dated Jul. 11, 2022 (11 pages). |
Final Office Action from U.S. Appl. No. 17/229,064 dated Oct. 29, 2021. |
English translation of WO2020/009446 A1. |
Non-Final Office Action from U.S. Appl. No. 17/326,616 dated Nov. 23, 2022. |
Final Office Action from U.S. Appl. No. 17/204,448 dated Aug. 15, 2022. |
Yang et al. “Non-CE4: Unified Context Model of AMVR and Affine AMVR,” 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-N0434, 2019. |
An et al. “Progressive MV Resolution,” Joint Collaborative Team on Video Coding (JCT-VC) of ITU-T SG16 WP3 and ISO/IEC JTC1/SC29/WG116th Meeting: Torino, IT, 14-22, Jul. 2011, document JCTVC-F125. 2011. |
Bross et al. “Versatile Video Coding (Draft 2),” Joint Video Experts Team (JVET) of ITU-T SG 16 WP 3 and ISO/IEC JTC 1/SC 29/WG 11, 11th Meeting, Ljubljana, SI, Jul. 10-18, 2018, document JVET-K1001, 2018. |
Non-Final Office Action from U.S. Appl. No. 17/386,346 dated Aug. 29, 2023. |
Non-Final Office Action from U.S. Appl. No. 17/729,284 dated Aug. 31, 2023. |
Final Office Action from U.S. Appl. No. 17/386,346 dated Jan. 25, 2024. |
Number | Date | Country | |
---|---|---|---|
20220021885 A1 | Jan 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16940959 | Jul 2020 | US |
Child | 17490806 | US | |
Parent | PCT/IB2019/055135 | Jun 2019 | WO |
Child | 16940959 | US |