Patent Publication Number: US-2023135007-A1

Title: Virtual prediction buffer for intra block copy in video coding

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation application of U.S. application Ser. No. 17/569,390 filed on Jan. 5, 2022, which is a continuation of International Application No. PCT/CN2020/099702 filed on Jul. 1, 2020, which claims the priority to and benefits of International Patent Application No. PCT/CN2019/094957 filed on Jul. 6, 2019 and International Patent Application No. PCT/CN2019/095297 filed on Jul. 9, 2019. All the aforementioned patent applications are hereby incorporated by reference in their entireties. 
    
    
     TECHNICAL FIELD 
     The present disclosure relates to video coding and decoding techniques, devices and systems. 
     BACKGROUND 
     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. 
     SUMMARY 
     The present disclosure describes various embodiments for buffer management and block vector coding for intra block copy mode for decoding or encoding video or images. 
     In one example aspect, a method of visual media processing is disclosed. The method includes determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the current video block, a block vector (BVx, BVy), wherein validity of the block vector (BVx, BVy) is independent of (1) a location (P, Q) of a sample block and/or (2) whether a sample at the location (P, Q) is reconstructed, and/or (3) a location of the current video block, wherein, the block vector (BVx, BVy) represents a pixel displacement between the current video block and the sample block; and performing, using the block vector, the conversion in an intra block copy mode which is based on a reconstructed block located in same video region with the current video block comprising reference samples used for deriving a prediction block of the current video block, wherein, during the conversion, a prediction sample with a location (A, B) from reference samples in a buffer is determined at least according to a size of the buffer and/or the block vector (BVx, BVy). 
     In another example aspect, another method of visual media processing is disclosed. The method includes determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, whether a block vector (BVx, BVy) corresponding to the current video block is valid according to a rule, wherein the block vector (BVx, BVy) represents a pixel displacement between the current video block and a sample block; and performing, using the block vector, the conversion based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, wherein the rule specifies that the block vector (BVx, BVy) is valid in case that (1) one or more samples from the sample block are outside the current picture and/or (2) one or more samples from the sample block are outside at least one coding tree unit (CTU) associated with the current video block, and/or (3) one or more samples from the sample block fail to be reconstructed. 
     In yet another example aspect, another method of visual media processing is disclosed. The method includes performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, wherein, the conversion is based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, and wherein a virtual buffer of a defined size is used for tracking availability of the reference samples for deriving the prediction block. 
     In yet another example aspect, another method of visual media processing is disclosed. The method includes maintaining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, a buffer comprising reference samples from the current picture for a derivation of a prediction block of the current video block, wherein one or more reference samples in the buffer that are marked unavailable for the derivation have values outside of a pixel value range. 
     In another example aspect, another method of video processing is disclosed. The method includes performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data using a buffer comprising reference samples from the current picture for derivation of a prediction block of the current video block, wherein the conversion is based according to rule which specifies that, for the bitstream representation to conform the rule, a reference sample in the buffer is to satisfy a bitstream conformance constraint. 
     In yet another example aspect, a video encoder or decoder apparatus comprising a processor configured to implement an above described method is disclosed. 
     In another example aspect, a computer readable program medium is disclosed. The medium stores code that embodies processor executable instructions for implementing one of the disclosed methods. 
     These, and other, aspects are described in greater detail in the present disclosure. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIG.  1    shows an example of a current picture referencing or an intra block copy video or image coding technique. 
         FIG.  2    shows an example of dynamic reference area. 
         FIG.  3    shows an example of coding of a block starting from (x,y). 
         FIG.  4    shows examples of a possible alternative way to choose the previous coded 64×64 blocks. 
         FIG.  5    shows an example of a possible alternative way to change the coding/decoding order of 64×64 blocks. 
         FIG.  6    is a flowchart of an example method of video or image processing. 
         FIG.  7    is a block diagram of a hardware platform for video or image coding or decoding. 
         FIG.  8    shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from top to bottom, left to right. 
         FIG.  9    shows another possible alternative way to choose the previous coded 64×64 blocks. 
         FIG.  10    shows an example flowchart for a decoding process with reshaping. 
         FIG.  11    shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from left to right, top to bottom. 
         FIG.  12    is an illustration of intra block copy (IBC) reference buffer status, where a block denotes a 64×64 coding tree unit (CTU). 
         FIG.  13    shows one arrangement of a reference area for IBC. 
         FIG.  14    shows another arrangement of a reference area for IBC. 
         FIG.  15    shows another arrangement of a reference area for IBC when the current virtual pipeline data unit (VPDU) is to the right side of the picture boundary. 
         FIG.  16    shows an example of the status of virtual buffer when VPDUs in a CTU row are decoded sequentially. 
         FIG.  17    is a block diagram of an example video processing system in which disclosed embodiments may be implemented. 
         FIG.  18    is a flowchart of an example method of visual media processing. 
         FIG.  19    is a flowchart of an example method of visual media processing. 
         FIG.  20    is a flowchart of an example method of visual media processing. 
         FIG.  21    is a flowchart of an example method of visual media processing. 
         FIG.  22    is a flowchart of an example method of visual media processing. 
     
    
    
     DETAILED DESCRIPTION 
     Section headings are used in the present disclosure for ease of understanding and do not limit scope of the disclosed embodiments in each section only to that section. The present disclosure describes various embodiments for buffer management and block vector coding for intra block copy mode for decoding or encoding video or images. 
     1. Summary 
     The present disclosure is related to video coding technologies. Specifically, it is related to intra block copy in video coding. It may be applied to the standard under development, e.g., versatile video coding (VVC). It may be also applicable to future video coding standards or video codec. 
     2. Brief Discussion 
     Video coding standards have evolved primarily through the development of the well-known International Telecommunication Union (ITU) Telecommunication Standardization Sector (ITU-T) and International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) standards. The ITU-T produced H.261 and H.263, ISO/IEC produced Moving Picture Experts Group (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 Video Coding Experts Group (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 a 50% bitrate reduction compared to HEVC. 
     2.1 Inter Prediction in HEVC/H.265 
     Each inter-predicted picture unit (PU) has motion parameters for one or two reference picture lists. Motion parameters include a motion vector (MV) and a reference picture index. Usage of one of the two reference picture lists may also be signalled using inter_pred_idc. Motion vectors may be explicitly coded as deltas relative to predictors. 
     When a coding unit (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 differences (MVD) compared to a motion vector predictor), corresponding reference picture index for each reference picture list and reference picture list usage are signalled explicitly per each PU. Such a mode is named advanced motion vector prediction (AMVP) in this disclosure. 
     When signalling 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 signalling 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. The description will start with the merge mode. 
     2.2 Current Picture Referencing 
     Current picture referencing (CPR), or once named as intra block copy (IBC) has been adopted in HEVC screen content coding extensions (HEVC-SCC) and the current VVC test model (VTM). IBC extends the concept of motion compensation from inter-frame coding to intra-frame coding. As demonstrated in  FIG.  1   , the current block is predicted by a reference block in the same picture when CPR is applied. The samples in the reference block must have been already reconstructed before the current block is coded or decoded. Although CPR is not so efficient for most camera-captured sequences, it shows significant coding gains for screen content. The reason is that there are lots of repeating patterns, such as icons and text characters in a screen content picture. CPR can remove the redundancy between these repeating patterns effectively. In HEVC-SCC, an inter-coded coding unit (CU) can apply CPR if it chooses the current picture as its reference picture. The MV is renamed as block vector (BV) in this case, and a BV always has an integer-pixel precision. To be compatible with main profile HEVC, the current picture is marked as a “long-term” reference picture in the decoded picture buffer (DPB). It should be noted that similarly, in multiple view/three-dimensional (3D) video coding standards, the inter-view reference picture is also marked as a “long-term” reference picture. 
     Following a BV to find its reference block, the prediction can be generated by copying the reference block. The residual can be generated by subtracting the reference pixels from the original signals. Then transform and quantization can be applied as in other coding modes. 
       FIG.  1    is an example illustration of CPR. 
     However, when a reference block is outside of the picture, or overlaps with the current block, or outside of the reconstructed area, or outside of the valid area restricted by some constraints, part or all pixel values are not defined. Basically, there are two solutions to handle such a problem. One is to disallow such a situation, e.g., in bitstream conformance. The other is to apply padding for those undefined pixel values. The following sub-sections describe the solutions in detail. 
     2.3 CPR in HEVC Screen Content Coding extensions 
     In the screen content coding extensions of HEVC, when a block uses current picture as reference, it should guarantee that the whole reference block is within the available reconstructed area, as indicated in the following spec text: 
     The variables offsetX and offsetY are derived as follows: 
       offsetX=(ChromaArrayType==0)?0:(myCLX[0]&amp;0x7?2:0)   (8-104)
 
       offsetY=(ChromaArrayType==0)?0:(myCLX[1]&amp;0x7?2:0)   (8-105)
 
     It is a requirement of bitstream conformance that when the reference picture is the current picture, the luma motion vector mvLX shall obey the following constraints:
         When the derivation process for z-scan order block availability of specified in clause 6.4.1 is invoked with (xCurr, yCurr) set equal to (xCb, yCb) and the neighboring luma location (xNbY, yNbY) set equal to
           (xPb+(mvLX[0]&gt;&gt;2)−offsetX, yPb+(mvLX[1]&gt;&gt;2)−offsetY) as inputs, the output shall be equal to TRUE.   
           When the derivation process for z-scan order block availability as specified in clause 6.4.1 is invoked with (xCurr, yCurr) set equal to (xCb, yCb) and the neighboring luma location (xNbY, yNbY) set equal to
           (xPb+(mvLX[0]&gt;&gt;2)+nPbW−1+offsetX, yPb+(mvLX[1]&gt;&gt;2)+nPbH−1+offsetY) as inputs, the output shall be equal to TRUE.   
           One or both of the following conditions shall be true:
           The value of (mvLX[0]&gt;&gt;2)+nPbW+xB1+offsetX is less than or equal to 0.   The value of (mvLX[1]&gt;&gt;2)+nPbH+yB1+offsetY is less than or equal to 0.   
           The following condition shall be true:       

       (xPb+(mvLX[0]&gt;&gt;2)+ nPbSw− 1+offsetX)/CtbSizeY−xCb/CtbSizeY yCb/CtbSizeY−(yPb+(mvLX[1]&gt;&gt;2)+nPbSh−1+offsetY)/CtbSizeY   (8-106)
 
     Thus, the case that the reference block overlaps with the current block or the reference block is outside of the picture will not happen. There is no need to pad the reference or prediction block. 
     2.4 Examples of CPR/IBC 
     In a VVC test model, the whole reference block should be with the current coding tree unit (CTU) and does not overlap with the current block. Thus, there is no need to pad the reference or prediction block. 
     When dual tree is enabled, the partition structure may be different from luma to chroma CTUs. Therefore, for the 4:2:0 color format, one chroma block (e.g., CU) may correspond to one collocated luma region which have been split to multiple luma CUs. 
     The chroma block could only be coded with the CPR mode when the following conditions shall be true:
         1) each of the luma CU within the collocated luma block shall be coded with CPR mode   2) each of the luma 4×4 block&#39;s BV is firstly converted to a chroma block&#39;s BV and the chroma block&#39;s BV is a valid BV.       

     If any of the two conditions is false, the chroma block shall not be coded with CPR mode. 
     It is noted that the definition of ‘valid BV’ has the following constraints:
         1) all samples within the reference block identified by a BV shall be within the restricted search range (e.g., shall be within the same CTU in current VVC design).   2) all samples within the reference block identified by a BV have been reconstructed.       

     2.5 Examples of CPR/IBC 
     In some examples, the reference area for CPR/IBC is restricted to the current CTU, which is up to 128×128. The reference area is dynamically changed to reuse memory to store reference samples for CPR/IBC so that a CPR/IBC block can have more reference candidate while the reference buffer for CPR/IBC can be kept or reduced from one CTU. 
       FIG.  2    shows a method, where a block is of 64×64 and a CTU contains 4 64×64 blocks. When coding a 64×64 block, the previous 3 64×64 blocks can be used as reference. By doing so, a decoder just needs to store 4 64×64 blocks to support CPR/IBC. 
     Suppose that the current luma CU&#39;s position relative to the upper-left corner of the picture is (x, y) and block vector is (BVx, BVy). In the current design, if the BV is valid can be told by that the luma position ((x+BVx)&gt;&gt;6&lt;&lt;6+(1&lt;&lt;7), (y+BVy)&gt;&gt;6&lt;&lt;6) has not been reconstructed and ((x+BVx)&gt;&gt;6&lt;&lt;6+(1&lt;&lt;7), (y+BVy)&gt;&gt;6&lt;&lt;6) is not equal to (x&gt;&gt;6&lt;&lt;6, y&gt;&gt;6&lt;&lt;6). 
     2.6 In-Loop Reshaping (ILR) 
     The basic idea of in-loop reshaping (ILR) is to convert the original (in the first domain) signal (prediction/reconstruction signal) to a second domain (reshaped domain) 
     The in-loop luma reshaper is implemented as a pair of look-up tables (LUTs), but only one of the two LUTs needs to be signalled as the other one can be computed from the signalled LUT. Each LUT is a one-dimensional, 10-bit, 1024-entry mapping table (1D-LUT). One LUT is a forward LUT, FwdLUT, that maps input luma code values Y i  to altered values Y r : Y r =FwdLUT[Y i ]. The other LUT is an inverse LUT, InvLUT, that maps altered code values Y r  to Ŷ i :Ŷ i =InvLUT[Y r ]. (Ŷ i  represents the reconstruction values of Y i .). 
     2.6.1 Piecewise Linear (PWL) Model 
     Conceptually, piecewise linear (PWL) is implemented in the following way: 
     Let x1, x2 be two input pivot points, and y1, y2 be their corresponding output pivot points for one piece. The output value y for any input value x between x1 and x2 can be interpolated by the following equation: 
         y= (( y 2 −y 1)/( x 2 −x 1))*( x−x 1)+ y 1 
     In fixed point implementation, the equation can be rewritten as: 
         y =(( m*x+ 2 FP_PREC-1 )&gt;&gt;FP_PREC)+ c    
     where m is scalar, c is an offset, and FP_PREC is a constant value to specify the precision. 
     In some examples, the PWL model is used to precompute the 1024-entry FwdLUT and InvLUT mapping tables; but the PWL model also allows embodiments to calculate identical mapping values on-the-fly without pre-computing the LUTs. 
     2.6.2.1 Luma Reshaping 
     A method of the in-loop luma reshaping provides a lower complexity pipeline that also eliminates decoding latency for block-wise intra prediction in inter slice reconstruction. Intra prediction is performed in reshaped domain for both inter and intra slices. 
     Intra prediction is always performed in reshaped domain regardless of slice type. With such arrangement, intra prediction can start immediately after previous transform unit (TU) reconstruction is done. Such arrangement can also provide a unified process for intra mode instead of being slice dependent.  FIG.  10    shows the block diagram of the CE12-2 decoding process based on mode. 
     16-piece PWL models are tested for luma and chroma residue scaling instead of the 32-piece PWL models. 
     Inter slice reconstruction with in-loop luma reshaper (shaded blocks indicate signal in reshaped domain: luma residue; intra luma predicted; and intra luma reconstructed). 
     2.6.2.2 Luma-Dependent Chroma Residue Scaling 
     Luma-dependent chroma residue scaling is a multiplicative process implemented with fixed-point integer operation. Chroma residue scaling compensates for luma signal interaction with the chroma signal. Chroma residue scaling is applied at the TU level. More specifically, the following applies:
         For intra, the reconstructed luma is averaged.   For inter, the prediction luma is averaged.       

     The average is used to identify an index in a PWL model. The index identifies a scaling factor cScaleInv. The chroma residual is multiplied by that number. 
     It is noted that the chroma scaling factor is calculated from forward-mapped predicted luma values rather than reconstructed luma values. 
     2.6.2.3 Signalling of ILR Side Information 
     The parameters are (currently) sent in the tile group header (similar to adaptive loop filter (ALF)). These reportedly take 40-100 bits. 
     In some examples, the added syntax is highlighted in italics. 
     In 7.3.2.1 Sequence parameter set RBSP syntax 
                                    seq_parameter_set_rbsp( ) {     Descriptor                    sps _seq_parameter_set_id    ue(v)          ...                 sps _triangle_enabled_flag    u(1)           sps _ladf_enabled_flag    u(1)         if ( sps_ladf_enabled_flag ) {               sps _num_ladf_intervals_minus2    u(2)            sps _ladf_lowest_interval_qp_offset    se(v)          for( i = 0; i &lt; sps_num_ladf_intervals_minus2 + 1;              i++ ) {                sps _ladf_qp_offset [   i    ]     se(v)             sps _ladf_delta_threshold_minus1 [   i    ]     ue(v)            }                }                                 rbsp_trailing_bits( )            }                       In 7.3.3.1 General tile   group   header   syntax                               tile_group_header( ) {     Descriptor                 ...             if( num_tiles_in_tile_group_minus1 &gt; 0 ) {              offset _len_minus1    ue(v)          for( i = 0; i &lt; num_tiles_in_tile_group_minus1; i++ )                entry _point_offset_minus1 [   i    ]     u(v)         }             if ( sps _reshaper_enabled_flag  ) {                         u(1)             if (   tile _group_reshaper_model_present_flag )                 tile _group_reshaper_model ( )                           u(1)              if (   tile _group_reshaper_enable_flag &amp;&amp; (!(              qtbtt _dual_tree_intra_flag &amp;&amp; tile_group_type == I ) ) )                            u(1)            }              byte_alignment( )            }                       Add a new syntax table tile   group   reshaper model:                                 tile _group_reshaper_model ( ) {                                ue(v)                     ue(v)             _           ue(v)             for ( i = reshaper _model_min_bin_idx; i &lt; =             reshaper _model_max_bin_idx; i++ ) {                    [    i    ]       u(v)              if (   reshaper _model_bin_delta_abs_CW [    i    ]    ) &gt; 0   )                          [    i    ]       u(1)             }               }                      
In General sequence parameter set RBSP semantics, add the following semantics:
 
sps_reshaper_enabled_flag equal to 1 specifies that reshaper is used in the coded video sequence (CVS). sps_reshaper_enabled_flag equal to 0 specifies that reshaper is not used in the CVS.
 
In tile group header syntax, add the following semantics
 
tile_group_reshaper_model_present_flag equal to 1 specifies tile_group_reshaper_model( ) is present in tile group header. tile_group_reshaper_model_present_flag equal to 0 specifies tile_group_reshaper_model( ) is not present in tile group header. When tile_group_reshaper_model_present_flag is not present, it is inferred to be equal to 0.
 
tile_group_reshaper_enabled_flag equal to 1 specifies that reshaper is enabled for the current tile group. tile_group_reshaper_enabled_flag equal to 0 specifies that reshaper is not enabled for the current tile group. When tile_group_reshaper_enable_flag is not present, it is inferred to be equal to 0.
 
tile_group_reshaper_chroma_residual_scale_flag equal to 1 specifies that chroma residual scaling is enabled for the current tile group. tile_group_reshaper_chroma_residual_scale_flag equal to 0 specifies that chroma residual scaling is not enabled for the current tile group. When tile_group_reshaper_chromaresidual_scale_flag is not present, it is inferred to be equal to 0.
 
Add tile group reshaper model( ) syntax
 
reshape_model_min_bin_idx specifies the minimum bin (or piece) index to be used in the reshaper construction process. The value of reshape_model_min_bin_idx shall be in the range of 0 to MaxBinIdx, inclusive. The value of MaxBinIdx shall be equal to 15.
 
reshape_modeldeltamax_bin_idx specifies the maximum allowed bin (or piece) index MaxBinIdx minus the maximum bin index to be used in the reshaper construction process. The value of reshape_model_max_bin_idx is set equal to MaxBinIdx−reshape_model_delta_max_bin_idx.
 
reshaper_model_bin_delta_abs_cw_prec_minus1 plus 1 specifies the number of bits used for the representation of the syntax reshape_model_bin_delta_abs_CW[i].
 
reshape_model_bin_delta_abs_CW[i] specifies the absolute delta codeword value for the ith bin.
 
reshaper_model_bin_delia_sign_CW_flag[i] specifies the sign of reshape_model_bin_delta_abs_CW[i] as follows:
         If reshape_model_bin_deltasign_CW_flag[i] is equal to 0, the corresponding variable RspDeltaCW[i] is a positive value.   Otherwise (reshape_model_bin_delta_sign_CW_flag[i] is not equal to 0), the corresponding variable RspDeltaCW[i] is a negative value.       

     When reshape_model_bin_delta_sign_CW_flag[i] is not present, it is inferred to be equal to 0. 
     The variable RspDeltaCW[i]=(1 2*reshape_model_bin_deltasign_CW[i])*reshape_model_bin_delta_abs_CW[i]; 
     The variable RspCW[i] is derived as following steps: 
     The variable OrgCW is set equal to (1&lt;&lt;BitDepth Y )/(MaxBinIdx+1).
         If reshaper_model_min_bin_idx&lt;=i&lt;=reshaper_model_max_bin_idx       

       RspCW[ i]= OrgCW+RspDeltaCW[ i].            Otherwise, RspCW[i]=0.       
     The value of RspCW[i] shall be in the range of 32 to 2*OrgCW−1 if the value of BitDepthy is equal to 10. 
     The variables InputPivot[i] with i in the range of 0 to MaxBinIdx+1, inclusive are derived as follows: 
       InputPivot[ i]=i *OrgCW 
     The variable ReshapePivot[i] with i in the range of 0 to MaxBinIdx+1, inclusive, the variable ScaleCoef[i] and InvScaleCoeff[i] with i in the range of 0 to MaxBinIdx, inclusive, are derived as follows: 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 shiftY = 14 
               
               
                   
                 ReshapePivot[ 0 ] = 0; 
               
               
                   
                 for( i = 0; i &lt;= MaxBinIdx ; i++) { 
               
               
                   
                 ReshapePivot[ i + 1 ] = ReshapePivot[ i ] + RspCW[ i ] 
               
               
                   
                  ScaleCoef[ i ] = ( RspCW[ i ] * (1 &lt;&lt; shiftY) +  
               
               
                   
                  (1 &lt;&lt; (Log2(OrgCW) − 1))) &gt;&gt; 
               
               
                   
                 (Log2(OrgCW)) 
               
               
                   
                  if( RspCW[ i ] == 0 ) 
               
               
                   
                   InvScaleCoeff[ i ] = 0 
               
               
                   
                  else 
               
               
                   
                   InvScaleCoeff[ i ] = OrgCW * (1 &lt;&lt; shiftY) / RspCW[ i ] 
               
               
                   
                 } 
               
               
                   
               
            
           
         
       
     
     The variable ChromaScaleCoef[i] with i in the range of 0 to MaxBinIdx, inclusive, are derived as follows:
         ChromaResidualScaleLut[64]={16384, 16384, 16384, 16384, 16384, 16384, 16384, 8192, 8192, 8192, 8192, 5461, 5461, 5461, 5461, 4096, 4096, 4096, 4096, 3277, 3277, 3277, 3277, 2731, 2731, 2731, 2731, 2341, 2341, 2341, 2048, 2048, 2048, 1820, 1820, 1820, 1638, 1638, 1638, 1638, 1489, 1489, 1489, 1489, 1365, 1365, 1365, 1365, 1260, 1260, 1260, 1260, 1170, 1170, 1170, 1170, 1092, 1092, 1092, 1092, 1024, 1024, 1024, 1024};   shiftC=11    if (RspCW[i]==0)       

       ChromaScaleCoef[ i]= (1&lt;&lt;shiftC)          Otherwise (RspCW[i]!=0),       
       ChromaScaleCoef[ i]= ChromaResidualScaleLut[RspCW[ i]&gt;&gt; 1] 
     2.6.2.4 Usage of ILR 
     At the encoder side, each picture (or tile group) is firstly converted to the reshaped domain And all the coding process is performed in the reshaped domain. For intra prediction, the neighboring block is in the reshaped domain; for inter prediction, the reference blocks (generated from the original domain from decoded picture buffer) are firstly converted to the reshaped domain. Then the residuals are generated and coded to the bitstream. 
     After the whole picture (or tile group) finishes encoding/decoding, samples in the reshaped domain are converted to the original domain, then deblocking filter and other filters are applied. 
     Forward reshaping to the prediction signal is disabled for the following cases: 
     Current block is intra-coded. 
     Current block is coded as CPR (current picture referencing, aka intra block copy, IBC). 
     Current block is coded as combined inter-intra mode (CIIP) and the forward reshaping is disabled for the intra prediction block. 
     3. Examples of Problems Solved by Various Embodiments 
     In the current design of CPR/IBC, some problems exist.
         1) The reference area changes dynamically, which makes encoder/decoder processing complicated.   2) Invalid block vectors are easily generated and difficult to check, which complicates both encoding and decoding.   3) Irregular reference area leads to inefficient coding of block vector.   4) It is unclear how to handle CTU size smaller than 128×128.   5) In the determination process of whether a BV is valid or invalid, for chroma blocks, the decision is based on the luma sample&#39;s availability which may result in wrong decisions due to the dual tree partition structure.       

     4. Example Embodiments 
     In some embodiments, a regular buffer can be used for CPR/IBC block to get reference. 
     A function isRec(x,y) is defined to indicate if pixel (x,y) has been reconstructed and be referenced by IBC mode. When (x,y) is out of picture, of different slice/tile/brick, isRec(x,y) returns false; when (x,y) has not been reconstructed, isRec(x,y) returns false. In another example, when sample (x,y) has been reconstructed but some other conditions are satisfied, it may also be marked as unavailable, such as out of the reference area/in a different VPDU, and isRec(x,y) returns false. 
     A function isRec(c, x,y) is defined to indicate if sample (x,y) for component c is available. For example, if the sample (x, y) has not yet been reconstructed, it is marked as unavailable. In another example, when sample (x,y) has been reconstructed but some other conditions are satisfied, it may also be marked as unavailable, such as it is out of picture/in a different slice/tile/brick/in a different VPDU, out of allowed reference area. isRec(c, x,y) returns false when sample (x, y) is unavailable, otherwise, it returns true. 
     In the following discussion, the reference samples can be reconstructed samples. It is noted that ‘pixel buffer’ may response to ‘buffer of one color component’ or ‘buffer of multiple color components’. 
     Reference Buffer for CPR/IBC 
     1. It is proposed to use a M×N pixel buffer to store the luma reference samples for CPR/IBC.
         a. In one example, the buffer size is 64×64.   b. In one example, the buffer size is 128×128.   c. In one example, the buffer size is 64×128.   d. In one example, the buffer size is 128×64.   e. In one example, N equals to the height of a CTU.   f. In one example, N=nH, where H is the height of a CTU, n is a positive integer.   g. In one example, M equals to the width of a CTU.   h. In one example, M=mW, where W is the width of a CTU, m is a positive integer.   i. In one example, the buffer size is unequal to the CTU size, such as 96×128 or 128×96.   j. In one example, the buffer size is equal to the CTU size.   k. In one example, M=mW and N=H, where W and H are width and height of a CTU, m is a positive integer.   l. In one example, M=W and N=nH, where W and H are width and height of a CTU, n is a positive integer.   m. In one example, M=mW and N=nH, where W and H are width and height of a CTU, m and n are positive integers.   n. In above example, m and n may depend on CTU size.
           i. In one example, when CTU size is 128×128, m=1 and n=1.   ii. In one example, when CTU size is 64×64, m=4 and n=1.   iii. In one example, when CTU size is 32×32, m=16 and n=1.   iv. In one example, when CTU size is 16×16, m=64 and n=1.   
           o. Alternatively, the buffer size corresponds to CTU size.   p. Alternatively, the buffer size corresponds to a VPDU size.   q. M and/or N may be signalled from the encoder to the decoder, such as in video parameter set (VPS)/sequence parameter set (SPS)/picture parameter set (PPS)/picture header/slice header/tile group header.       

     2. M and/or N may be different in different profiles/levels/tiers defined in a standard. It is proposed to use another Mc×Nc pixel buffer to store the chroma reference samples for CPR/IBC.
         a. In one example, Mc=M/2 and Nc=N/2 for 4:2:0 video.   b. In one example, Mc=M and Nc=N for 4:4:4 video.   c. In one example, Mc=M and Nc=N/2 for 4:2:2 video.   d. Alternatively, Mc and Nc can be independent of M and N.   e. In one example, the chroma buffer includes two channels, corresponding to Cb and Cr.   f In one example, Mc=M and Nc=N.       

     3. It is proposed to use a M×N sample buffer to store the RGB reference samples for CPR/IBC.
         a. In one example, the buffer size is 64×64.   b. In one example, the buffer size is 128×128.   c. In one example, the buffer size is 64×128.   d. In one example, the buffer size is 128×64.   e. Alternatively, the buffer size corresponds to CTU size.   f. Alternatively, the buffer size corresponds to a VPDU size.       

     4. It is proposed that the buffer can store reconstructed pixels before loop-filtering. Loop-filtering may refer to deblocking filter, ALF, sample adaptive offset (SAO), a cross-component ALF, or any other filters.
         a. In one example, the buffer can store samples in the current CTU.   b. In one example, the buffer can store samples outside of the current CTU.   c. In one example, the buffer can store samples from any part of the current picture.   d. In one example, the buffer can store samples from other pictures. 5. It is proposed that the buffer can store reconstructed pixels after loop-filtering. Loop-filtering may refer to deblocking filter, ALF, SAO, a cross-component ALF, or any other filters.   a. In one example, the buffer can store samples in the current CTU.   b. In one example, the buffer can store samples outside of the current CTU.   c. In one example, the buffer can store samples from any part of the current picture.   d. In one example, the buffer can store samples from other pictures.       

     6. It is proposed that the buffer can store both reconstructed samples before loop-filtering and after loop-filtering. Loop-filtering may refer to deblocking filter, ALF, SAO, a cross-component ALF, or any other filters.
         a. In one example, the buffer can store both samples from the current picture and samples from other pictures, depending on the availability of those samples.   b. In one example, reference samples from other pictures are from reconstructed samples after loop-filtering.   c. In one example, reference samples from other pictures are from reconstructed samples before loop-filtering.       

     7. It is proposed that the buffer stores samples with a given bit-depth which may be different from the bit-depth for coded video data.
         a. In one example, the bit-depth for the reconstruction buffer/coded video data is larger than that for IBC reference samples stored in the buffer.   b. In one example, even when the internal bit-depth is different from the input bit-depth for a video sequence, such as (10 bits vs 8 bits), the IBC reference samples are stored to be aligned with the input bit-depth.   c. In one example, the bit-depth is identical to that of the reconstruction buffer.   d. In one example, the bit-depth is identical to that of input image/video.   e. In one example, the bit-depth is identical to a predefine number.   f. In one example, the bit-depth depends on profile of a standard.   g. In one example, the bit-depth or the bit-depth difference compared to the output bit-depth/input bit-depth/internal bit-depth may be signalled in SPS/PPS/sequence header/picture header/slice header/tile group header/tile header or other kinds of video data units.   h. The proposed methods may be applied with the proposed buffer definitions mentioned in other bullets, alternatively, they may be also applicable to existing design of IBC.   i. The bit-depth of each color component of the buffer may be different.       

     Buffer Initiation 
     8. It is proposed to initialize the buffer with a given value
         a. In one example, the buffer is initialized with a given value.
           i. In one example, the given value may depend on the input bit-depth and/or internal bit-depth.   ii. In one example, the buffer is initialized with mid-grey value, e.g., 128 for 8-bit signal or 512 for 10-bit signal.   iii. In one example, the buffer is initialized with forwardLUT(m) when ILR is used. E.g., m=1&lt;&lt;(Bitdepth−1).   
           b. Alternatively, the buffer is initialized with a value signalled in SPS/VPS/adaptation parameter set (APS)/PPS/sequence header/tile group header/picture header/tile/CTU/CU/VPDU/region.   c. In one example, the given value may be derived from samples of previously decoded pictures or slices or CTU rows or CTUs or CUs.   d. The given value may be different for different color component.       

     9. Alternatively, it is proposed to initialize the buffer with decoded pixels from previously coded blocks.
         a. In one example, the decoded pixels are those before in-loop filtering.   b. In one example, when the buffer size is a CTU, the buffer is initialized with decoded pixels of the previous decoded CTU, if available.   c. In one example, when the buffer size is of 64×64, its buffer size is initialized with decoded pixels of the previous decoded 64×64 block, if available.   d. Alternatively, furthermore, if no previously coded blocks are available, the methods in bullet 8 may be applied.       

     Reference to the Buffer 
     10. For a block to use pixels in the buffer as a reference, it can use a position (x,y), x=0,1,2, . . . ,M−1;y=0,1,2, . . . ,N−1, within the buffer to indicate where to get the reference. 
     11. Alternatively, the reference position can be denoted as 1=y*M+x, 1=0,1, . . . ,M*N−1. 
     12. Denote the upper-left position of a block related to the current CTU as (x0,y0), a block vector (BVx,BVy)=(x−x0,y−y0) may be sent to the decoder to indicate where to get the reference in the buffer. 
     13. Alternatively, a block vector (BVx,BVy) can be defined as (x−x0+Tx,y−y0+Ty) where Tx and Ty are predefined offsets. 
     14. For any pixel (x0, y0) and (BVx, BVy), its reference in the buffer can be found at (x0+BVx, y0+BVy).
         a. In one example, when (x0+BVx, y0+BVy) is outside of the buffer, it will be clipped to the boundary.   b. Alternatively, when (x0+BVx, y0+BVy) is outside of the buffer, its reference value is predefined as a given value, e.g., mid-grey.   c. Alternatively, the reference position is defined as ((x0+BVx)mod M, (y0+BVy)mod N) so that it is always within the buffer.       

     15. For any pixel (x0, y0) and (BVx, BVy), when (x0+BVx, y0+BVy) is outside of the buffer, its reference value may be derived from the values in the buffer.
         a. In one example, the value is derived from the sample ((x0+BVx)mod M, (y0+BVy)mod N) in the buffer.   b. In one example, the value is derived from the sample ((x0+BVx)mod M, clip(y0+BVy, 0, N−1)) in the buffer.   c. In one example, the value is derived from the sample (clip(x0+BVx, 0, M−1), (y0+BVy) mod N) in the buffer.   d. In one example, the value is derived from the sample (clip(x0+BVx, 0, M−1), clip(y0+BVy, 0, N−1)) in the buffer.       

     16. It may disallow a certain coordinate outside of the buffer range.
         a. In one example, for any pixel (x0, y0) relative to the upper-left corner of a CTU and block vector (BVx, BVy), it is a bitstream constraint that y0+BVy should be in the range of [0, . . . ,N−1].   b. In one example, for any pixel (x0, y0) relative to the upper-left corner of a CTU and block vector (BVx, BVy), it is a bitstream constraint that x0+BVx should be in the range of [0, . . . ,M−1].   c. In one example, for any pixel (x0, y0) relative to the upper-left corner of a CTU and block vector (BVx, BVy), it is a bitstream constraint that both y0+BVy should be in the range of [0, . . . ,N−1] and x0+BVx should be in the range of [0, . . . ,M−1].       

     17. When the signalled or derived block vector of one block points to somewhere outside the buffer, padding may be applied according to the buffer.
         a. In one example, the value of any sample outside of the buffer is defined with a predefined value.
           i. In one example, the value can be 1&lt;&lt;(Bitdepth−1), e.g., 128 for 8-bit signals and 512 for 10-bit signals.   ii. In one example, the value can be forwardLUT(m) when ILR is used. E.g., m=1&lt;&lt;(Bitdepth−1).   iii. Alternatively, indication of the predefined value may be signalled or indicated at SPS/PPS/sequence header/picture header/slice header/Tile group/Tile/CTU/CU level.   
           b. In one example, any sample outside of the buffer is defined as the value of the nearest sample in the buffer.       

     18. The methods to handle out of the buffer reference may be different horizontally and vertically or may be different according to the location of the current block (e.g., closer to picture boundary or not).
         a. In one example, when y0+BVy is outside of [0, N−1], the sample value of (x0+BVx, y0+BVy) is assigned as a predefined value.   b. In one example, when x0+BVx is outside of [0, M−1], the sample value of (x0+BVx, y0+BVy) is assigned as a predefined value.   c. Alternatively, the sample value of (x0+BVx, y0+BVy) is assigned as the sample value of ((x0+BVx)mod M, y0+BVy), which may invoke other methods to further derive the value if ((x0+BVx)mod M, y0+BVy) is still outside of the buffer.   d. Alternatively, the sample value of (x0+BVx, y0+BVy) is assigned as the sample value of (x0+BVx, (y0+BVy)mod N), which may invoke other methods to further derive the value if (x0+BVx, (y0+BVy)mod N) is still outside of the buffer.       

     Block Vector Representation 
     19. Each component of a block vector (BVx, BVy) or one of the components may be normalized to a certain range.
         a. In one example, BVx can be replaced by (BVx mod M).   b. Alternatively, BVx can be replaced by ((BVx+X)mod M)−X, where X is a predefined value.
           i. In one example, X is 64.   ii. In one example, X is M/2.   iii. In one example, X is the horizontal coordinate of a block relative to the current CTU.   
           c. In one example, BVy can be replaced by (BVy mod N).   d. Alternatively, BVy can be replaced by ((BVy+Y)mod N)−Y, where Y is a predefined value.
           i. In one example, Y is 64.   ii. In one example, Y is N/2.   iii. In one example, Y is the vertical coordinate of a block relative to the current CTU.   
               

     20. BVx and BVy may have different normalized ranges. 
     21. A block vector difference (BVDx, BVDy) can be normalized to a certain range. 
     a. In one example, BVDx can be replaced by (BVDx mod M) wherein the function mod returns the reminder.
         b. Alternatively, BVDx can be replaced by ((BVDx+X)mod M)−X, where X is a predefined value.
           i. In one example, X is 64.   ii. In one example, X is M/2.   
           c. In one example, BVy can be replaced by (BVDy mod N).   d. Alternatively, BVy can be replaced by ((BVDy+Y)mod N)−Y, where Y is a predefined value.
           i. In one example, Y is 64.   ii. In one example, Y is N/2.   
               

     22. BVDx and BVDy may have different normalized ranges. 
     Validity Check for a Block Vector 
     Denote the width and height of an IBC buffer as W buf  and H buf . For a W×H block (may be a luma block, chroma block, CU, TU, 4×4, 2×2, or other subblocks) starting from (X, Y) relative to the upper-left corner of a picture, the following may apply to tell if a block vector (BVx, BVy) is valid or not. Let W pic  and H pic  be the width and height of a picture and; W ctu  and H ctu  be the width and height of a CTU. Function floor(x) returns the largest integer no larger than x. Function isRec(x, y) returns whether sample (x, y) has been reconstructed. 
     23. Block vector (BVx, BVy) may be set as valid even if any reference position is outside of picture boundary.
         a. In one example, the block vector may be set as valid even if X+BVx&lt;0.   b. In one example, the block vector may be set as valid even if X+W+BVx&gt;W pic .   c. In one example, the block vector may be set as valid even if Y+BVy&lt;0.   d. In one example, the block vector may be set as valid even if Y+H+BVy&gt;H pic .       

     24. Block vector (BVx, BVy) may be set as valid even if any reference position is outside of the current CTU row.
         a. In one example, the block vector may be set as valid even if Y+BVy&lt;floor(Y/H ctu )*H ctu .   b. In one example, the block vector may be set as valid even if Y+H+BVy&gt;=floor(Y/H ctu )*H ctu +H ctu .       

     25. Block vector (BVx, BVy) may be set as valid even if any reference position is outside of the current and left (n−1) CTUs, where n is the number of CTUs (including or excluding the current CTU) that can be used as reference area for IBC.
         a. In one example, the block vector may be set as valid even if X+BVx&lt;floor(X/W ctu )* W ctu −(n−1)*W ctu .   b. In one example, the block vector may be set as valid even if X+W+BVx&gt;floor(X/W ctu )*W ctu *W ctu .       

     26. Block vector (BVx, BVy) may be set as valid even if a certain sample has not been reconstructed.
         a. In one example, the block vector may be set as valid even if isRec(X+BVx, Y+BVy) is false.   b. In one example, the block vector may be set as valid even if isRec(X+BVx+W−1, Y+BVy) is false.   c. In one example, the block vector may be set as valid even if isRec(X+BVx, Y+BVy+H−1) is false.   d. In one example, the block vector may be set as valid even if isRec(X+BVx+W−1, Y+BVy+H−1) is false.       

     27. Block vector (BVx, BVy) may be always set as valid when a block is not of the 1 st  CTU in a CTU row.
         a. Alternatively, the block vector may be always set as valid.       

     28. Block vector (BVx, BVy) may be always set as valid when the following 3 conditions are all satisfied: 
         X+ BVx&gt;=0; 
         Y+ BVy&gt;=floor( Y/H   ctu ); and 
       isRec( X+ BVx+ W− 1, Y+ BVy+ H− 1) true.         a. Alternatively, when the three conditions are all satisfied for a block of the 1 st  CTU in a CTU row, the block vector may be always set as valid.       
     29. When a block vector (BVx, BVy) is valid, sample copying for the block may be based on the block vector.
         a. In one example, prediction of sample (X, Y) may be from ((X+BVx)%W buf , (Y+BVy)%H buf ).       

     Buffer Update 
     30. When coding a new picture or tile, the buffer may be reset.
         a. The term “reset” may refer to the buffer being initialized.   b. The term “reset” may refer to all samples/pixels in the buffer being set to a given value (e.g., 0 or −1).       

     31. When finishing coding of a VPDU, the buffer may be updated with the reconstructed values of the VPDU. 
     32. When finishing coding of a CTU, the buffer may be updated with the reconstructed values of the CTU.
         a. In one example, when the buffer is not full, the buffer may be updated CTU by CTU sequentially.   b. In one example, when the buffer is full, the buffer area corresponding to the oldest CTU will be updated.   c. In one example, when M=mW and N=H (W and H are CTU size; M and N are the buffer size) and the previous updated area started from (kW, 0), the next starting position to update will be ((k+1)W mod M, 0).       

     33. The buffer can be reset at the beginning of each CTU row.
         a. Alternatively, the buffer may be reset at the beginning of decoding each CTU.   b. Alternatively, the buffer may be reset at the beginning of decoding one tile.   c. Alternatively, the buffer may be reset at the beginning of decoding one tile group/picture.       

     34. When finishing coding a block starting from (x,y), the buffer&#39;s corresponding area, starting from (x,y) will be updated with reconstruction from the block.
         a. In one example, (x,y) is a position relative to the upper-left corner of a CTU.       

     35. When finishing coding a block relative to the picture, the buffer&#39;s corresponding area will be updated with reconstruction from the block.
         a. In one example, the value at position (x mod M, y mod N) in the buffer may be updated with the reconstructed pixel value of position (x, y) relative to the upper-left corner of the picture.   b. In one example, the value at position (x mod M, y mod N) in the buffer may be updated with the reconstructed pixel value of position (x, y) relative to the upper-left corner of the current tile.   c. In one example, the value at position (x mod M, y mod N) in the buffer may be updated with the reconstructed pixel value of position (x, y) relative to the upper-left corner of the current CTU row.   d. In one example, the value in the buffer may be updated with the reconstructed pixel values after bit-depth alignment.       

     36. When finishing coding a block starting from (x,y), the buffer&#39;s corresponding area, starting from (xb,yb) will be updated with reconstruction from the block wherein (xb, yb) and (x, y) are two different coordinates.
         a. In one example, (x,y) is a position related to the upper-left corner of a CTU, and (xb, yb) is (x+update_x, y+update_y), wherein update_x and update_y point to an updatable position in the buffer.       

     37. For above examples, the reconstructed values of a block may indicate the reconstructed values before filters (e.g., deblocking filter) are applied.
         a. Alternatively, the reconstructed values of a block may indicate the reconstructed values after filters (e.g., deblocking filter) are applied.       

     38. When the buffer is updated from reconstructed samples, the reconstructed samples may be firstly modified before being stored, such as sample bit-depth can be changed.
         a. In one example, the buffer is updated with reconstructed sample value after bit-depth alignment to the bit-depth of the buffer.   b. In one example, the buffer value is updated according to the value {p+[1&lt;&lt;(b−1)]}1&gt;&gt;b, where p is reconstructed sample value, b is a predefined bit-shifting value.   c. In one example, the buffer value is updated according to the value clip({p+[1&lt;&lt;(b−1)]}1&gt;&gt;b, 0, (1&lt;&lt;bitdepth)−1), where p is reconstructed sample value, b is a predefined bit-shifting value, bitdepth is the buffer bit-depth.   d. In one example, the buffer value is updated according to the value {p+[1&lt;&lt;(b−1)−1]}&gt;&gt;b, where p is reconstructed sample value, b is a predefined bit-shifting value.   e. In one example, the buffer value is updated according to the value clip({p+[1&lt;&lt;(b1)−1]}&gt;&gt;b, 0, (1&lt;&lt;bitdepth)−1), where p is reconstructed sample value, b is a predefined bit-shifting value, bitdepth is the buffer bit-depth.   f. In one example, the buffer value is updated according to the value p&gt;&gt;b.   g. In one example, the buffer value is updated according to the value clip(p&gt;&gt;b, 0, (1&lt;&lt;bitdepth)−1), where bitdepth is the buffer bit-depth.   h. In the above examples, b can be reconstructed bit-depth minus input sample bit-depth.       

     39. When use the buffer samples to form prediction, a preprocessing can be applied.
         a. In one example, the prediction value is p&lt;&lt;b, where p is a sample value in the buffer, and b is a predefined value.   b. In one example, the prediction value is clip(p&lt;&lt;b, 0, 1&lt;&lt;bitdepth), where bitdepth is the bit-depth for reconstruction samples.   c. In one example, the prediction value is (p&lt;&lt;b)+(1&lt;&lt;(bitdepth−1)), where p is a sample value in the buffer, and b is a predefined value, bitdepth is the bit-depth for reconstruction samples.   d. In the above examples, b can be reconstructed bit-depth minus input sample bit-depth.       

     40. The buffer can be updated in a given order.
         a. In one example, the buffer can be updated sequentially.   b. In one example, the buffer can be updated according to the order of blocks reconstructed.       

     41. When the buffer is full, the samples in the buffer can be replaced with latest reconstructed samples.
         a. In one example, the samples can be updated in a first-in-first-out manner.   b. In one example, the oldest samples will be replaced.   c. In one example, the samples can be assigned a priority and replaced according to the priority.   d. In one example, the samples can be marked as “long-term” so that other samples will be replaced first.   e. In one example, a flag can be sent along with a block to indicate a high priority.   f. In one example, a number can be sent along with a block to indicate priority.   g. In one example, samples from a reconstructed block with a certain characteristic will be assign a higher priority so that other samples will be replace first.
           i. In one example, when the percentage of samples coded in IBC mode is larger than a threshold, all samples of the block can be assigned a high priority.   ii. In one example, when the percentage of samples coded in palette mode is larger than a threshold, all samples of the block can be assigned a high priority.   iii. In one example, when the percentage of samples coded in IBC or palette mode is larger than a threshold, all samples of the block can be assigned a high priority.   iv. In one example, when the percentage of samples coded in transform-skip mode is larger than a threshold, all samples of the block can be assigned a high priority.   v. The threshold can be different according to block-size, color component, CTU size.   vi. The threshold can be signalled in SPS/PPS/sequence header/slice header/Tile group/Tile level/a region.   
           h. In one example, that buffer is full may mean that the number of available samples in the buffer is equal or larger than a given threshold.
           i. In one example, when the number of available samples in the buffer is equal or larger than 64×64×3 luma samples, the buffer may be determined as full.   
               

     Alternative Buffer Combination 
     42. Instead of always using the previously coded three 64×64 blocks as a reference region, it is proposed to adaptively change it based on current block&#39;s (or VPDU&#39;s) location.
         a. In one example, when coding/decoding a 64×64 block, previous 3 64×64 blocks can be used as reference. Compared to  FIG.  2   , more kinds of combination of previous 64×64 blocks can be applied.  FIG.  2    shows an example of a different combination of previous 64×64 blocks.       

     43. Instead of using the z-scan order, vertical scan order may be utilized instead.
         a. In one example, when one block is split into 4 VPDUs with index 0 . . . 3 in z-scan order, the encoding/decoding order is 0, 2, 1, 3.   b. In one example, when coding/decoding a 64×64 blocks, previous 3 64×64 blocks can be used as reference. Compared to  FIG.  2   , more kind of coding/decoding orders of 64×64 blocks can be applied.  FIG.  4    shows an example of a different coding/decoding order of 64×64 blocks.   c. Alternatively, above methods may be applied only for screen content coding.   d. Alternatively, above methods may be applied only when CPR is enabled for one tile/tile group/picture.   e. Alternatively, above methods may be applied only when CPR is enabled for one CTU or one CTU row.       

     Virtual IBC Buffer 
     The following, the width and height of a VPDU is denoted as W VPDU  (e.g., 64) and H VPDU  (e.g., 64), respectively in luma samples. Alternatively, W VPDU  and/or H VPDU  may denote the width and/or height of another video unit (e.g., CTU). 
     44. A virtual buffer may be maintained to keep track of the IBC reference region status.
         a. In one example, the virtual buffer size is m W VPDU ×n H VPDU .
           i. In one example, m is equal to 3 and n is equal to 2.   ii. In one example, m and/or n may depend on the picture resolution, CTU sizes.   iii. In one example, m and/or n may be signalled or pre-defined.   
           b. In one example, the methods described in above bullets and sub-bullets may be applied to the virtual buffer.   c. In one example, a sample (x, y) relative to the upper-left corner of the picture/slice/tile/brick may be mapped to (x%(mW VDPU ), y%(nH VDPU )).       

     45. An array may be used to track the availability of each sample associated with the virtual buffer.
         a. In one example, a flag may be associated with a sample in the virtual buffer to specify if the sample in the buffer can be used as IBC reference or not.   b. In one example, each 4×4 block containing luma and chroma samples may share a flag to indicate if any samples associated with that block can be used as IBC reference or not.   c. In one example, an array corresponding to 3×2 VPDUs (e.g., each 4×4 block may share the same availability flag) maintained to track availability of IBC reference samples.   d. In one example, an array corresponding to 4×2 VPDUs (e.g., each 4×4 block may share the same availability flag) maintained to track availability of IBC reference samples.       

     46. After finishing decoding a VPDU or a video unit, certain samples associated with the virtual buffer may be marked as unavailable for IBC reference.
         a. In one example, which samples may be marked as unavailable depend on the position of the most recently decoded VPDU.   b. When one sample is marked unavailable, prediction from the sample is disallowed.
           i. Alternatively, other ways (e.g., using default values) may be further applied to derive a predictor to replace the unavailable sample.   
               

     47. The position of most recently decoded VPDU may be recorded to help to identify which samples associated with the virtual buffer may be marked as unavailable.
         a. In one example, at the beginning of decoding a VPDU, certain samples associated with the virtual buffer may be marked as unavailable according to the position of most recently decoded VPDU.
           i. In one example, denote (xPrevVPDU, yPrevVPDU) as the upper-left position relative to the upper-left corner of the picture/slice/tile/brick/other video processing unit of most recently decoded VPDU, if yPrevVPDU%(n H VPDU ) is equal to 0, certain positions (x, y) may be marked as unavailable.
               1. In one example, x may be within a range, such as [xPrevVPDU−2W VPDU +2mW VPDU )%mW VPDU , ((xPrevVPDU−2W VPDU +2mW VPDU )%mW VPDU )−1+W VPDU ].   2. In one example, y may be within a range, such as [yPrevVPDU%(n H VPDU ), (yPrevVPDU%(nH VPDU ))−1+H VPDU ].   3. In one example, x may be within a range, such as [xPrevVPDU−2W VPDU +2mW VPDU )%mW VPDU , ((xPrevVPDU−2W VPDU +2mW VPDU )%mW VPDU )−1+W VPDU ] and y may be within a range, such as [yPrevVPDU%(n H VPDU ), (yPrevVPDU%(n H VPDU ))−1+H VPDU ].   
               ii. In one example, denote (xPrevVPDU, yPrevVPDU) as the upper-left position relative to the upper-left corner of the picture/slice/tile/brick/other video processing unit of most recently decoded VPDU, if yPrevVPDU%(n H VPDU ) is not equal to 0, certain positions (x, y) may be marked as unavailable.
               1. In one example, x may be within a range, such as [xPrevVPDU−W VPDU +2mW VPDU )%mW VPDU , ((xPrevVPDU−W VPDU +2mW VPDU )%mW VPDU )−1+W VPDU ].   2. In one example, y may be within a range, such as [yPrevVPDU%(n H VPDU ), (yPrevVPDU%(n H VPDU ))−1+H VPDU ].   3. In one example, x may be within a range, such as [xPrevVPDU−W VPDU +2mW VPDU )%mW VPDU , ((xPrevVPDU−W VPDU +2mW VPDU )%mW VPDU )−1+W VPDU ] and y may be within a range, such as [yPrevVPDU%(n H VPDU ), (yPrevVPDU%(n H VPDU ))−1+H VPDU ].   
               
               

     48. When a CU contains multiple VPDUs, instead of applying IBC reference availability marking process according to VPDU, the IBC reference availability marking process may be according to the CU.
         a. In one example, at the beginning of decoding a CU containing multiple VPDUs, the IBC reference availability marking process may be applied for each VPDU before the VPDU within the CU is decoded.   b. In such a case, 128×64 and 64×128 IBC blocks may be disallowed.
           i. In one example, pred_mode_ibc_flag for 128×64 and 64×128 CUs may not be sent and may be inferred to equal to 0.   
               

     49. For a reference block or sub-block, the reference availability status of the upper-right corner may not need to be checked to tell if the block vector associated with the reference block is valid or not.
         a. In one example, only the upper-left, bottom-left and bottom-right corner of a block/sub-block will be checked to tell if the block vector is valid or not.       

     50. The IBC buffer size may depend on VPDU size (wherein the width/height is denoted by vSize) and/or CTB/CTU size (wherein the width/height is denoted by ctbSize).
         a. In one example, the height of the buffer may be equal to ctbSize.   b. In one example, the width of the buffer may depend on min(ctbSize, 64).
           i. In one example, the width of the buffer may be (128*128/vSize, min(ctbSize, 64)).   
               

     51. An IBC buffer may contain values outside of pixel range, which indicates that the position may not be available for IBC reference, e.g., not utilized for predicting other samples.
         a. A sample value may be set to a value which indicates the sample is unavailable.   b. In one example, the value may be −1.   c. In one example, the value may be any value outside of [0, 1&lt;&lt;(internal_bit_depth)−1] wherein internal_bit_depth is a positive integer value. For example, internal_bit_depth is the internal bit-depth used for encoding/decoding a sample for a color component.   d. In one example, the value may be any value outside of [0, 1&lt;&lt;(input_bit_depth)−1] wherein input_bit_depth is a positive integer value. For example, input_bit_depth is the input bit-depth used for encoding/decoding a sample for a color component.       

     52. Availability marking for samples in the IBC buffer may depend on position of the current block, size of the current block, CTU/CTB size and VPDU size. In one example, let (xCb, yCb) denotes the block&#39;s position relative to top-left of the picture; ctb Size is the size (i.e., width and/or height) of a CTU/CTB; vSize=min(ctbSize, 64); wIbcBuf and hIbcBuf are the IBC buffer width and height.
         a. In one example, if (xCb%vSize) is equal to 0 and (yCb%vSize) is equal to 0, a certain set of positions in the IBC buffer may be marked as unavailable.   b. In one example, when the current block size is smaller than the VPDU size, i.e., min(ctbSize, 64), the region marked as unavailable may be according to the VPDU size.   c. In one example, when the current block size is larger than the VPDU size, i.e., min(ctbSize, 64), the region marked as unavailable may be according to the CU size.       

     53. At the beginning of decoding a video unit (e.g., VPDU (xV, yV)) relative to the top-left position of a picture, corresponding positions in the IBC buffer may be set to a value outside of pixel range.
         a. In one example, buffer samples with position (x%wIbcBuf, y%hIbcBuf) in the buffer, with x=xV, . . . , xV+ctbSize−1 and y=yV, . . . , yV+ctb Size−1, will be set to value −1. Where wIbcBuf and hIbcBuf are the IBC buffer width and height, ctbSize is the width of a CTU/CTB.
           i. In one example, hIbcBuf may be equal to ctbSize.   
               

     54. A bitstream conformance constraint may be according to the value of a sample in the IBC buffer.
         a. In one example, if a reference block associated with a block vector in IBC buffer contains value outside of pixel range, the bitstream may be illegal.       

     55. A bitstream conformance constraint may be set according to the availability indication in the IBC buffer.
         a. In one example, if any reference sample mapped in the IBC buffer is marked as unavailable for encoding/decoding a block, the bitstream may be illegal.   b. In one example, when singletree is used, if any luma reference sample mapped in the IBC buffer for encoding/decoding a block is marked as unavailable, the bitstream may be illegal.   c. A conformance bitstream may satisfy that for an IBC coded block, the associated block vector may point to a reference block mapped in the IBC buffer and each luma reference sample located in the IBC buffer for encoding/decoding a block shall be marked as available (e.g., the values of samples are within the range of [K0, K1] wherein for example, K0 is set to 0 and K1 is set to (1&lt;&lt;BitDepth−1) wherein BitDepth is the internal bit-depth or the input bit-depth).       

     56. Bitstream conformance constraints may depend on partitioning tree types and current CU&#39;s coding treeType
         a. In one example, if dualtree is allowed in high-level (e.g., slice/picture/brick/tile) and the current video block (e.g., CU/PU/coding block (CB)/prediction block (PB)) is coded with single tree, bitstreams constraints may need to check whether all components&#39; positions mapped in the IBC buffer are marked as unavailable or not.   b. In one example, if dualtree is allowed in high-level (e.g., slice/picture/brick/tile) and the current luma video block (e.g., CU/PU/CB/PB) is coded with dual tree, bitstreams constraints may neglect chroma components&#39; positions mapped in the IBC buffer whether marked as unavailable or not.
           i. Alternatively, in such a case, bitstreams constraints may still check all components&#39; positions mapped in the IBC buffer whether marked as unavailable or not.   
           c. In one example, if single tree is used, bitstreams constraints may neglect chroma components&#39; positions mapped in the IBC buffer whether marked as unavailable or not.       

     Improvement to the Current VTM Design 
     57. The prediction for IBC can have a lower precision than the reconstruction.
         a. In one example, the prediction value is according to the value clip{{p+[1&lt;&lt;(b−1)]}&gt;&gt;b,0,(1&lt;&lt;bitdepth)−1}&lt;&lt;b, where p is reconstructed sample value, b is a predefined bit-shifting value, bitdepth is prediction sample bit-depth.   b. In one example, the prediction value is according to the value clip{{p+[1&lt;&lt;(b−1)−1]}&gt;&gt;b,0,(1&lt;&lt;bitdepth)−1}&lt;&lt;b, where p is reconstructed sample value, b is a predefined bit-shifting value.   c. In one example, the prediction value is according to the value ((p&gt;&gt;b)+(1&lt;&lt;(bitdepth−1)))&lt;&lt;b, where bitdepth is prediction sample bit-depth.   d. In one example, the prediction value is according to the value (clip((p&gt;&gt;b),0,(1&lt;&lt;(bitdepth−b)))+(1&lt;&lt;(bitdepth−1)))&lt;&lt;b, where bitdepth is prediction sample bit-depth.   e. In one example, the prediction value is clipped in different ways depending on whether ILR is applied or not.   f. In the above examples, b can be reconstructed bit-depth minus input sample bit-depth.   g. In one example, the bit-depth or the bit-depth difference compared to the output bit-depth/input bit-depth/internal bit-depth may be signalled in SPS/PPS/sequence header/picture header/slice header/Tile group header/Tile header or other kinds of video data units.       

     58. Part of the prediction of IBC can have a lower precision and the other part has the same precision as the reconstruction.
         a. In one example, the allowed reference area may contain samples with different precisions (e.g., bit-depth).   b. In one example, reference from other 64×64 blocks than the current 64×64 block being decoded is of low precision and reference from the current 64×64 block has the same precision as the reconstruction.   c. In one example, reference from other CTUs than the current CTU being decoded is of low precision and reference from the current CTU has the same precision as the reconstruction.   d. In one example, reference from a certain set of color components is of low precision and reference from the other color components has the same precision as the reconstruction.       

     59. When CTU size is M×M and reference area size is nM×nM, the reference area is the nearest available n×n CTU in a CTU row.
         a. In one example, when reference area size is 128×128 and CTU size is 64×64, the nearest available 4 CTUs in a CTU row can be used for IBC reference.   b. In one example, when reference area size is 128×128 and CTU size is 32×32, the nearest available 16 CTUs in a CTU row can be used for IBC reference.       

     60. When CTU size is M and reference area size is nM, the reference area is the nearest available n−1 CTUs in a CTU row/tile.
         a. In one example, when reference area size is 128×128 or 256×64 and CTU size is 64×64, the nearest available 3 CTUs in a CTU row can be used for IBC reference.   b. In one example, when reference area size is 128×128 or 512×32 and CTU size is 32×32, the nearest available 15 CTUs in a CTU row can be used for IBC reference.       

     61. When CTU size is M, VPDU size is kM and reference area size is nM, and the reference area is the nearest available n−k CTUs in a CTU row/tile.
         a. In one example, CTU size is 64×64, VPDU size is also 64×64, reference area size is 128×128, the nearest 3 CTUs in a CTU row can be used for IBC reference.   b. In one example, CTU size is 32×32, VPDU size is also 64×64, reference area size is 128×128, the nearest (16−4)=12 CTUs in a CTU row can be used for IBC reference.       

     62. For a w×h block with upper-left corner being (x, y) using IBC, there are constraints that keep reference block from certain area for memory reuse, wherein w and h are width and height of the current block.
         a. In one example, when CTU size is 128×128 and (x, y)=(m×64, n×64), the reference block cannot overlap with the 64×64 region starting from ((m−2)×64, n×64).   b. In one example, when CTU size is 128×128, the reference block cannot overlap with the w×h block with upper-left corner being (x−128, y).   c. In one example, when CTU size is 128×128, (x+BVx, y+BVy) cannot be within the w*h block with upper-left corner being (x−128, y), where BVx and BVy denote the block vector for the current block.   d. In one example, when CTU size is M×M and IBC buffer size is k×M×M, reference block cannot overlap with the w×h block with upper-left corner being (x−k×M, y), where BVx and BVy denote the block vector for the current block.   e. In one example, when CTU size is M×M and IBC buffer size is k×M×M, (x+BVx, y+BVy) cannot be within the w×h block with upper-left corner being (x−k×M, y), where BVx and BVy denote the block vector for the current block.       

     63. When CTU size is not M×M and reference area size is nM×nM, the reference area is the nearest available n×n−1 CTU in a CTU row.
         a. In one example, when reference area size is 128×128 and CTU size is 64×64, the nearest available 3 CTUs in a CTU row can be used for IBC reference.   b. In one example, when reference area size is 128×128 and CTU size is 32×32, the nearest available 15 CTUs in a CTU row can be used for IBC reference.       

     64. For a CU within a 64×64 block starting from (2m*64, 2n*64), i.e., an upper-left 64×64 block in a 128×128 CTU, its IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−2)*64, 2n*64), the 64×64 block starting from ((2m−1)*64, 2n*64), the 64×64 block starting from ((2m−1)*64, (2n+1)*64) and the current 64×64 block. 
     65. For a CU within a 64×64 block starting from ((2m+1)*64, (2n+1)*64), i.e., a bottom-right 64×64 block in a 128×128 CTU, its IBC prediction can be from the current 128×128 CTU. 
     66. For a CU within a 64×64 block starting from ((2m+1)*64, 2n*64), i.e., an upper-right 64×64 block in a 128×128 CTU, its IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−1)*64, 2n*64), the 64×64 block starting from ((2m−1)*64, (2n+1)*64), the 64×64 block starting from (2m*64, 2n*64) and the current 64×64 block.
         a. Alternatively, if the 64×64 block starting from (2m*64, (2n+1)*64) has been reconstructed, the IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−1)*64, 2n*64), the 64×64 block starting from (2m*64, 2n*64), the 64×64 block starting from (2m*64, (2n+1)*64) and the current 64×64 block.       

     67. For a CU within a 64×64 block starting from (2m*64, (2n+1)*64), i.e., a bottom-left 64×64 block in a 128×128 CTU, its IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−1)*64, (2n+1)*64), the 64×64 block starting from (2m*64, 2n*64); the 64×64 block starting from ((2m+1)*64, 2n*64) and the current 64×64 block.
         a. Alternatively, if the 64×64 block starting from ((2m+1)*64, 2n*64) has not been reconstructed, the IBC prediction can be from reconstructed samples in the 64×64 block starting from ((2m−1)*64, 2n*64), the 64×64 block starting from ((2m−1)*64, (2n+1)*64), the 64×64 block starting from (2m*64, 2n*64) and the current 64×64 block.       

     68. It is proposed to adjust the reference area based on which 64×64 blocks the current CU belongs to.
         a. In one example, for a CU starting from (x,y), when (y&gt;&gt;6)&amp;1==0, two or up to two previous 64×64 blocks, starting from ((x&gt;&gt;6&lt;&lt;6)−128, y&gt;&gt;6&lt;&lt;6) and ((x&gt;&gt;6&lt;&lt;6)−64, y&gt;&gt;6&lt;&lt;6) can be referenced by IBC mode.   b. In one example, for a CU starting from (x,y), when (y&gt;&gt;6)&amp;1==1, one previous 64×64 block, starting from ((x&gt;&gt;6&lt;&lt;6)−64, y&gt;&gt;6&lt;&lt;6) can be referenced by IBC mode.       

     69. For a block starting from (x,y) and with block vector (BVx, BVy), if isRec(((x+BVx)&gt;&gt;6&lt;&lt;6)+128−(((y+BVy)&gt;&gt;6)&amp;1)*64+(x%64), ((y+BVy)&gt;&gt;6&lt;&lt;6)+(y%64)) is true, the block vector is invalid.
         a. In one example, the block is a luma block.   b. In one example, the block is a chroma block in 4:4:4 format.   c. In one example, the block contains both luma and chroma components.       

     70. For a chroma block in 4:2:0 format starting from (x,y) and with block vector (BVx, BVy), if isRec(((x+BVx)&gt;&gt;5&lt;&lt;5)+64−(((y+BVy)&gt;&gt;5)&amp;1)*32+(x%32), ((y+BVy)&gt;&gt;5&lt;&lt;5)+(y%32)) is true, the block vector is invalid. 
     71. The determination of whether a BV is invalid or not for a block of component c may rely on the availability of samples of component X, instead of checking the luma sample only.
         a. For a block of component c starting from (x,y) and with block vector (BVx, BVy), if isRec(c, ((x+BVx)&gt;&gt;6&lt;&lt;6)+128−(((y+BVy)&gt;&gt;6)&amp;1)*64+(x%64), ((y+BVy)&gt;&gt;6&lt;&lt;6)+(y%64)) is true, the block vector may be treated as invalid.
           i. In one example, the block is a luma block (e.g., c is the luma component, or G component for RGB coding).   ii. In one example, the block is a chroma block in 4:4:4 format (e.g., c is the Cb or Cr component, or B/R component for RGB coding).   iii. In one example, availability of samples for both luma and chroma components may be checked, e.g., the block contains both luma and chroma components.   
           b. For a chroma block in 4:2:0 format starting from (x,y) of component c and with block vector (BVx, BVy), if isRec(c, ((x+BVx)&gt;&gt;5&lt;&lt;5)+64−(((y+BVy)&gt;&gt;5)&amp;1)*32+(x%32), ((y+BVy)&gt;&gt;5&lt;&lt;5)+(y%32)) is true, the block vector may be treated as invalid.   c. For a chroma block or sub-block starting from (x, y) of component c and with block vector (BVx, BVy), if isRec(c, x+BVx+ChromaCTU_size, y) for a chroma component is true, the block vector may be treated as invalid, where Chroma_CTU_size is the CTU size for chroma component.
           i. In one example, for 4:2:0 format, ChromaCTU_size may be 64.   ii. In one example, a chroma sub-block may be a 2×2 block in 4:2:0 format.   iii. In one example, a chroma sub-block may be a 4×4 block in 4:4:4 format.   iv. In one example, a chroma sub-block may correspond to the minimal CU size in luma component.
               1. Alternatively, a chroma sub-block may correspond to the minimal CU size for the chroma component.   
               
               

     72. For all bullets mentioned above, it is assumed that the reference buffer contains multiple M×M blocks (M=64). However, it could be extended to other cases such as the reference buffer contains multiple N×M blocks (e.g., N=128, M=64). 
     73. For all bullets mentioned above, further restrictions may be applied that the reference buffer should be within the same brick/tile/tile group/slice as the current block.
         a. In one example, if partial of the reference buffer is outside the current brick/tile/tile group/slice, the usage of IBC may be disabled. The signalling of IBC related syntax elements may be skipped.   b. Alternatively, if partial of the reference buffer is outside the current brick/tile/tile group/slice, IBC may be still enabled for one block, however, the block vector associated with one block may only point to the remaining reference buffer.       

     74. It is proposed to have K1 most recently coded VPDU, if available, in the 1 st  VPDU row of the CTU/CTB row and K2 most recently coded VPDU, if available, in the 2 nd  VPDU row of the CTU/CTB row as the reference area for IBC, excluding the current VPDU.
         a. In one example, K1 is equal to 2 and K2 is equal to 1.   b. In one example, the above methods may be applied when the CTU/CTB size is 128×128 and VPDU size is 64×64.   c. In one example, the above methods may be applied when the CTU/CTB size is 64×64 and VPDU size is 64×64 and/or 32×32.   d. In one example, the above methods may be applied when the CTU/CTB size is 32×32 and VPDU size is 32×32 or smaller.       

     75. The above methods may be applied in different stages.
         a. In one example, the modulo operation (e.g., a mod b) of block vectors (BVs) may be invoked in the availability check process of BVs to decide whether the BV is valid or not.   b. In one example, the modulo operation (e.g., a mod b) of block vectors (BVs) may be invoked to identify a reference sample&#39;s location (e.g., according to the modulo results of a current sample&#39;s location and BV) in the IBC virtual buffer or reconstructed picture buffer (e.g., before in-loop filtering process).       

     5. Embodiments 
     5.1 Embodiment #1 
     An embodiment of the buffer for IBC is described below. 
     The buffer size is 128×128. CTU size is also 128×128. For coding of the 1 st  CTU in a CTU row, the buffer is initialized with 128 (for 8-bit video signal). For coding of the k-th CTU in a CTU row, the buffer is initialized with the reconstruction before loop-filtering of the (k−1)-th CTU. 
       FIG.  3    shows an example of coding of a block starting from (x,y). 
     When coding a block starting from (x,y) related to the current CTU, a block vector (BVx, BVy)=(x−x0, y−y0) is sent to the decoder to indicate the reference block is from (x0,y0) in the IBC buffer. Suppose the width and height of the block are w and h respectively. When finishing coding of the block, a w×h area starting from (x,y) in the IBC buffer will be updated with the block&#39;s reconstruction before loop-filtering. 
     5.2 Embodiment #2 
       FIG.  4    shows examples of a possible alternative way to choose the previous coded 64×64 blocks. 
     5.3 Embodiment #3 
       FIG.  5    shows an example of a possible alternative way to change the coding/decoding order of 64×64 blocks. 
     5.4 Embodiment #4 
       FIG.  8    shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from top to bottom, left to right. 
     5.5 Embodiment #5 
       FIG.  9    shows another possible alternative way to choose the previous coded 64×64 blocks. 
     5.6 Embodiment #6 
       FIG.  11    shows another possible alternative way to choose the previous coded 64×64 blocks, when the decoding order for 64×64 blocks is from left to right, top to bottom. 
     5.7 Embodiment #7 
     Suppose that CTU size is W×W, an embodiment of IBC buffer with size mW×W and bit-depth being B, at the decoder is as below. 
     At the beginning of decoding a CTU row, initialize the buffer with value (1&lt;&lt;(B−1)) and set the starting point to update (xb, yb) to be (0,0). 
     When a CU starting from (x, y) related to a CTU upper-left corner and with size w×h is decoded, the area starting from (xb+x, yb+y) and w×h size will be updated with the reconstructed pixel values of the CU, after bit-depth aligned to B-bit. 
     After a CTU is decoded, the starting point to update (xb, yb) will be set as ((xb+W)mod mW, 0). 
     When decoding an IBC CU with block vector (BVx, BVy), for any pixel (x, y) related to a CTU upper-left corner, its prediction is extracted from the buffer at position ((x+BVx)mod mW, (y+BVy) mode W) after bit-depth alignment to the bit-depth of prediction signals. 
     In one example, B is set to 7, or 8 while the output/input bit-depth of the block may be equal to 10. 
     5.8 Embodiment #8 
     For a luma CU or joint luma/chroma CU starting from (x,y) related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(((x+BVx)&gt;&gt;6&lt;&lt;6)+128−(((y+BVy)&gt;&gt;6)&amp;1)*64+(x%64), ((y+BVy)&gt;&gt;6&lt;&lt;6)+(y%64)) is true. 
     For a chroma CU starting from (x,y) related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(((x+BVx)&gt;&gt;5&lt;&lt;5)+64−(((y+BVy)&gt;&gt;5)&amp;1)*32+(x%32), ((y+BVy)&gt;&gt;5&lt;&lt;5)+(y%32)) is true. 
     5.9 Embodiment #9 
     For a chroma block or sub-block starting from (x,y) in 4:2:0 format related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(c, (x+BVx+64, y+BVy) is true, where c is a chroma component. 
     For a chroma block or sub-block starting from (x,y) in 4:4:4 format related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(c, (x+BVx+128, y+BVy) is true, where c is a chroma component. 
     5.10 Embodiment #10 
     For a luma CU or joint luma/chroma CU starting from (x,y) related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(((x+BVx)&gt;&gt;6&lt;&lt;6)+128−(((y+BVy)&gt;&gt;6)&amp;1)*64+(x%64), ((y+BVy)&gt;&gt;6&lt;&lt;6)+(y%64)) is true. 
     For a chroma block or sub-block starting from (x,y) in 4:2:0 format related to the upper-left corner of a picture and a block vector (BVx, BVy), the block vector is invalid when isRec(c, ((x+BVx)&gt;&gt;5&lt;&lt;5)+64−(((y+BVy)&gt;&gt;5)&amp;1)*32+(x %32), ((y+BVy)&gt;&gt;5&lt;&lt;5)+(y%32)) is true, where c is a chroma component. 
     5.11 Embodiment #11 
     This embodiment is an embodiment of keeping two most coded VPDUs in the l′ VPDU row and one most coded VPDU in the r d  VPDU row of a CTU/CTB row, excluding the current VPDU. 
     When VPDU coding order is top to bottom and left to right, the reference area is illustrated as in  FIG.  13   . 
     When VPDU coding order is left to right and top to bottom and the current VPDU is not to the right side of the picture boundary, the reference area is illustrated as in  FIG.  14   . 
     When VPDU coding order is left to right and top to bottom and the current VPDU is to the right side of the picture boundary, the reference area may be illustrated as  FIG.  15   . 
     Given a luma block (x, y) with size w×h, a block vector (BVx, BVy) is valid or not can be told by checking the following condition: 
       isRec((( x+ BVx+128)&gt;&gt;6&lt;&lt;6)−(refy&amp;0x40)+( x %64), (( y+ BVy)&gt;&gt;6&lt;&lt;6)+(refy&gt;&gt;6== y&gt;&gt; 6)?( y %64):0), where refy=( y &amp;0x40)?( y+ BVy):( y+ BVy+ w− 1).
 
     If the above function returns true, the block vector (BVx, BVy) is invalid, otherwise the block vector might be valid. 
     5.12 Embodiment #12 
     If CTU size is 192×128, a virtual buffer with size 192×128 is maintained to track the reference samples for IBC. 
     A sample (x, y) relative to the upper-left corner of the picture is associated with the position (x%192, y%128) relative to the upper-left corner of the buffer. The following steps show how to mark availability of the samples associate with the virtual buffer for IBC reference. 
     A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
         1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).   2) At the beginning of decoding the 1st CU of a VPDU, positions (x, y) with x=(xPrevVPDU−2WVPDU+2mWVPDU)%(mWVPDU), . . . , ((xPrevVPDU−2WVPDU+2mWVPDU)%(mWVPDU))−1+WVPDU; and y=yPrevVPDU%(nHVPDU), . . . , (yPrevVPDU%(nHVPDU))−1+HVPDU may be marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e., the upper-left position of the CU relative to the picture.   3) After decoding a CU, positions (x, y) with x=xCU%(mWVPDU), . . . , (xCU+CU_width−1)%(mWVPDU) and y=yCU%(nHVPDU), . . . , (yCU+CU_height−1)%(nHVPDU) are marked as available.   4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xBV)%(mWVPDU), . . . , (xCU+xBV+CU_width−1)%(mWVPDU) and y=(yCU+yBV)%(nHVPDU), . . . , (yCU+yBV+CU_height−1)%(nHVPDU) is marked as unavailable, the block vector is considered as invalid.       

       FIG.  16    shows the buffer status along with the VPDU decoding status in the picture. 
     5.13 Embodiment #13 
     If CTU size is 128×128 or CTU size is greater than VPDU size (e.g., 64×64 in current design) or CTU size is greater than VPDU size (e.g., 64×64 in current design), a virtual buffer with size 192×128 is maintained to track the reference samples for IBC. In the following, when a&lt;0, (a%b) is defined as floor(a/b)*b, where floor (c) returns the largest integer no larger than c. 
     A sample (x, y) relative to the upper-left corner of the picture is associated with the position (x%192, y%128) relative to the upper-left corner of the buffer. The following steps show how to mark availability of the samples associate with the virtual buffer for IBC reference. 
     A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
         1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).   2) At the beginning of decoding the 1 st  CU of a VPDU,
           a. If yPrevVPDU%64 is equal to 0, positions (x, y) with x=(xPrevVPDU−128)%192, . . . , ((xPrevVPDU−128)%192)+63; and y=yPrevVPDU%128, . . . , (yPrevVPDU%128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e., the upper-left position of the CU relative to the picture.   b. Otherwise, positions (x, y) with x=(xPrevVPDU−64)%192, . . . , ((xPrevVPDU−64)%192)+63; and y=yPrevVPDU%128, . . . , (yPrevVPDU%128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e., the upper-left position of the CU relative to the picture.   
           3) After decoding a CU, positions (x, y) with x=xCU%192, . . . , (xCU+CU_width−1)%192 and y=yCU%128, . . . , (yCU+CU_height−1)%128 are marked as available.   4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xBV)%192, . . . , (xCU+xBV+CU_width−1)%192 and (yCU+yBV)%128, . . . , (yCU+yBV+CU_height−1)%128 is marked as unavailable, the block vector is considered as invalid.       

     If CTU size is S×S, S is not equal to 128, let Wbuf be equal to 128*128/S. A virtual buffer with size Wbuf×S is maintained to track the reference samples for IBC. The VPDU size is equal to the CTU size in such a case. 
     A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
         1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).   2) At the beginning of decoding the 1 st  CU of a VPDU, positions (x, y) with x=(xPrevVPDU−W buf *S)%S, . . . , ((xPrevVPDU−W buf *S)%S)+S−1; and y=yPrevVPDU%S, . . . , (yPrevVPDU%S)+S−1; are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e., the upper-left position of the CU relative to the picture.   3) After decoding a CU, positions (x, y) with x=xCU%(W buf ), . . . , (xCU+CU_width−1)%(W buf ) and y=yCU%S, . . . , (yCU+CU_height−1)%S are marked as available.   4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xBV)%(Wbuf), . . . , (xCU+xBV+CU_width−1)%(Wbuf) and y=(yCU+yBV)%S, . . . , (yCU+yBV+CU_height−1)%S is marked as unavailable, the block vector is considered as invalid.       

     5.14 Embodiment #14 
     If CTU size is 128×128 or CTU size is greater than VPDU size (e.g., 64×64 in current design) or CTU size is greater than VPDU size (e.g., 64×64 in current design), a virtual buffer with size 256×128 is maintained to track the reference samples for IBC. In the following, when a &lt;0, (a%b) is defined as floor(a/b)*b, where floor(c) returns the largest integer no larger than c. 
     A sample (x, y) relative to the upper-left corner of the picture is associated with the position (x%256, y%128) relative to the upper-left corner of the buffer. The following steps show how to mark availability of the samples associate with the virtual buffer for IBC reference. 
     A position (xPrevVPDU, yPrevVPDU) relative to the upper-left corner of the picture is recorded to stand for the upper-left sample of the most recently decoded VPDU.
         1) At the beginning of decoding a VPDU row, all positions of the buffer are marked as unavailable. (xPrevVPDU, yPrevVPDU) is set as (0,0).   2) At the beginning of decoding the 1 st  CU of a VPDU:
           a. If yPrevVPDU%64 is equal to 0, positions (x, y) with x=(xPrevVPDU−128)%256, . . . , ((xPrevVPDU−128)%256)+63; and y=yPrevVPDU%128, . . . , (yPrevVPDU%128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e., the upper-left position of the CU relative to the picture.   b. Otherwise, positions (x, y) with x=(xPrevVPDU−64)%256, . . . , ((xPrevVPDU−64)%256)+63; and y=yPrevVPDU%128, . . . , (yPrevVPDU%128)+63, are marked as unavailable. Then (xPrevVPDU, yPrevVPDU) is set as (xCU, yCU), i.e., the upper-left position of the CU relative to the picture.   
           3) After decoding a CU, positions (x, y) with x=xCU%256, . . . (xCU+CU_width−1)%256 and y=yCU%128, . . . , (yCU+CU_height−1)%128 are marked as available.   4) For an IBC CU with a block vector (xBV, yBV), if any position (x, y) with x=(xCU+xBV)%256, . . . , (xCU+xBV+CU_width−1)%256 and y=(yCU+yBV)%128, . . . , (yCU+yBV+CU_height−1)%128 is marked as unavailable, the block vector is considered as invalid.       

     When CTU size is not 128×128 or less than 64×64 or less than 64×64, the same process applies as in the previous embodiment, i.e., embodiment #14. 
     5.15 Embodiment #15 
     An IBC reference availability marking process is described as follows. The changes are indicated in bolded, underlined, italicized text in this disclosure. 
     7.3.7.1 General Slice Data Syntax 
       
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 slice_data( ) { 
                 
                   Descriptor 
                 
               
               
                   
               
               
                  for( i = 0; i &lt; NumBricksInCurrSlice; i++ ) { 
                   
               
               
                   CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ] 
                   
               
               
                   for( j = 0; j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++,  
                   
               
               
                 CtbAddrInBs++ ) { 
                   
               
               
                    if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) { 
                   
               
               
                     NumHmvpCand = 0  
                   
               
               
                     NumHmvpIbcCand = 0  
                   
               
               
                 ________   
                   
               
               
                 ________   
                   
               
               
                 ________   
                   
               
               
                 __________  _  _   
                   
               
               
                    _   
                   
               
               
                 ________   
                   
               
               
                 __________   
                   
               
               
                    _   
                   
               
               
                    } 
                   
               
               
                    CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ] 
                   
               
               
                    ... ... 
               
               
                   
               
               
                    _  _   
                 
                   
                 
               
               
                   
               
               
                 ___    
                   
               
               
                 ____  _   
                   
               
               
                 ______  _   
                   
               
               
                 ________  _   
                   
               
               
                 
                   
                 
               
               
                   
               
            
           
         
       
     
     
       
       
       
       
       
     
     7.3.7.5 Coding Unit Syntax 
       
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 coding_unit( x0, y0, cbWidth, cbHeight, treeType ) { 
                 
                   Descriptor 
                 
               
               
                   
               
               
                 __         
                   
               
               
                        
                   
               
               
                 _____      
                   
               
               
                 _______      
                   
               
               
                 _________      
                   
               
               
                 ___________      
                   
               
               
                           
                   
               
               
                 _________   
                   
               
               
                 ___________      
                   
               
               
                           
                   
               
               
                 ____   
                   
               
               
                 ____   
                   
               
               
                 ___   
                   
               
               
                 ___         
                   
               
               
                        
                   
               
               
                 _____      
                   
               
               
                           
                   
               
               
                 ____   
                   
               
               
                 ____   
                   
               
               
                 ___   
                   
               
               
                  if( slice_type != I | | sps_ibc_enabled_flag ) { 
                   
               
               
                   if( treeType != DUAL_TREE_CHROMA &amp;&amp;  
                   
               
               
                    !( cbWidth = = 4 &amp;&amp; cbHeight = = 4  
                   
               
               
                 &amp;&amp; !sps_ibc_enabled_flag ) )  
                   
               
               
                     cu _skip_flag[ x0 ][ y0 ] 
                 ae(v)  
               
               
                   if( cu_skip_flag[ x0 ][ y0 ] = = 0 &amp;&amp; slice type != I  
                   
               
               
                    &amp;&amp; !( cbWidth = = 4 &amp;&amp; cbHeight = = 4 ) )  
                   
               
               
                     pred _mode_flag  
                 ae(v)  
               
               
                   if( ( ( slice type = = I &amp;&amp; cu_skip_flag[ x0 ][ y0 ] = =0 ) | |  
                   
               
               
                    ( slice_type != I &amp;&amp; ( CuPredMode[ x0 ][ y0 ] != 
                   
               
               
                 MODE_INTRA | | 
                   
               
               
                    ( cbWidth = = 4 &amp;&amp; cbHeight = = 4 &amp;&amp;  
                   
               
               
                 cu_skip_flag[ x0 ][ y0 ] = = 0 ) ) ) ) &amp;&amp;  
                   
               
               
                    sps_ibc_enabled_flag &amp;&amp; ( cbWidth != 128     
                   
               
               
                 cbHeight != 128 ) )  
                   
               
               
                     pred _mode_ibc_flag  
                 ae(v)  
               
               
                  } 
                   
               
               
                  ... 
               
               
                   
               
            
           
         
       
     
     8.6.2 Derivation Process for Motion Vector Components for IBC Blocks 
     8.6.2.1 General 
     
       
       
       
       
       
       
       
       
       
     
     8.6.3 Decoding Process for IBC Blocks 
     8.6.3.1 General 
     This process is invoked when decoding a coding unit coded in IBC prediction mode. 
     Inputs to this process are:
         a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples,   a variable cbHeight specifying the height of the current coding block in luma samples,   variables numSbX and numSbY specifying the number of luma coding subblocks in horizontal and vertical direction,   the motion vectors mv[xSbIdx][ySbIdx] with xSbIdx=0 numSbX−1, and ySbIdx=0 . . . numSbY−1,   a variable cIdx specifying the colour component index of the current block.               

     For each coding subblock at subblock index (xSbIdx, ySbIdx) with xSbIdx=0 . . . numSbX−1, and ySbIdx=0 . . . numSbY−1, the following applies:
         The luma location (xSb, ySb) specifying the top-left sample of the current coding subblock relative to the top-left luma sample of the current picture is derived as follows:       

       (xSb,ySb)=(xCb+xSbIdx*sbWidth,yCb+ySbIdx*sbHeight)   (8-913)
 
     
       
       
       
       
       
       
       
       
     
     
       
      
       
       
       
       
       
       
      
         
         
           
             
               
               
               
               
             
           
         
       
    
     
      
      
      
     
     
       
       
         
         
           
             
               
               
               
               
               
               
               
             
             
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
               
             
             
               
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
             
             
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
               
               
             
           
         
       
    
     
       
      
       
       
       
       
      
     
     
       
      
       
       
       
      
     
     
       
      
       
       
       
       
       
      
     
     
       
      
       
       
       
       
       
      
     
     
       
       
       
       
       
       
       
       
       
     
     8.7.5 Picture Reconstruction Process 
     8.7.5.1 General 
     Inputs to this process are:
         a location (xCurr, vCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,   the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,   a variable cIdx specifying the colour component of the current block,   (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,   an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.       

     Output of this process are
         a reconstructed picture sample array recSamples.                               

     
       
      
       
       
       
       
       
       
      
         
         
           
             
               
               
             
           
         
       
    
     5.16 Embodiment #16 
     This is identical to the previous embodiment except for the following changes: 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 slice_data( ) { 
                 
                   Descriptor 
                 
               
               
                   
               
               
                  for( i = 0; i &lt; NumBricksInCurrSlice; i++ ) { 
                   
               
               
                   CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ] 
                   
               
               
                   for( j = 0; j &lt; NumCtusInBrick[ SliceBrick[Idx i ] ]; j++,  
                   
               
               
                 CtbAddrInBs++ ) { 
                   
               
               
                    if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) { 
                   
               
               
                     NumHmvpCand = 0  
                   
               
               
                     NumHmvpIbcCand = 0  
                   
               
               
                 ________    
                   
               
               
                 ________    
                   
               
               
                 ________    
                   
               
               
                 ___________      
                   
               
               
                 
                   
                 
                   
               
               
                 ________    
                   
               
               
                 __________    
                   
               
               
                              
                   
               
               
                    } 
                   
               
               
                    CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ] 
                   
               
               
                    ... ... 
               
               
                   
               
               
                           
                 
                   
                 
               
               
                   
               
               
                 ___    
                   
               
               
                 _____       
                   
               
               
                 ________       
                   
               
               
                 ___________       
                   
               
               
                 
                   
                 
               
               
                   
               
            
           
         
       
       
       
       
       
       
       
     
     5.17 Embodiment #17 
     The changes in some examples are indicated in bolded, underlined, text in this disclosure. 
     7.3.7 Slice Data Syntax 
     7.3.7.1 General Slice Data Syntax 
       
     
       
         
           
               
               
             
               
                   
               
               
                 slice_data( ) { 
                 
                   Descriptor 
                 
               
               
                   
               
             
            
               
                  for( i = 0; i &lt; NumBricksInCurrSlice; i++ ) { 
                   
               
               
                   CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ] 
                   
               
               
                   for( j = 0; j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++,  
                   
               
               
                 CtbAddrInBs++ ) { 
                   
               
               
                    if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) { 
                   
               
               
                     NumHmvpCand = 0  
                   
               
               
                     NumHmvpIbcCand = 0  
                   
               
               
                        
                   
               
               
                    } 
                   
               
               
                    CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ] 
                   
               
               
                    coding_tree_unit( )  
                   
               
               
                    if( entropy_coding_sync_enabled_flag &amp;&amp;  
                   
               
               
                      ( ( j + 1 ) % BrickWidth[ SliceBrickIdx[ i ] ] 
                   
               
               
                 = = 0 ) ) { 
                   
               
               
                      end _of_subset_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                     if( j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ] − 1 )  
                   
               
               
                      byte_alignment( )  
                   
               
               
                    } 
                   
               
               
                   } 
                   
               
               
                   if( !entropy_coding_sync_enabled_flag ) { 
                   
               
               
                     end _of_brick_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                    if( i &lt; NumBricksInCurrSlice − 1 )  
                   
               
               
                     byte_alignment( )  
                   
               
               
                   } 
                   
               
               
                  } 
                   
               
               
                 } 
               
               
                   
               
            
           
         
       
     
     7.4.8.5 Coding Unit Semantics 
     When all the following conditions are true, the history-based motion vector predictor (HMVP) list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
         IsInSmr[x0][y0] is equal to TRUE.   SmrX[x0][y0] is equal to x0.   SmrY[x0][y0] is equal to y0.       

     The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1: 
       CbPosX[ x][y]=x 0   (7-135)
 
       CbPosY[ x][y]=y 0   (7-136)
 
       CbWidth[ x][y]= cbWidth   (7-137)
 
       CbHeight[ x][y]= cbHeight   (7-138)
 
     
       
       
       
       
       
       
       
       
       
       
       
         
         
           
             
               
               
               
               
               
               
                 
                   
                   
                   
                   
                   
                   
                   
                   
                   
                 
               
             
           
         
       
    
     
       
      
       
       
      
     
     8.6.2 Derivation Process for Motion Vector Components for IBC Blocks 
     8.6.2.1 General 
     Inputs to this process are:
         a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples,   a variable cbHeight specifying the height of the current coding block in luma samples.       

     Outputs of this process are:
         the luma motion vector in 1/16 fractional-sample accuracy mvL.       

     The luma motion vector mvL is derived as follows:
         The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.   When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
           1. The variable mvd is derived as follows:   
               

       mvd[0]=MvdL0[xCb][yCb][0]  (8-883)
 
       mvd[1]=MvdL0[xCb][yCb][1]  (8-884)
             2. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.   3. The luma motion vector mvL is modified as follows:           

         u[ 0]=(mvL[0]+mvd[0]+2 18 )%2 18    (8-885)
 
       mvL[0]=( u[ 0]&gt;=2 17 )?( u[ 0]−2 18 ): u[ 0]  (8-886)
 
         u[ 1]=(mvL[1]+mvd[1]+2 18 )%2 18    (8-887)
 
       mvL[1]=( u[ 1]&gt;=2 17 )?( u[ 1]−2 18 ):u[1]  (8-888)
          NOTE 1—The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2 17  to 2 17 −1, inclusive.       

     The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is invoked with luma motion vector mvL. 
     
       
       
       
       
       
       
         
         
           
             
               
               
               
               
             
             
               
               
               
               
               
               
               
               
             
           
         
       
    
     8.7.5 Picture Reconstruction Process 
     8.7.5.1 General 
     Inputs to this process are:
         a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,   the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,   a variable cIdx specifying the colour component of the current block,   an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,   an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.       

     Output of this process   a reconstructed picture sample array recSamples      
     Depending on the value of the color component cIdx, the following assignments are made:
         If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array S L  and the function clipCidx1 corresponds to Clip1 Y .   Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S Cb  and the function clipCidx1 corresponds to Clip1 C .   Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S Cr  and the function clipCidx1 corresponds to Clip1 C .       

     Depending on the value of slice_lmcs_enabled_flag, the following applies:
         If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1:       

       recSamples[xCurr+ i] [yCurr+ j]= clipCidx1(predSamples[ i][j]+ resSamples[ i][j] )    (8-992)
         Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
           If cIdx is equal to 0, the following applies:
               The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.   
               Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.
 
     
   
               

     
       
      
       
       
       
       
      
     
     
       
       
     
     5.18 Embodiment #18 
     The changes in some examples are indicated in bolded, underlined, italicized text in this disclosure. 
     7.3.7 Slice Data Syntax 
     7.3.7.1 General Slice Data Syntax 
       
     
       
         
           
               
               
             
               
                   
               
               
                 slice_data( ) { 
                 
                   Descriptor 
                 
               
               
                   
               
             
            
               
                  for( i = 0; i &lt; NumBricksInCurrSlice; i++ ) { 
                   
               
               
                   CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ] 
                   
               
               
                   for( j = 0; j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++,  
                   
               
               
                 CtbAddrInBs++ ) { 
                   
               
               
                    if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) { 
                   
               
               
                     NumHmvpCand = 0  
                   
               
               
                     NumHmvpIbcCand = 0  
                   
               
               
                        
                   
               
               
                    } 
                   
               
               
                    CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ] 
                   
               
               
                    coding_tree_unit( )  
                   
               
               
                    if( entropy_coding_sync_enabled_flag &amp;&amp;  
                   
               
               
                      ( ( j + 1 ) % BrickWidth[ SliceBrickIdx[ i ] ] 
                   
               
               
                 = = 0 ) ) { 
                   
               
               
                      end _of_subset_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                     if( j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ] − 1 )  
                   
               
               
                      byte_alignment( )  
                   
               
               
                    } 
                   
               
               
                   } 
                   
               
               
                   if( !entropy_coding_sync_enabled_flag ) { 
                   
               
               
                     end _of_brick_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                    if( i &lt; NumBricksInCurrSlice − 1 )  
                   
               
               
                     byte_alignment( )  
                   
               
               
                   } 
                   
               
               
                  } 
                   
               
               
                 } 
               
               
                   
               
            
           
         
       
     
     7.4.8.5 Coding Unit Semantics 
     When all the following conditions are true, the history-based motion vector predictor list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
         IsInSmr[x0][y0] is equal to TRUE.   SmrX[x0][y0] is equal to x0.   SmrY[x0][y0] is equal to y0.       

     The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1: 
       CbPosX[ x][y]=x 0   (7-135)
 
       CbPosY[ x][y]=y 0   (7-135)
 
       CbWidth[ x][y]= cbWidth   (7-135)
 
       CbHeight[ x][y]= cbHeight   (7-135)
 
     
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
         
         
           
             
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
             
           
         
       
    
     8.6.2 Derivation Process for Motion Vector Components for IBC Blocks 
     8.6.2.1 General 
     Inputs to this process are:
         a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples,   a variable cbHeight specifying the height of the current coding block in luma samples.       

     Outputs of this process are:
         the luma motion vector in 1/16 fractional-sample accuracy mvL.       

     The luma motion vector mvL is derived as follows:
         The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.   When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
           1. The variable mvd is derived as follows:   
               

       mvd[0]=MvdL0[xCb][yCb][0]  (8-883)
 
       mvd[1]=MvdL0[xCb][yCb][1]  (8-884)
             2. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.   3. The luma motion vector mvL is modified as follows:           

         u[ 0]=(mvL[0]+mvd[0]+2 18 )%2 18    (8-885)
 
       mvL[0]=( u[ 0]&gt;=2 17 )?( u[ 0]−2 18 ): u[ 0]  (8-886)
 
         u[ 1]=(mvL[1]+mvd[1]+2 18 %2 18    (8-887)
 
       mvL[1]=( u[ 1]&gt;=2 17 )?( u[ 1]−2 18 ): u[ 1]  (8-888)
          NOTE 1—The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2 17  to 2 17 −1, inclusive.       

     The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is Invoked With Luma Motion Vector mvL. 
     
       
       
       
       
       
       
       
       
       
       
       
       
       
         
         
           
             
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
               
               
               
             
           
         
       
    
     8.6.3 Decoding Process for IBC Blocks 
     8.6.3.1 General 
     This process is invoked when decoding a coding unit coded in IBCprediction mode. 
     Inputs to this process are:
         a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples, a variable cbHeight specifying the height of the current coding block in luma samples,   colour component index of the current block.                               

     Outputs of this process are:
         an array predSamples of prediction samples.
 
         
 
 
       

     
       
      
       
       
       
       
       
      
     
     
       
     
     
       
      
       
       
       
       
       
       
      
     
     
       
     
     
       
      
       
       
       
       
       
       
      
     
     8.7.5 Picture Reconstruction Process 
     8.7.5.1 General 
     Inputs to this process are:
         a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,   the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,   a variable cIdx specifying the colour component of the current block,   an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,   an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.       

     Output of this process   a reconstructed picture sample array recSamples        
     Depending on the value of the color component cIdx, the following assignments are made:
         If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array SL and the function clipCidx 1  corresponds to Clip1 Y .   Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array SCb and the function clipCidx 1  corresponds to Clip1 C .   Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S Cr  and the function clipCidx 1  corresponds to Clip1 C .       

     Depending on the value of slice_lmcs_enabled_flag, the following applies:
         If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1:       

       recSamples[xCurr+ i] [yCurr+ j]= clipCidx1(predSamples[ i][j]+ resSamples[ i][j] )   (8-992)
         Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
           If cIdx is equal to 0, the following applies:
               The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.   
               Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.
 
     
 
             
   
               

     
       
      
       
       
       
       
       
      
     
     
       
       
       
       
       
       
       
       
       
       
     
     
       
      
       
       
       
       
       
      
     
     
       
       
       
       
       
       
       
       
       
       
     
     
       
      
       
       
       
       
       
      
     
     
       
       
     
     5.19 Embodiment #19 
     The changes in some examples are indicated in bolded, underlined, text in this disclosure. 
     7.3.7 Slice Data Syntax 
     7.3.7.1 General Slice Data Syntax 
       
     
       
         
           
               
               
             
               
                   
               
               
                 slice_data( ) { 
                 
                   Descriptor 
                 
               
               
                   
               
             
            
               
                  for( i = 0; i &lt; NumBricksInCurrSlice; i++ ) { 
                   
               
               
                   CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ] 
                   
               
               
                   for( j = 0; j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++,  
                   
               
               
                 CtbAddrInBs++ ) { 
                   
               
               
                    if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) { 
                   
               
               
                     NumHmvpCand = 0  
                   
               
               
                     NumHmvpIbcCand = 0  
                   
               
               
                    __   
                   
               
               
                    } 
                   
               
               
                    CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ] 
                   
               
               
                    coding_tree_unit( )  
                   
               
               
                    if( entropy_coding_sync_enabled_flag &amp;&amp;  
                   
               
               
                      ( ( j + 1 ) % BrickWidth[ SliceBrickIdx[ i ] ] 
                   
               
               
                 = = 0 ) ) { 
                   
               
               
                      end _of_subset_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                     if( j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ] − 1 )  
                   
               
               
                      byte_alignment( )  
                   
               
               
                    } 
                   
               
               
                   } 
                   
               
               
                   if( !entropy_coding_sync_enabled_flag ) { 
                   
               
               
                     end _of_brick_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                    if( i &lt; NumBricksInCurrSlice − 1 )  
                   
               
               
                     byte_alignment( )  
                   
               
               
                   } 
                   
               
               
                  } 
                   
               
               
                 } 
               
               
                   
               
            
           
         
       
     
     7.4.8.5 Coding Unit Semantics 
     When all the following conditions are true, the history-based motion vector predictor list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
         IsInSmr[x0][y0] is equal to TRUE.   SmrX[x0][y0] is equal to x0.   SmrY[x0][y0] is equal to y0.       

     The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1: 
       CbPosX[ x][y]=x 0   (7-135)
 
       CbPosY[ x][y]=y 0   (7-136)
 
       CbWidth[ x][y]= cbWidth   (7-137)
 
       CbHeight[ x][y]= cbHeight   (7-138)
 
     
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
         
         
           
             
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
               
               
               
               
             
           
         
       
    
     8.6.2 Derivation Process for Motion Vector Components for IBC Blocks 
     8.6.2.1 General 
     Inputs to this process are:
         a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples,   a variable cbHeight specifying the height of the current coding block in luma samples.       

     Outputs of this process are:
         the luma motion vector in 1/16 fractional-sample accuracy mvL.       

     The luma motion vector mvL is derived as follows:
         The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.   When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
           1. The variable mvd is derived as follows:   
               

       mvd[0]=MvdL0[xCb][yCb][0]  (8-883)
 
       mvd[1]=MvdL0[xCb][yCb][1]  (8-884)
             2. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.   3. The luma motion vector mvL is modified as follows:           

         u[ 0]=(mvL[0]+mvd[0]+2 18 )%2 18    (8-885)
 
       mvL[0]=( u[ 0]&gt;=2 17 )?( u[ 0]−2 18 ):  u[ 0]  (8-886)
 
         u[ 1]=(mvL[1]+mvd[1]+2 18 )%2 18    (8-887)
 
       mvL[1]=( u[ 1]&gt;=2 17 )?( u[ 1]−2 18 ):  u[ 1]  (8-888)
          NOTE 1—The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2 17  to 2 17 −1, inclusive.       

     The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is invoked with luma motion vector mvL. 
     
       
       
       
       
       
       
       
       
       
       
       
       
       
         
         
           
             
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
               
             
           
         
       
    
     8.6.3 Decoding Process for IBC Blocks 
     8.6.3.1 General 
     This process is invoked when decoding a coding unit coded in IBC prediction mode. 
     Inputs to this process are:
         a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples,   a variable cbHeight specifying the height of the current coding block in luma samples,                                                                       

     
       
      
       
       
       
       
       
      
     
     
       
     
     
       
      
       
       
       
       
       
      
     
     
       
     
     
       
      
       
       
       
       
       
      
     
     8.7.5 Picture Reconstruction Process 
     8.7.5.1 General 
     Inputs to this process are:
         a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,   the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,   a variable cIdx specifying the colour component of the current block,   an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,   an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.       

     Output of this process are a reconstructed picture sample array recSamples and IBC buffer arrays ibcBuf L , ibcBuf Cb , ibcBuf Cr . 
     Depending on the value of the color component cIdx, the following assignments are made:
         If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array S L  and the function clipCidx1 corresponds to Clip1 Y .   Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S Cb  and the function clipCidx1 corresponds to Clip1 C .   Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S Cr  and the function clipCidx 1  corresponds to Clip1 C .       

     Depending on the value of slice_lmcs_enabled_flag, the following applies:
         If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1:       

          (8-992)
         Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
           If cIdx is equal to 0, the following applies:
               The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.   
               Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.
 
     
 
           
   
               

     
       
      
       
       
       
       
       
      
     
     
       
       
       
       
       
       
       
       
       
       
     
     
       
      
       
       
       
       
       
      
     
     
       
       
       
       
       
       
       
       
       
       
     
     
       
      
       
       
       
       
       
      
     
     
       
       
     
     5.20 Embodiment #20 
     The changes in some examples are indicated in bolded, underlined, italicized text in this disclosure. 
     7.3.7 Slice Data Syntax 
     7.3.7.1 General Slice Data Syntax 
       
     
       
         
           
               
               
             
               
                   
               
               
                 slice_data( ) { 
                 
                   Descriptor 
                 
               
               
                   
               
             
            
               
                  for( i = 0; i &lt; NumBricksInCurrSlice; i++ ) { 
                   
               
               
                   CtbAddrInBs = FirstCtbAddrBs[ SliceBrickIdx[ i ] ] 
                   
               
               
                   for( j = 0; j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ]; j++,  
                   
               
               
                 CtbAddrInBs++ ) { 
                   
               
               
                    if( ( j % BrickWidth[ SliceBrickIdx[ i ] ] ) = = 0 ) { 
                   
               
               
                     NumHmvpCand = 0  
                   
               
               
                     NumHmvpIbcCand = 0  
                   
               
               
                         
                   
               
               
                    } 
                   
               
               
                    CtbAddrInRs = CtbAddrBsToRs[ CtbAddrInBs ] 
                   
               
               
                    coding_tree_unit( )  
                   
               
               
                    if( entropy_coding_sync_enabled_flag &amp;&amp;  
                   
               
               
                      ( ( j + 1 ) % BrickWidth[ SliceBrickIdx[ i ] ] 
                   
               
               
                 = = 0 ) ) { 
                   
               
               
                      end _of_subset_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                     if( j &lt; NumCtusInBrick[ SliceBrickIdx[ i ] ] − 1 )  
                   
               
               
                      byte_alignment( )  
                   
               
               
                    } 
                   
               
               
                   } 
                   
               
               
                   if( !entropy_coding_sync_enabled_flag ) { 
                   
               
               
                     end _of_brick_one_bit /* equal to 1 */  
                 ae(v)  
               
               
                    if( i &lt; NumBricksInCurrSlice − 1 )  
                   
               
               
                     byte_alignment( )  
                   
               
               
                   } 
                   
               
               
                  } 
                   
               
               
                 } 
               
               
                   
               
            
           
         
       
     
     7.4.8.5 Coding Unit Semantics 
     When all the following conditions are true, the history-based motion vector predictor list for the shared merging candidate list region is updated by setting NumHmvpSmrIbcCand equal to NumHmvpIbcCand, and setting HmvpSmrIbcCandList[i] equal to HmvpIbcCandList[i] for i=0 . . . NumHmvpIbcCand−1:
         IsInSmr[x0][y0] is equal to TRUE.   SmrX[x0][y0] is equal to x0.   SmrY[x0][y0] is equal to y0.       

     The following assignments are made for x=x0 . . . x0+cbWidth−1 and y=y0 . . . y0+cbHeight−1: 
       CbPosX[ x][y]=x 0   (7-135)
 
       CbPosY[ x][y]=y 0   (7-136)
 
       CbWidth[ x][y]= cbWidth   (7-137)
 
       CbHeight[ x][y]= cbHeight   (7-138)
 
     
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
         
         
           
             
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
             
             
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
               
               
             
             
               
               
               
               
               
               
               
               
               
               
             
           
         
       
    
     8.6.2 Derivation Process for Motion Vector Components for IBC Blocks 
     8.6.2.1 General 
     Inputs to this process are:
         a luma location (xCb, yCb) of the top-left sample of the current luma coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples,   a variable cbHeight specifying the height of the current coding block in luma samples.       

     Outputs of this process are:
         the luma motion vector in 1/16 fractional-sample accuracy mvL.       

     The luma motion vector mvL is derived as follows:
         The derivation process for IBC luma motion vector prediction as specified in clause 8.6.2.2 is invoked with the luma location (xCb, yCb), the variables cbWidth and cbHeight inputs, and the output being the luma motion vector mvL.   When general_merge_flag[xCb][yCb] is equal to 0, the following applies:
           1. The variable mvd is derived as follows:   
               

       mvd[0]=MvdL0[xCb][yCb][0]  (8-883)
 
       mvd[1]=MvdL0[xCb][yCb][1]  (8-884)
             2. The rounding process for motion vectors as specified in clause 8.5.2.14 is invoked with mvX set equal to mvL, rightShift set equal to MvShift+2, and leftShift set equal to MvShift+2 as inputs and the rounded mvL as output.   3. The luma motion vector mvL is modified as follows:           

         u[ 0]=(mvL[0]+mvd[0]+2 18 )%2 18    (8-885)
 
       mvL[0]=( u[ 0]&gt;=2 17 )?( u[ 0]−2 18 ): u[ 0]  (8-886)
 
         u[ 1]=(mvL[1]+mvd[1]+2 18 )%2 18    (8-887)
 
       mvL[1]=( u[ 1]&gt;=2 17 )?( u[ 1]−2 18 ): u[ 1]  (8-888)
          NOTE 1—The resulting values of mvL[0] and mvL[1] as specified above will always be in the range of −2 17  to 2 17 −1, inclusive.       

     The updating process for the history-based motion vector predictor list as specified in clause 8.6.2.6 is invoked with luma motion vector mvL. 
     
       
       
       
       
       
       
       
       
       
       
         
         
           
             
               
               
               
               
             
             
               
               
               
               
               
               
             
           
         
       
    
     8.6.3 Decoding Process for IBC Blocks 
     8.6.3.1 General 
     This process is invoked when decoding a coding unit coded in IBC prediction mode. 
     Inputs to this process are:
         a luma location (xCb, yCb) specifying the top-left sample of the current coding block relative to the top-left luma sample of the current picture,   a variable cbWidth specifying the width of the current coding block in luma samples,   a variable cbHeight specifying the height of the current coding block in luma samples,   a variable cIdx specifying the colour component index of the current block.                                                       

     
       
      
       
       
       
       
       
      
     
     
       
     
     
       
      
       
       
       
       
       
      
     
     
       
     
     
       
      
       
       
       
       
       
      
     
     8.7.5 Picture Reconstruction Process 
     8.7.5.1 General 
     Inputs to this process are:
         a location (xCurr, yCurr) specifying the top-left sample of the current block relative to the top-left sample of the current picture component,   the variables nCurrSw and nCurrSh specifying the width and height, respectively, of the current block,   a variable cIdx specifying the colour component of the current block,   an (nCurrSw)×(nCurrSh) array predSamples specifying the predicted samples of the current block,   an (nCurrSw)×(nCurrSh) array resSamples specifying the residual samples of the current block.       

     Output of this process are a reconstructed picture sample array recSamples and IBC buffer arrays ibcBuf L , ibcBuf Cb , ibcBuf Cr . 
     Depending on the value of the color component cIdx, the following assignments are made:
         If cIdx is equal to 0, recSamples corresponds to the reconstructed picture sample array S L  and the function clipCidx1 corresponds to Clip1 Y .   Otherwise, if cIdx is equal to 1, tuCbfChroma is set equal to tu_cbf_cb[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S Cb  and the function clipCidx1 corresponds to Clip1 C .   Otherwise (cIdx is equal to 2), tuCbfChroma is set equal to tu_cbf_cr[xCurr][yCurr], recSamples corresponds to the reconstructed chroma sample array S Cr  and the function clipCidx1 corresponds to Clip1 C .       

     Depending on the value of slice_lmcs_enabled_flag, the following applies:
         If slice_lmcs_enabled_flag is equal to 0, the (nCurrSw)×(nCurrSh) block of the reconstructed samples recSamples at location (xCurr, yCurr) is derived as follows for i=0 . . . nCurrSw−1, j=0 . . . nCurrSh−1:       

       recSamples[xCurr+ i] [yCurr+ j]= clipCidx1(predSamples[ i][j]+ resSamples[ i][j] )    (8-992)
         Otherwise (slice_lmcs_enabled_flag is equal to 1), the following applies:
           If cIdx is equal to 0, the following applies:
               The picture reconstruction with mapping process for luma samples as specified in clause 8.7.5.2 is invoked with the luma location (xCurr, yCurr), the block width nCurrSw and height nCurrSh, the predicted luma sample array predSamples, and the residual luma sample array resSamples as inputs, and the output is the reconstructed luma sample array recSamples.   
               Otherwise (cIdx is greater than 0), the picture reconstruction with luma dependent chroma residual scaling process for chroma samples as specified in clause 8.7.5.3 is invoked with the chroma location (xCurr, yCurr), the transform block width nCurrSw and height nCurrSh, the coded block flag of the current chroma transform block tuCbfChroma, the predicted chroma sample array predSamples, and the residual chroma sample array resSamples as inputs, and the output is the reconstructed chroma sample array recSamples.
 
     
 
           
   
               

     
       
      
       
       
       
       
      
     
     
       
       
       
       
       
       
       
       
       
     
     
       
      
       
       
       
       
      
     
     
       
       
       
       
       
       
       
       
       
     
     
       
      
       
       
       
       
       
      
     
     
       
       
     
       FIG.  6    is a flowchart of an example method  600  of visual media (video or image) processing. The method  600  includes determining ( 602 ), for a conversion between a current video block and a bitstream representation of the current video block, a size of a buffer to store reference samples for the current video block using an intra block copy coding mode, and performing ( 604 ) the conversion using the reference samples stored in the buffer. 
     The following clauses describe some example preferred features implemented by embodiments of method  600  and other methods. Additional examples are provided in Section 4 of the present disclosure. 
     1. A method of video processing, comprising: determining, for a conversion between a current video block and a bitstream representation of the current video block, a size of a buffer to store reference samples for the current video block using an intra-block copy coding mode; and performing the conversion using the reference samples stored in the buffer. 
     2. The method of clause 1, wherein the size of the buffer is a predetermined constant. 
     3. The method of any of clauses 1-2, wherein the size is M×N, where M and N are integers. 
     4. The method of clause 3, wherein M×N is equal to 64×64 or 128×128 or 64×128. 
     5. The method of clause 1, wherein the size of the buffer is equal to a size of a coding tree unit of the current video block. 
     6. The method of clause 1, wherein the size of the buffer is equal to a size of a virtual pipeline data unit used during the conversion. 
     7. The method of clause 1, wherein the size of the buffer corresponds to a field in the bitstream representation. 
     8. The method of clause 7, wherein the field is included in the bitstream representation at a video parameter set or sequence parameter set or picture parameter set or a picture header or a slice header or a tile group header level. 
     9. The method of any of clauses 1-8, wherein the size of the buffer is different for reference samples for luma component and reference samples for chroma components. 
     10. The method of any of clauses 1-8, wherein the size of the buffer is dependent on chroma subsampling format of the current video block. 
     11. The method of any of clauses 1-8, wherein the reference samples are stored in RGB format. 
     12. The method of any of clauses 1-11, wherein the buffer is used for storing reconstructed samples before loop filtering and after loop filtering. 
     13. The method of clause 12, wherein loop filtering includes deblocking filtering or adaptive loop filtering (ALF) or sample adaptive offset (SAO) filtering. 
     14. A method of video processing, comprising: initializing, for a conversion between a current video block and a bitstream representation of the current video block, a buffer to store reference samples for the current video block using an intra-block copy coding mode using initial values for the reference samples; and performing the conversion using the reference samples stored in the buffer. 
     15. The method of clause 14, wherein the initial values correspond to a constant. 
     16. The method of any of clauses 14-15, wherein the initial values are a function of bit-depth of the current video block. 
     17. The method of clause 15, wherein the constant corresponds to a mid-grey value. 
     18. The method of clause 14, wherein the initial values correspond to pixel values of a previously decoded video block. 
     19. The method of clause 18, wherein the previously decoded video block corresponds to a decoded block prior to in-loop filtering. 
     20. The method of any of clauses 14-19, wherein a size of the buffer is at recited in one of clauses 1-13. 
     21. The method of any of clauses 1-20, wherein pixel locations within the buffer as addressed using x and y numbers. 
     22. The method of any of clauses 1-20, wherein pixel locations within the buffer as addressed using a single number that extends from 0 to M*N−1, where M and N are pixel width and pixel height of the buffer. 
     23. The method of any of clauses 1-20, wherein, the current bitstream representation includes a block vector for the conversion, wherein the block vector, denoted as (BVx,BVy) is equal to (x−x0,y−y0), where (x0, y0) correspond to an upper-left position of a coding tree unit of the current video block. 
     24. The method of any of clauses 1-20, wherein, the current bitstream representation includes a block vector for the conversion, wherein the block vector, denoted as (BVx,BVy) is equal to (x−x0+Tx,y−y0+Ty), where (x0, y0) correspond to an upper-left position of a coding tree unit of the current video block and wherein Tx and Ty are offset values. 
     25. The method of clause 24, wherein Tx and Ty are pre-defined offset values. 
     26. The method of any of clauses 1-20, wherein during the conversion, for a pixel at location (x0, y0) and having a block vector (BVx, BVy), a corresponding reference in the buffer is found at a reference location (x0+BVx, y0+BVy). 
     27. The method of clause 26, wherein in case that the reference location is outside the buffer, the reference in the buffer is determined by clipping at a boundary of the buffer. 
     28. The method of clause 26, wherein in case that the reference location is outside the buffer, the reference in the buffer is determined to have a predetermined value. 
     29. The method of any of clauses 1-20, wherein during the conversion, for a pixel at location (x0, y0) and having a block vector (BVx, BVy), a corresponding reference in the buffer is found at a reference location ((x0+BVx)mod M, (y0+BVy)mod N) where “mod” is modulo operation and M and N are integers representing x and y dimensions of the buffer. 
     30. A method of video processing, comprising: resetting, during a conversion between a video and a bitstream representation of the current video block, a buffer that stores reference samples for intra block copy coding at a video boundary; and performing the conversion using the reference samples stored in the buffer. 
     31. The method of clause 30, wherein the video boundary corresponds to a new picture or a new tile. 
     32. The method of clause 30, wherein the conversion is performed by updating, after the resetting, the buffer with reconstructed values of a Virtual Pipeline Data Unit (VPDU). 
     33. The method of clause 30, wherein the conversion is performed by updating, after the resetting, the buffer with reconstructed values of a coding tree unit. 
     34. The method of clause 30, wherein the resetting is performed at beginning of each coding tree unit row. 
     35. The method of clause 1, wherein the size of the buffer corresponds to L 64×64 previously decoded blocks., where L is an integer. 
     36. The method of any of clauses 1-35, wherein a vertical scan order is used for reading or storing samples in the buffer during the conversion. 
     37. A method of video processing, comprising: using, for a conversion between a current video block and a bitstream representation of the current video block, a buffer to store reference samples for the current video block using an intra-block copy coding mode, wherein a first bit-depth of the buffer is different than a second bit-depth of the coded data; and performing the conversion using the reference samples stored in the buffer. 
     38. The method of clause 37, wherein the first bit-depth is greater than the second bit-depth. 
     39. The method of any of clauses 37-38, wherein the first bit-depth is identical to a bit-depth of a reconstruction buffer used during the conversion. 
     40. The method of any of clauses 37-39, wherein the first bit-depth is signalled in the bitstream representation as a value or a difference value. 
     41. The method of any of clauses 37-40, wherein the conversion uses different bit-depths for chroma and luma components. 
     Additional embodiments and examples of clauses 37 to 41 are described in Item 7 in Section 4. 
     42. A method of video processing, comprising: performing a conversion between a current video block and a bitstream representation of the current video block using an intra-block copy mode in which a first precision used for prediction calculations during the conversion is lower than a second precision used for reconstruction calculations during the conversion. 
     43. The method of clause 42, wherein the prediction calculations include determining a prediction sample value from a reconstructed sample value using clip{{p+[1&lt;&lt;(b−1)]}&gt;&gt;b,0,(1&lt;&lt;bitdepth)−1}&lt;&lt;b, where p is the reconstructed sample value, b is a predefined bit-shifting value, and bitdepth is a prediction sample precision. 
     Additional embodiments and examples of clauses 42 to 43 are described in Items 28 to 31 and 34 in Section 4. 
     44. A method of video processing, comprising: performing a conversion between a current video block and a bitstream representation of the current video block using an intra-block copy mode in which a reference area of size nM×nM is used for a coding tree unit size M×M, where n and M are integers and wherein the current video block is positioned in the coding tree unit, and wherein the reference area is a nearest available n×n coding tree unit in a coding tree unit row corresponding to the current video block. 
     Additional embodiments and examples of clause 4 are described in Item 35 in Section 4. 
     45. A method of video processing, comprising: performing a conversion between a current video block and a bitstream representation of the current video block using an intra-block copy mode in which a reference area of size nM×nM is used for a coding tree unit size other than M×M, where n and M are integers and wherein the current video block is positioned in the coding tree unit, and wherein the reference area is a nearest available n×n-1 coding tree unit in a coding tree unit row corresponding to the current video block. 
     Additional embodiments and examples of clause 4 are described in Item 36 in Section 4.  FIGS.  8  and  9    show additional example embodiments. 
     46. The method of clause 44 or 45, wherein M=mW and N=H, where W and H are width and height of a coding tree unit (CTU) of the current video block, and m is a positive integer. 
     47. The method of clause 44 or 45, wherein M=W and N=nH, where W and H are width and height of a coding tree unit (CTU), and n is a positive integer. 
     48. The method of clause 44 or 45, wherein M=mW and N=nH, where W and H are width and height of a coding tree unit (CTU), m and n are positive integers. 
     49. The method of any of clauses 46-48, wherein n and m depend on a size of the CTU. 
     50. A method of video processing, comprising: determining, for a conversion between a current video block of a video and a bitstream representation of the current video block, validity of a block vector corresponding to the current video block of a component c of the video using a component X of the video, wherein the component X is different from a luma component of the video; and performing the conversion using the block vector upon determining that the block vector is valid for the current video block. Here, the block vector, denoted as (BVx,BVy) is equal to (x−x0,y−y0), where (x0, y0) correspond to an upper-left position of a coding tree unit of the current video block. 
     51. The method of clause 50, wherein the component c corresponds to the luma component of the video. 
     52. The method of clause 50, wherein the current video block is a chroma block and the video is in a 4:4:4 format. 
     53. The method of clause 50, wherein the video is in a 4:2:0 format, and wherein the current video block is a chroma block starting at position (x, y), and wherein the determining comprises determining the block vector to be invalid for a case in which isRec(c, ((x+BVx)&gt;&gt;5&lt;&lt;5)+64−(((y+BVy)&gt;&gt;5)&amp;1)*32+(x%32), ((y+BVy)&gt;&gt;5&lt;&lt;5)+(y%32)) is true. 
     54. The method of clause 50, wherein the video is in a 4:2:0 format, and wherein the current video block is a chroma block starting at position (x, y), and wherein the determining comprises determining the block vector to be invalid for a case in which if isRec(c, x+BVx+ChromaSTU_size, y) is true. 
     55. A method of video processing, comprising: determining, selectively for a conversion between a current video block of a current virtual pipeline data unit (VPDU) of a video region and a bitstream representation of the current video block, to use K1 previously processed VPDUs from a first row of the video region and K2 previously processed VPDUs from a second row of the video region; and performing the conversion, wherein the conversion excludes using remaining of the current VPDU. 
     56. The method of clause 55, wherein K1=1 and K2=2. 
     57. The method of any of clauses 55-56, wherein the current video block is selectively processed based on a dimension of the video region or a dimension of the current VPDU. 
     58. A method of video processing, comprising: performing a validity check of a block vector for a conversion between a current video block and a bitstream representation of the current video block, wherein the block vector is used for intra block copy mode; and using a result of the validity check to selectively use the block vector during the conversion. 
     59. The method of clause 58, wherein an intra block copy (IBC) buffer is used during the conversion, wherein a width and a height of the IBC buffer as Wbuf and Hbuf an dimensions of the current video block are W×H and wherein the block vector is represented as (BVx, BVy), and wherein the current video block is in a current picture having dimensions Wpic and Hpic and a coding tree unit having Wctu and Hctu as width and height, and wherein the validity check uses a pre-determined rule. 
     60. The method of any of clauses 58-59, wherein the current video block is a luma block, a chroma block, a coding unit CU, a transform unit TU, a 4×4 block, a 2×2 block, or a subblock of a parent block starting from pixel coordinates (X, Y). 
     61. The method of any of clauses 58-60, wherein the validity check considers the block vector that falls outside a boundary of the current picture as valid. 
     62. The method of any of clauses 58-60, wherein the validity check considers the block vector that falls outside a boundary of the coding tree unit as valid. 
     Items 23-30 in the previous section provide additional examples and variations of the above clauses 58-62. 
     63. The method of any of clauses 1-62, wherein the conversion includes generating the bitstream representation from the current video block. 
     64. The method of any of clauses 1-62, wherein the conversion includes generating pixel values of the current video block from the bitstream representation. 
     65. A video encoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1-62. 
     66. A video decoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses 1-62. 
     67. A computer readable medium having code stored thereon, the code embodying processor-executable instructions for implementing a method recited in any of or more of clauses 1-62. 
       FIG.  7    is a block diagram of a hardware platform of a video/image processing apparatus  700 . The apparatus  700  may be used to implement one or more of the methods described herein. The apparatus  700  may be embodied in a smartphone, tablet, computer, Internet of Things (IoT) receiver, and so on. The apparatus  700  may include one or more processors  702 , one or more memories  704  and video processing hardware  706 . The processor(s)  702  may be configured to implement one or more methods (including, but not limited to, method  600 ) described in the present disclosure. The memory (memories)  704  may be used for storing data and code used for implementing the methods and embodiments described herein. The video processing hardware  706  may be used to implement, in hardware circuitry, some embodiments described in the present disclosure. 
     The bitstream representation corresponding to a current video block need not be a contiguous set of bits and may be distributed across headers, parameter sets, and network abstraction layer (NAL) packets. 
     Section A: Another Additional Example Embodiment 
     In Section A, we present another example embodiment in which the current version of the VVC standard may be modified for implementing some of the embodiments described in the present disclosure. 
     This section analyzes several issues in the current IBC reference buffer design and presents a different design to address the issues. An independent IBC reference buffer is proposed instead of mixing with decoding memory. Compared with the current anchor, the proposed scheme shows −0.99%/−0.71%/−0.79% AI/RA/LD-B luma BD-rate for class F and −2.57%/−1.81%/−1.36% for 4:2:0 TGM, with 6.7% memory reduction; or −1.31%/−1.01%/−0.81% for class F and −3.23%/−2.33%/−1.71% for 4:2:0 TGM with 6.7% memory increase. 
     A1. Introduction 
     Intra block copy, i.e., IBC (or current picture referencing, i.e., CPR previously) coding mode, is adopted. It is realized that IBC reference samples should be stored in on-chip memory and thus a limited reference area of one CTU is defined. To restrict the extra on-chip memory for the buffer, the current design reuses the 64×64 memory for decoding the current VPDU so that only 3 additional 64×64 blocks&#39; memory is needed to support IBC. When CTU size is 128×128, currently the reference area is shown in  FIG.  2   . 
     In the current draft (VVC draft 4), the area is defined as 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                 - 
                 The following conditions shall be true: 
               
            
           
           
               
               
               
            
               
                   
                  ( yCb + ( mvL[ 1 ] &gt;&gt; 4 ) ) &gt;&gt; CtbLog2SizeY = yCb &gt;&gt; CtbLog2SizeY 
                 (8-972) 
               
               
                   
                  ( yCb + ( mvL[ 1 ] &gt;&gt; 4 ) + cbHeight − 1) &gt;&gt; CtbLog2SizeY = yCb &gt;&gt; 
                 (8-973) 
               
               
                   
                  CtbLog2SizeY  
                 (8-974) 
               
               
                   
                  ( xCb + ( mvL[ 0 ] &gt;&gt; 4 ) ) &gt;&gt; CtbLog2SizeY &gt;= ( xCb &gt;&gt; CtbLog2SizeY ) − 1 
                   
               
               
                   
                  ( xCb + ( mvL[ 0 ] &gt;&gt; 4 ) + cbWidth − 1) &gt;&gt; CtbLog2SizeY &lt;= (xCb &gt;&gt; 
                 (8-975) 
               
            
           
           
               
               
            
               
                   
                  CtbLog2SizeY ) 
               
               
                   
                  [Ed. (SL): conditions (8-218) and (8-216) might have been checked by 6.4.X.] 
               
               
                 - 
                 When ( xCb + (mvL[ 0 ] &gt;&gt; 4 ) ) &gt;&gt; CtbLog2SizeY is equal to ( xCb &gt;&gt; CtbLog2SizeY ) − 1, the 
               
               
                   
                 derivation process for block availability as specified in clause 6.4.X [Ed. (BB): Neighboring blocks 
               
               
                   
                 availability checking process tbd] is invoked with the current luma location( xCurr, yCurr ) set 
               
               
                   
                 equal to ( xCb, yCb ) and the neighboring luma location ( ( ( xCb + ( mvL[ 0 ] &gt;&gt; 4 ) + 
               
               
                   
                 CtbSizeY ) &gt;&gt; ( CtbLog2SizeY − 1 ) ) &lt;&lt; ( CtbLog2SizeY − 1 ), ( ( yCb + (mvL[ 1 ] &gt;&gt; 4 ) ) &gt;&gt; 
               
               
                   
                 ( CtbLog2SizeY − 1 ) ) &lt;&lt; ( CtbLog2SizeY − 1 ) ) as inputs, and the output shall be equal to 
               
               
                   
                 FALSE. 
               
               
                   
               
            
           
         
       
     
     Thus, the total reference size is a CTU. 
     A2. Potential Issues of the Current Design 
     The current design assumes to reuse the 64×64 memory for decoding the current VPDU and the IBC reference is aligned to VPDU memory reuse accordingly. Such a design bundles VPDU decoding memory with the IBC buffer. There might be several issues:
         1. To handle smaller CTU size might be an issue. Suppose that CTU size is 32×32, it is not clear whether the current 64×64 memory for decoding the current VPDU can support 32×32 level memory reuse efficiently in different architectures.   2. The reference area varies significantly. Accordingly, too many bitstream conformance constraints are introduced. It places extra burden to encoder to exploit reference area efficiently and avoid generating legal bitstreams. It also increases the possibility to have invalid BVs in different modules, e.g., merge list. To handle those invalid BVs may introduce extra logics or extra conformance constraints. It not only introduces burdens to encoder or decoder, it may also create divergence between BV coding and MV coding.   3. The design does not scale well. Because VPDU decoding is mixed with IBC buffer, it is not easy to increase or decrease reference area relative to the current one 128×128 CTU design. It may limit the flexibility to exploit a better coding efficiency vs. on-chip memory trade-off in the later development, e.g., a lower or higher profile.   4. The bit-depth of IBC reference buffer is linked with decoding buffer. Even though screen contents usually have a lower bit-depth than internal decoding bit-depth, the buffer still needs to spend memory to store bits mostly representing rounding or quantization noises. The issue becomes even severe when considering higher decoding bit-depth configurations.       

     A3. A Clear IBC Buffer Design 
     To address issues listed in the above sub-section, we propose to have a dedicated IBC buffer, which is not mixed with decoding memory. 
     For 128×128 CTU, the buffer is defined as 128×128 with 8-bit samples, when a CU (x, y) with size w×h has been decoded, its reconstruction before loop-filtering is converted to 8-bit and written to the w×h block area starting from position (x%128, y%128). Here the modulo operator % always returns a positive number, i.e., for x&lt;0, x%L −(−x%L), e.g., −3%128=125. 
     Assume that a pixel (x,y) is coded in IBC mode with BV=(BVx,BVy), it is prediction sample in the IBC reference buffer locates at ((x+BVx)%128, (y+BVy)%128) and the pixel value will be converted to 10-bit before prediction. 
     When the buffer is considered as (W, H), after decoding a CTU or CU starting from (x, y), the reconstructed pixels before loop-filtering will be stored in the buffer starting from (x%W, y%H). Thus, after decoding a CTU, the corresponding IBC reference buffer will be updated accordingly. Such setting might happen when CTU size is not 128×128. For example, for 64×64 CTU, with the current buffer size, it can be considered as a 256×64 buffer. For 64×64 CTU,  FIG.  2    shows the buffer status. 
       FIG.  12    is an illustration of IBC reference buffer status, where a block denotes a 64×64 CTU. 
     In such a design, because the IBC buffer is different from the VPDU decoding memory, all the IBC reference buffer can be used as reference. 
     When the bit-depth of the IBC buffer is 8-bit, compared with the current design that needs 3 additional 10-bit 64×64 buffer, the on-chip memory increase is (8*4)/(10*3)−100%=6.7%. 
     If we further reduce the bit-depth. The memory requirement can be further reduced. For example, for 7-bit buffer, the on-chip memory saving is 100%−(7*4)/(10*3)=6.7%. 
     With the design, the only bitstream conformance constraint is that the reference block shall be within the reconstructed area in the current CTU row of the current Tile. 
     When initialization to 512 is allowed at the beginning of each CTU row, all bitstream conformance constraints can be removed. 
     A4. Experimental Results 
     In some embodiments, the disclosed methods can be implemented using VTM-4.0 software. 
     For a 10-bit buffer implementation and common test conditions (CTC), the decoder is fully compatible to the current VTM4.0 encoder, which means that the proposed decoder can exactly decode the VTM-4.0 CTC bitstreams. 
     For a 7-bit buffer implementation, the results shown in Table I. 
     For an 8-bit buffer implementation, the results shown in Table II. 
     
       
         
           
               
             
               
                 TABLE I 
               
               
                   
               
               
                 Performance with a 7-bit buffer. The anchor is VTM-4.0 with  
               
               
                 IBC on for all sequences. 
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
            
               
                   
                 All Intra  
               
               
                   
                 Over VTM-4.0 w/ IBC on  
               
            
           
           
               
               
               
               
               
               
            
               
                   
                 Y  
                 U  
                 V  
                 EncT  
                 DccT 
               
               
                   
               
               
                 Class A1  
                 −0.01%  
                 −0.09%  
                 −0.10%  
                 132%  
                 101%  
               
               
                 Class A2  
                 0.05%  
                 0.00%  
                 0.06%  
                 135%  
                 100%  
               
               
                 Class B  
                 0.00%  
                 −0.02%  
                 0.01%  
                 135%  
                 100%  
               
               
                 Class C  
                 −0.02%  
                 0.01%  
                 0.03%  
                 130%  
                  98%  
               
               
                 Class E  
                 −0.13%  
                 −0.16%  
                 −0.04%  
                 135%  
                  99%  
               
               
                 Overall  
                 −0.02%  
                 −0.05%  
                 0.00%  
                 133%  
                 100%  
               
               
                 Class D  
                 0.04%  
                 0.04%  
                 0.12%  
                 127%  
                 107%  
               
               
                 Class F  
                 −0.99%  
                 −1.14%  
                 −1.18%  
                 115%  
                  99%  
               
               
                 4:2:0 TGM  
                 −2.57%  
                 −2.73%  
                 −2.67%  
                 104%  
                 102% 
               
               
                   
               
            
           
           
               
               
            
               
                   
                 Random Access  
               
               
                   
                 Over VTM-4.0 w/ IBC on  
               
            
           
           
               
               
               
               
               
               
            
               
                   
                 Y  
                 U  
                 V  
                 EncT  
                 DecT 
               
               
                   
               
               
                 Class A1  
                 0.02%  
                 −0.01%  
                 0.01%  
                 109%  
                 100%  
               
               
                 Class A2  
                 0.00%  
                 −0.04%  
                 0.03%  
                 111%  
                 100%  
               
               
                 Class B  
                 −0.01%  
                 −0.10%  
                 −0.22%  
                 113%  
                 101%  
               
               
                 Class C  
                 −0.01%  
                 0.17%  
                 0.12%  
                 115%  
                 100%  
               
               
                 Class E  
                   
                   
                   
                   
                   
               
               
                 Overall  
                 0.00%  
                 0.00%  
                 −0.04%  
                 112%  
                 100%  
               
               
                 Class D  
                 0.05%  
                 0.16%  
                 0.20%  
                 117%  
                 101%  
               
               
                 Class F  
                 −0.71%  
                 −0.77%  
                 −0.77%  
                 109%  
                  99%  
               
               
                 4:2:0 TGM  
                 −1.81%  
                 −1.65%  
                 −1.64%  
                 107%  
                 101% 
               
               
                   
               
            
           
         
       
     
     
       
         
           
               
             
               
                 TABLE II 
               
               
                   
               
               
                 Performance with an 8-bit buffer. The anchor is VTM-4.0 with  
               
               
                 IBC on for all sequences 
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
            
               
                   
                 All Intra  
               
               
                   
                 Over VTM-4.0 w/ IBC on  
               
            
           
           
               
               
               
               
               
               
            
               
                   
                 Y  
                 U  
                 V  
                 EncT  
                 DecT 
               
               
                   
               
               
                 Class A1  
                 −0.01%  
                 0.02%  
                 −0.10%  
                 129%  
                 102%  
               
               
                 Class A2  
                 0.02%  
                 −0.06%  
                 −0.02%  
                 134%  
                 102%  
               
               
                 Class B  
                 −0.04%  
                 −0.02%  
                 −0.07%  
                 135%  
                 101%  
               
               
                 Class C  
                 −0.03%  
                 0.04%  
                 0.00%  
                 130%  
                  98%  
               
               
                 Class E  
                 −0.16%  
                 −0.14%  
                 −0.08%  
                 134%  
                 100%  
               
               
                 Overall  
                 −0.04%  
                 −0.03%  
                 −0.05%  
                 133%  
                 100%  
               
               
                 Class D  
                 0.00%  
                 0.04%  
                 0.02%  
                 126%  
                 101%  
               
               
                 Class F  
                 −1.31%  
                 −1.27%  
                 −1.29%  
                 114%  
                  98%  
               
               
                 4:2:0 TGM  
                 −3.23%  
                 −3.27%  
                 −3.24%  
                 101%  
                 100% 
               
               
                   
               
            
           
           
               
               
            
               
                   
                 Random Access  
               
               
                   
                 Over VTM-4.0 w/ IBC on  
               
            
           
           
               
               
               
               
               
               
            
               
                   
                 Y  
                 U  
                 V  
                 EncT  
                 DecT 
               
               
                   
               
               
                 Class A1  
                 −0.01%  
                 −0.08%  
                 0.04%  
                 107%  
                  99%  
               
               
                 Class A2  
                 −0.03%  
                 −0.16%  
                 0.06%  
                 110%  
                  99%  
               
               
                 Class B  
                 −0.01%  
                 −0.14%  
                 −0.22%  
                 111%  
                  99%  
               
               
                 Class C  
                 −0.01%  
                 0.15%  
                 0.09%  
                 115%  
                 100%  
               
               
                 Class E  
                   
                   
                   
                   
                   
               
               
                 Overall  
                 −0.01%  
                 −0.05%  
                 −0.03%  
                 111%  
                  99%  
               
               
                 Class D  
                 0.01%  
                 0.19%  
                 0.22%  
                 116%  
                 101%  
               
               
                 Class F  
                 −1.01%  
                 −0.99%  
                 −1.01%  
                 108%  
                  99%  
               
               
                 4:2:0 TGM  
                 −2.33%  
                 −2.14%  
                 −2.19%  
                 105%  
                 100% 
               
               
                   
               
            
           
           
               
               
            
               
                   
                 Low delay B  
               
               
                   
                 Over VTM-4.0 w/ IBC on  
               
            
           
           
               
               
               
               
               
               
            
               
                   
                 Y  
                 U  
                 V  
                 EncT  
                 DecT 
               
               
                   
               
               
                 Class A1  
                   
                   
                   
                   
                   
               
               
                 Class A2  
                   
                   
                   
                   
                   
               
               
                 Class B  
                 0.00%  
                 0.04%  
                 −0.14%  
                 113%  
                 #NUM! 
               
               
                 Class C  
                 −0.05%  
                 −0.28%  
                 −0.15%  
                 119%  
                 98%  
               
               
                 Class E  
                 0.04%  
                 −0.16%  
                 0.43%  
                 107%  
                 #NUM! 
               
               
                 Overall  
                 0.00%  
                 −0.11%  
                 0.00%  
                 113%  
                 #NUM! 
               
               
                 Class D  
                 −0.07%  
                 1.14%  
                 0.13%  
                 122%  
                 99%  
               
               
                 Class F  
                 −0.81%  
                 −0.92%  
                 −0.96%  
                 111%  
                 99%  
               
               
                 4:2:0 TGM  
                 −1.71%  
                 −1.67%  
                 −1.71%  
                 106%  
                 95% 
               
               
                   
               
            
           
         
       
     
       FIG.  17    is a block diagram showing an example video processing system  1700  in which various embodiments disclosed herein may be implemented. Various embodiments may include some or all of the components of the system  1700 . The system  1700  may include input  1702  for receiving video content. The video content may be received in a raw or uncompressed format, e.g., 8 or 10 bit multi-component pixel values, or may be in a compressed or encoded format. The input  1702  may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interface include wired interfaces such as Ethernet, passive optical network (PON), etc., and wireless interfaces such as Wi-Fi or cellular interfaces. 
     The system  1700  may include a coding component  1704  that may implement the various coding or encoding methods described in the present disclosure. The coding component  1704  may reduce the average bitrate of video from the input  1702  to the output of the coding component  1704  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  1704  may be either stored, or transmitted via a communication connected, as represented by the component  1706 . The stored or communicated bitstream (or coded) representation of the video received at the input  1702  may be used by the component  1708  for generating pixel values or displayable video that is sent to a display interface  1710 . 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 serial advanced technology attachment (SATA), peripheral component interface (PCI), integrated drive electronics (IDE) interface, and the like. The embodiments described in the present disclosure 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. 
       FIG.  18    is a flowchart of an example method  1800  of visual data processing. Steps of this flowchart are discussed in connection with example 23 discussed in Section 4 of this disclosure. At step  1802 , the process determines, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the current video block, a block vector (BVx,BVy), wherein validity of the block vector (BVx, BVy) is independent of (1) a location (P, Q) of a sample block and/or (2) whether a sample at the location (P,Q) is reconstructed, and/or (3) a location of the current video block, wherein, the block vector (BVx, BVy) represents a pixel displacement between the current video block and the sample block. At step  1804 , the process performs, using the block vector, the conversion in an intra block copy mode which is based on a reconstructed block located in same video region with the current video block comprising reference samples used for deriving a prediction block of the current video block, wherein, during the conversion, a prediction sample with a location (A, B) from reference samples in a buffer is determined at least according to a size of the buffer and/or the block vector (BVx, BVy). 
       FIG.  19    is a flowchart of an example method  1900  of visual data processing. Steps of this flowchart are discussed in connection with example 23 discussed in Section 4 of this disclosure. At step  1902 , the process determines, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, whether a block vector (BVx, BVy) corresponding to the current video block is valid according to a rule, wherein the block vector (BVx, BVy) represents a pixel displacement between the current video block and a sample block. At step  1904 , the process performs, using the block vector, the conversion based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, wherein the rule specifies that the block vector (BVx, BVy) is valid in case that (1) one or more samples from the sample block are outside the current picture and/or (2) one or more samples from the sample block are outside at least one coding tree unit (CTU) associated with the current video block, and/or (3) one or more samples from the sample block fail to be reconstructed. 
       FIG.  20    is a flowchart of an example method  2000  of visual data processing. Steps of this flowchart are discussed in connection with example 44 discussed in Section 4 of this disclosure. At step  2002 , the process performs a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, wherein, the conversion is based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, and wherein a virtual buffer of a defined size is used for tracking availability of the reference samples for deriving the prediction block. 
       FIG.  21    is a flowchart of an example method  2100  of visual data processing. Steps of this flowchart are discussed in connection with example 51 discussed in Section 4 of this disclosure. At step  2102 , the process maintains, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, a buffer comprising reference samples from the current picture for a derivation of a prediction block of the current video block, wherein one or more reference samples in the buffer that are marked unavailable for the derivation have values outside of a pixel value range. 
       FIG.  22    is a flowchart of an example method  2200  of visual data processing. Steps of this flowchart are discussed in connection with example 54 discussed in Section 4 of this disclosure. At step  2202 , the process performs a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data using a buffer comprising reference samples from the current picture for derivation of a prediction block of the current video block, wherein the conversion is based according to rule which specifies that, for the bitstream representation to conform the rule, a reference sample in the buffer is to satisfy a bitstream conformance constraint. 
     Some embodiments of the present disclosure are now presented in clause-based format. 
     L1. A visual media processing method, comprising: 
     determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the current video block, a block vector (BVx,BVy), wherein validity of the block vector (BVx, BVy) is independent of (1) a location (P, Q) of a sample block and/or (2) whether a sample at the location (P,Q) is reconstructed, and/or (3) a location of the current video block, wherein, the block vector (BVx, BVy) represents a pixel displacement between the current video block and the sample block; and 
     performing, using the block vector, the conversion in an intra block copy mode which is based on a reconstructed block located in same video region with the current video block comprising reference samples used for deriving a prediction block of the current video block, wherein, during the conversion, a prediction sample with a location (A, B) from reference samples in a buffer is determined at least according to a size of the buffer and/or the block vector (BVx, BVy). 
     L2. A visual media processing method, comprising: 
     determining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, whether a block vector (BVx, BVy) corresponding to the current video block is valid according to a rule, wherein the block vector (BVx, BVy) represents a pixel displacement between the current video block and a sample block; and 
     performing, using the block vector, the conversion based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, wherein the rule specifies that the block vector (BVx, BVy) is valid in case that (1) one or more samples from the sample block are outside the current picture and/or (2) one or more samples from the sample block are outside at least one coding tree unit (CTU) associated with the current video block, and/or (3) one or more samples from the sample block fail to be reconstructed. 
     L3. The method of clause L2, wherein, upon identifying that the block vector (BVx, BVy) is valid, a prediction sample with a location (A, B) from reference samples in a buffer is determined at least according to a size of the buffer and/or the block vector (BVx, BVy). 
     L4. The method of any one or more of clauses L1 or L3, wherein the reference samples in the buffer corresponds to reconstructed samples of a region of the current picture. 
     L5. The method of clause L4, wherein the region includes a coding tree unit (CTU) row associated with the current video block. 
     L6. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is determined to be valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a boundary of a picture. 
     L7. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether x+BVx&lt;0 or x+BVx&gt;0. 
     L8. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether x+W+BVx&gt;W pic  or x+W+BVx&lt;W pic , where W denotes a width of the current video block and W pic  denotes a width of the picture. 
     L9. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether y+BVy&lt;0 or y+BVy&gt;0. 
     L10. The method of clause L6, wherein the block vector (BVx, BVy) is valid regardless of whether x+H+BVx &gt;H pic  or x+H+BVx&lt;H pic , where H denotes a height of the current video block and H pic  denotes a height of the picture. 
     L11. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a coding tree unit including the current video block. 
     L12. The method of clause L11, wherein the block vector (BVx, BVy) is valid regardless of whether y+BVy&lt;floor(y/H ctu )*H ctu  or y+BVy&gt;floor(y/H ctu )*H ctu , where H ctu  denotes a height of the coding tree unit and floor(a) is the largest integer no greater than a. 
     L13. The method of clause L11, wherein the block vector (BVx, BVy) is valid regardless of whether y+H+BVy&lt;floor(y/H ctu )*H ctu  or y+H+BVy&gt;floor(y/H ctu )*H ctu , where H denotes a height of the current video block, H ctu  denotes a height of the coding tree unit, and floor(a) is the largest integer no greater than a. 
     L14. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a coding tree unit including the current video block and (n−1) coding tree units along a left direction. 
     L15. The method of clause L14, wherein the block vector (BVx, BVy) is valid regardless of whether x+BVx&lt;floor(x/W ctu )*W ctu −(n−1)*W ctu  or x+BVx&gt;floor(X/W ctu )*W ctu −(n−1)*W ctu , where W ctu  denotes a weight of the coding tree unit and floor(a) is the largest integer no greater than a. 
     L16. The method of clause L14, wherein the block vector (BVx, BVy) is valid regardless of whether x+W+BVx&gt;floor(X/W ctu )*W ctu +W ctu  or x+W+BVx&lt;floor(X/W ctu )*W ctu +W ctu , where W denotes a width of the current video block, W ctu  denotes a weight of the coding tree unit, and floor(a) is the largest integer no greater than a. 
     L17. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is valid regardless of whether the location (P, Q) computed according to the block vector (BVx, BVy) and the upper-left position (x, y) of the current video block is outside a current CTU row including a current coding tree unit including the current video block. 
     L18. The method of clause L17, wherein the block vector (BVx, BVy) is valid regardless of whether Y+BVy&lt;floor(Y/Hctu)*Hctu or Y+H+BVy&gt;=floor(Y/Hctu)*Hctu+Hctu, wherein, W ctu  and H ctu  denote a width and height of a CTU respectively and floor(a) is the largest integer no greater than a. 
     L19. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is determined to be valid regardless of whether a sample fails to be reconstructed. 
     L20. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx, y+BVy) is false, where isRec(x,y) is true if pixel (x,y) is reconstructed by an intra block copy mode. 
     L21. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx+W−1, y+BVy) is false, where isRec(x,y) is true if pixel (x, y) is reconstructed by an intra block copy mode and W denotes a width of the current video block. 
     L22. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx, y+BVy+H−1) is false, where isRec(x,y) is true if pixel (x, y) is reconstructed by an intra block copy mode and H denotes a height of the current video block. 
     L23. The method of clause L19, wherein the block vector (BVx, BVy) is valid regardless of whether isRec(x+BVx+W-1, y+BVy+H-1) is false, where isRec(x, y) is true if pixel (x, y) is reconstructed by an intra block copy mode, W denotes a width of the current video block, and H denotes a height of the current video block. 
     L24. The method of any one or more of clauses L1-L5 wherein the block vector (BVx, BVy) is determined to be valid regardless of whether the current video block is included in a first coding tree unit of a coding tree unit row. 
     L25. The method of any one or more of clauses L1-L5, wherein the block vector (BVx, BVy) is determined to be valid when all the following conditions are satisfied: (i) x+BVx&gt;=0, (ii) y+BVy&gt;=floor(y/Hctu), and (iii) isRec(x+BVx+W−1, y+BVy+H−1) is true, where isRec(x, y) is true if sample (x, y) is reconstructed by an intra block copy mode, W denotes a width of the current video block, H denotes a height of the current video block, where floor(a) is the largest integer no greater than a. 
     L26. The method of clause L25, wherein the block vector is a located in a first CTU in a CTU row. 
     L27. The method of clause L3, wherein the prediction sample with the location (A, B) is determined according to the size of the buffer, the block vector (BVx, BVy), and the upper-left position (x,y). 
     L28. The method of clause L27, wherein the prediction sample with the location (A, B) comprises a predication sample with a location computed according to ((X+BVx)%Wbuf, (Y+BVy)%Hbuf), wherein Wbuf and Hbuf denote a width of the buffer and a height of the buffer respectively. 
     L29. The method of any one or more of clauses L1-L28, wherein the conversion is performed in an intra block copy mode. 
     M1. A visual media processing method, comprising: 
     performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, 
     wherein, the conversion is based on a reference region from the current picture comprising reference samples used for deriving a prediction block of the current video block, and 
     wherein a virtual buffer of a defined size is used for tracking availability of the reference samples for deriving the prediction block. 
     M2. The method of clause M1, wherein the virtual buffer is maintained using a virtual pipeline data unit (VPDU), and wherein a size of the virtual buffer is m*W VPDU ×n*H VPDU , where W VPDU  and H VPDU  denote a width and a height of the VPDU. 
     M3. The method of clause M2, wherein m=4 and n=2. 
     M4. The method of clause M2, wherein m and/or n are based at least in part on a resolution of a picture associated with the current video block or a size of a coding tree unit including the current video block. 
     M5. The method of clause M2, wherein m and/or are predefined quantities. 
     M6. The method of clause M2, wherein m and/or are signalled as fields in the bitstream representation. 
     M7. The method of clause M1, wherein a sample in the current video block is mapped to (x%(m*W VPDU ), y%(n*H VPDU )) in the virtual buffer, where the sample in the current video block is located at (x, y) relative to a upper-left corner of a picture; “x%y” is defined as y=x−y*floor(x/y), where floor(a) is the largest integer no greater than a, and W VPDU  and H VPDU  denote a width and a height of the VPDU. 
     M8. The method of clause M1, further comprising: 
     using an array for tracking availabilities of samples stored in the virtual buffer. 
     M9. The method of clause M8, wherein the array includes a flag to indicate if one or more samples stored in the buffer are used for prediction in an intra block copy mode. 
     M10. The method of clause M8, wherein the array corresponds to one or more VPDUs of size 3×2. 
     M11. The method of clause M8, wherein the array corresponds to one or more VPDUs of size 4×2. 
     M12. The method of clause M1, wherein a subset of samples stored in the virtual buffer are flagged as unavailable for prediction. 
     M13. The method of clause M12, wherein, the subset of samples flagged as unavailable for prediction are based on a position of a most-recently processed VPDU. 
     M14. The method of clause M13, wherein the samples are flagged as unavailable at a beginning of processing a VPDU. 
     M15. The method of clause M14, wherein, if yPrevVPDU%(n*H VPDU ) is equal to 0, then the subset of samples located at positions (x, y) are flagged as unavailable, wherein x lies in a first predetermined range and y lies in a second predetermined range, where (xPrevVPDU, yPrevVPDU) denotes an upper-left corner of a coding tree unit of a most-recently processed VPDU, and W VPDU  and H VPDU  denote a width and a height of the VPDU. 
     M16. The method of clause M15, wherein the first range is expressed as [xPrevVPDU−2W VPDU +2mW VPDU )%mW VPDU , ((xPrevVPDU−2*W VPDU +2*m*W VPDU )%(m*W VPDU )−1+W VPDU ] and the second range is expressed as [yPrevVPDU%(n*H VPDU ), (yPrevVPDU%(n*H VPDU ))−1+H VPDU ]. 
     M17. The method of clause M15, wherein the first range is expressed as [xPrevVPDU−2*W VPDU +2*m*W VPDU )%mW VPDU , ((xPrevVPDU−2*W VPDU +2*m*W VPDU )%(m*W VPDU )−1+W VPDU ] and the second range is expressed as [yPrevVPDU%(n*H VPDU ), (yPrevVPDU%(n*H VPDU ))−1+H VPDU ]. 
     M18. The method of clause M14, wherein, if yPrevVPDU%(n*H VPDU ) is not equal to 0, then the subset of samples located at positions (x, y) are flagged as unavailable, wherein x lies in a first predetermined range and y lies in a second predetermined range, where (xPrevVPDU, yPrevVPDU) denotes an upper-left corner of a coding tree unit of a most-recently processed VPDU, and W VPDU  and H VPDU  denote a width and a height of the VPDU. 
     M19. The method of clause M18, wherein the first range is expressed as [xPrevVPDU−W VPDU +2*m*W VPDU )%(m*W VPDU ), ((xPrevVPDU−W VPDU +2*m*W VPDU )%(m*W VPDU )−1+W VPDU ] and the second range is expressed as [yPrevVPDU%(n*H VPDU ), (yPrevVPDU%(n*H VPDU ))−1+H VPDU ]. 
     M20. The method of clause M18, wherein the first range is expressed as [xPrevVPDU−W VPDU +2*m*W VPDU )%mW VPDU , ((xPrevVPDU−W VPDU +2*m*W VPDU )%(m*W VPDU ))−1+W VPDU ] and the second range is expressed as [yPrevVPDU%(n*H VPDU ), (yPrevVPDU%(n*H VPDU ))−1+H VPDU ]. 
     M21. The method of clause M12, wherein, when the coding tree includes VPDUs, the subset of samples flagged as unavailable for prediction are based on a position of a most-recently processed coding tree unit. 
     M22. The method of clause M21, wherein the samples are flagged as unavailable at a beginning of processing a coding tree unit. 
     M23. The method of any one or more of clauses M1 -M22, further comprising: 
     determining validity of a block vector corresponding to the current video block based on an upper-left position of the current video block, a bottom-left position of the current video block, and a bottom-right position of the current video block, wherein the determining excludes use of an upper-right position of the current video block. 
     M24. The method of any one or more of clauses M 1 -M23, wherein the conversion is performed in an intra block copy mode. 
     N1. A visual media processing method, comprising: 
     maintaining, for a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data, a buffer comprising reference samples from the current picture for a derivation of a prediction block of the current video block, 
     wherein one or more reference samples in the buffer that are marked unavailable for the derivation have values outside of a pixel value range. 
     N2. The method of clause N1, wherein the pixel value range is expressed as [0, 1&lt;&lt;(bit_depth)−1], where bit_depth is a positive integer. 
     N3. The method of clause N2, wherein bit_depth is a precision used for processing the sample. 
     N4. The method of clause N1, wherein the method further comprises: 
     initializing a set of samples in the buffer to a predetermined value indicative of unavailability of the set of samples. 
     N5. The method of clause N4, wherein the predetermined value is −1. 
     N6. The method of any one or more of clauses N4-N5, wherein locations of the set of samples and/or whether to initialize the set of the samples to the predetermined value is/are based on one or more of: a position of the current video block, a size of the current video block, a size of a VPDU including the current video block, and/or a size of a coding tree unit including the current video block. 
     N7. The method of clause N6, wherein, if (xCb%vSize) is equal to 0 and (yCb%vSize) is equal to 0, the set of samples are marked as unavailable, where xCb, yCb denote a position of the current video block relative to the sample and vSize=min(ctbSize, 64), where ctbSize denotes a width or a height of the coding tree unit. 
     N8. The method of clause N1, wherein, if a size of the current video block is less than min(ctbSize, 64), the set of samples in the buffer are marked unavailable, where ctbSize denotes a width or a height of the coding tree unit. 
     N9. The method of clause N8, wherein locations of the plurality of samples are related to a size of a VPDU. 
     N10. The method of clause N8, wherein locations of the set of samples are related to a size of the coding tree unit including the current video block. 
     N11. The method of clause N4, wherein the set of samples in the buffer have with positions expressed as (x%wIbcBuf, y%hIbcBuf), where x=xV, . . . , xV+ctbSize−1 and y=yV, . . . , yV+ctbSize−1, and xV, yV denote the upper-left position of a VPDU relative to an upper-left position of a picture, where ctbSize denotes a size of the coding tree unit including the current video block, and wIbcBuf and hIbcBuf denote a buffer width and a buffer height. 
     N12. The method of clause N11, wherein the set of samples in the buffer are initialized to −1. 
     N13. The method of clause N4, wherein the set of samples are initialized at a beginning of decoding a video unit. 
     N14. The method of any one or more of clauses N1-N13, wherein the conversion is performed in an intra block copy mode. 
     O1. A visual media processing method, comprising: 
     performing a conversion between a current video block of a current picture of a visual media data and a bitstream representation of the visual media data using a buffer comprising reference samples from the current picture for derivation of a prediction block of the current video block, 
     wherein the conversion is based according to rule which specifies that, for the bitstream representation to conform the rule, a reference sample in the buffer is to satisfy a bitstream conformance constraint. 
     O2. The method of clause O1, wherein the bitstream conformance constraint is based on at least one of (1) a value of the reference sample in the buffer and/or (2) an availability information of the sample in the buffer. 
     O3. The method of any one or more of clauses O1-O2, wherein the bitstream conformance constraint specifies that the bitstream representation is non-conforming, if the sample in the buffer has a value outside of a pixel range. 
     O4. The method of clause O3, wherein the range is [K0, K1], wherein K0 is set to 0 and K1 is set to (1&lt;&lt;BitDepth−1), where BitDepth represents a precision of a prediction sample. 
     O5. The method of any one or more of clauses O1-O2, wherein the bitstream conformance constraint specifies that the bitstream representation is non-conforming, if the availability information of the sample in the buffer indicates that the sample is unavailable for the current video block. 
     O6. The method of any one or more of clauses O1-O2, wherein the sample is a luma sample, and wherein the bitstream conformance constraint specifies that the bitstream representation is non-conforming, if the availability information of the sample in the buffer indicates that the sample is unavailable for the current video block and a single tree partitioning is used for the current video block. 
     O7. The method of clause any one or more of clauses O1-O6, further comprising: 
     marking the availability information of the sample according to the value of the sample in the buffer. 
     O8. The method of clause O7, wherein, if the value of the sample lies in an interval denoted as [K0, K1], the availability information of the sample is marked as available. 
     O9. The method of clause O8, wherein K0 is set to 0 and K1 is set to (1&lt;&lt;BitDepth−1), where BitDepth is represents a precision of a prediction sample. 
     O10. The method of any one or more of clauses O1-O8, wherein the bitstream conformance constraint is further based on a partitioning type and a tree type of a coding unit associated with the current video block. 
     O11. The method of clause O10, wherein, if the partitioning type is dual tree and the tree type is single tree, then the bitstream conformance constraint specifies checking if all color components of the sample are marked as unavailable. 
     O12. The method of clause O10, wherein if the partitioning type is dual tree and the tree type is dual tree, then the bitstream conformance constraint specifies excludes checking if a chroma component of the sample is marked as unavailable. 
     O13. The method of any one or more of clauses O1-O12, wherein the conversion is performed in an intra block copy mode. 
     O14. The method of any of clauses L1-O13, wherein the conversion includes generating the bitstream representation from the current video block. 
     O15. The method of any of clauses L1-O13, wherein the conversion includes generating pixel values of the current video block from the bitstream representation. 
     P1. A video encoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses L1-O15. 
     P2. A video decoder apparatus comprising a processor configured to implement a method recited in any one or more of clauses L1-O15. 
     P3. A computer readable medium having code stored thereon, the code embodying processor-executable instructions for implementing a method recited in any of or more of clauses L1-O15. 
     In the present disclosure, 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. 
     From the foregoing, it will be appreciated that specific embodiments of the present disclosure have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of these embodiments. Accordingly, the present disclosure is not limited except as by the appended claims. 
     Embodiments of the subject matter and the functional operations described in the present disclosure 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. Embodiments 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., a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). 
     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., erasable programmable read-only memory (EPROM), electronically erasable programmable read-only memory (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 the present disclosure 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 the present disclosure 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 the present disclosure should not be understood as requiring such separation in all embodiments. 
     Only a few embodiments and examples are described and other embodiments, enhancements and variations can be made based on what is described and illustrated in the present disclosure.