• Aucun résultat trouvé

Memory bandwidth reduction

Dans le document Td corrigé JCT-VC - ITU pdf (Page 164-168)

JCTVC-I0075 AHG7: A restriction of motion vector for small PU size [T.Chujoh (Toshiba)]

An experimental result of imposing a restriction on motion vectors for small PU sizes is reported. This is to reduce memory bandwidth for motion compensation and does not change any current syntax, semantics or decoding process. The worst cases of memory bandwidth of interpolation process are two-dimensional interpolation positions for both luma and chroma of bi-prediction PU. Therefore, in order to reduce the worst case of memory bandwidth, for example, an encoding method is tested in which at least one motion vector of L0 or L1 is restricted to having an integer position for both luma and chroma. As an experimental result, a loss of coding efficiency of an average of 0.44% was observed and this value is smaller than the result of prohibition of both 4x8 and 8x4 bi-prediction. The worst memory bandwidths of these restrictions are reportedly almost the same. The proponent suggested for this restriction to be applied to levels equal to or higher than 3. No action was taken on this.

JCTVC-I0366 AHG07: Cross-check of a restriction of motion vector for small PU size

(JCTVC-I0075) [T. Ikai (Sharp)]

JCTVC-I0351 AHG7: Motion vector rounding for the worst case bandwidth reduction [V.

Seregin, X. Wang, J. Chen, M. Karczewicz (Qualcomm)]

In this contribution, MV rounding is studied for worst case bandwidth reduction. To address the worst case of 8x4 and 4x8 prediction blocks, vertical MV components of those blocks’ motion vectors are rounded to integer-pel, which reportedly results in 33% reduction of worst-case bandwidth. The impact on coding performance is reportedly about 0.1% loss under four common test configurations.

Additional loss was reported when it is done without syntax change: approximately 1%.

One expert said that the memory bandwidth advantage might be higher in the case of horizontal restriction (due to typical hardware arrangements).

No apparent subjective quality impact was said to be observed.

JCTVC-I0432 Cross verification of motion vector rounding for the worst case bandwidth reduction (JCTVC-I0351) [T. Lee, J. Park (Samsung)] [late]

JCTVC-I0567 Cross-Check of JCTVC-I0351 [A. Saxena, F. Fernandes (Samsung)] [late]

JCTVC-I0107 AHG7: Modification of merge candidate derivation to reduce MC memory bandwidth [K. Kondo, T. Suzuki (Sony), T. Yamamoto (Sharp)]

This contribution proposes to replace the bi-prediction of merge candidates with uni-prediction when the block size is small (e.g. 4x4, 4x8, 8x4 and 8x8). This technique aims to avoid coding efficiency loss by eliminating bi-prediction for small blocks. To restrict bi-prediction and small block is asserted to be a simple way to limit maximum memory bandwidth. When a bi-prediction for a small block is restricted by level, the encoder cannot choose merge candidates for bi-prediction. This makes it difficult to use the merge and skip modes, and introduces coding efficiency loss. This proposal makes it possible to use merge and skip modes by replacing the prediction direction from bi-pred to L0 uni-pred. For the restriction (4x4, bi-pred 4x8, 8x4 and 8x8) case, without the proposed method the BD BR impact is reportedly 1.5, 1.2, 2.1 and 1.7% for RA-Main, RA-HE10, LB-Main and LB-HE10. With the proposed method, the BD BR impact is 1.0, 0.8, 1.1 and 0.9%. It was reported that the coding efficiency can be recovered by this proposal.

The contribution proposed a flag sent in the SPS, and a derivation process of bi-pred merge candidates to be changed in the case of small PUs. The change of merge derivation for specific PU size is reportedly not so nice. The cross-checker (proponent of JCTVC-I0425) said that it would be rather desirable to put the replacement at the end of the derivation process.

JCTVC-I0121 AHG7: Cross-verification of Sony and Sharp proposal JCTVC-I0107 on modification of merge candidate derivation to reduce MC memory bandwidth [M. Zhou (TI)]

JCTVC-I0216 AHG7: Reducing HEVC worst-case memory bandwidth by restricting bi-directional 4x8 and 8x4 prediction units [T. Hellman, W. Wan (Broadcom)]

This proposal recommends adding a profile & level independent limit on the types of motion

compensation prediction units to alleviate worst-case motion compensation memory bandwidth. It says that the present draft of the standard results in worst-case bandwidth that is too high for practical implementations. It notes that the AVC standard has a level limit on the number of motion vectors per

MB pair, but the proposal claims that restricting 4x8 and 8x4 PUs to uni-prediction for all pictures would be a preferred method to address the same concerns for HEVC. The proposal claims luma losses of 0.2–

0.4% for class A and class B sequences, and 0.2–0.8% overall.

It was proposed to remove the 4x4 prediction size enable flag and replace it with a flag that enables the suggested mode, for which the following apply:

 4x8/8x4 are restricted to uni prediction

 merge mode is disable for 8x4 and 4x8

JCTVC-I0120 AHG7: Cross-verification of Broadcom proposal JCTVC-I0216 on

“Reducing HEVC worst-case memory bandwidth by restricting bi-directional 4x8 and 8x4 prediction units” [M. Zhou (TI)]

JCTVC-I0425 AHG7: A combined study on JCTVC-I0216 and JCTVC-I0107 [M. Zhou (TI)]

This contribution reports results of a combined study on JCTVC-I0216 and JCTVC-I0107. It is proposed to combine both solutions for further coding loss reduction. In the proposed combination, 4x4 inter PUs are permanently disabled (as proposed in JCTVC-I0216), 8x4 and 4x8 inter PUs are restricted to have either unidirectional merge mode (as proposed in JCTVC-I0107) or unidirectional predictive mode (as proposed in JCTVC-I0216 and JCTVC-I0107). The inter prediction direction flag is not signalled for 4x8 and 8x4 inter PUs in B-slices (as proposed in JCTVC-I0216), the merge mode signalling remains the same as in HM6.0. The merging candidate list derivation is modified that the bi-predictive merging candidates are converted into list 0 uni-predictive candidates for 8x4 and 4x8 PUs (as proposed in JCTVC-I0107). However, the conversion is performed after the completion of the current HM6.0 merging candidate derivation process to minimize changes to the current design. Experimental results reportedly show that the coding loss of combined design is reduced to 0.3/0.2/0.3/0.3% in RA-Main/RA-HE10/LB-Main/LB-HE10) when compared to the loss of 0.4/0.3/0.6/0.4 in JCTVC-I0216 and 0.4/0.3/0.4/0.3 in JCTVC-I0107.

Changing syntax for inter_pred_flag reportedly gives an benefit of 0.1%

Proponents of I0107 and I0216 agree that this may be an interesting additional operational point for memory bandwidth advantage versus loss in compression.

This keeps the process more consistent than in I0107 over the different PU sizes.

The enabling flag for this mode may be desirable for the purpose of not imposing same restrictions in future profiles. If this scheme is enabled by default in the Main profile, decoders would only need to implement the restricted method.

JCTVC-I0438 AHG7: Cross-check report of A combined study on JCTVC-I0216 and JCTVC-I0107 (JCTVC-I0425) [T. Sugio (Panasonic)] [late]

JCTVC-I0297 AHG7: Bi-pred restriction for small PUs [S. Fukushima, M. Ueda, H.

Takehara (JVC Kenwood)]

This contribution presents a restriction method for bi-prediction motion compensation affecting both the encoder and decoder to reduce the maximum memory bandwidth on decoder.

This contribution presents two methods of bi-prediction restriction with small changes to current HEVC specification. To restrict bi-prediction by the size of PU, bi-prediction motion information is restricted

after derivation of motion information in proposal 1, and bi-prediction motion compensation is restricted in the motion compensation process in proposal 2.

Simulation results reportedly show that both the proposed methods provide average 0.3% BD-BR loss compared to the HM6.0 anchor under RA and LB conditions in the case of bi-prediction restriction of 4x8/8x4 PU.

It was asked whether solution 2 is simpler to implement.

The proposal was similar to I0425, but also affects AMVP.

JCTVC-I0449 AHG7: Cross verification of bi-pred restriction for small PUs (JCTVC-I0297) [K. Kondo, T. Suzuki (Sony)] [late]

JCTVC-I0106 AHG7: Level definition to limit memory bandwidth of MC [K. Kondo, T.

Suzuki (Sony)]

This contribution proposes to limit the maximum memory bandwidth of motion compensation (MC). The two aspects are proposed to be changed. One of these is to restrict small PU blocks, and another is to limit the number of motion vectors in a LCU. This method was tested in the AVC context. For the small block size restriction, the impact of coding efficiency is shown.

Unfortunately, the restriction brings coding efficiency loss. It is possible to reduce this loss with other techniques (such as JCTVC-I0107).

A level-specific restriction seems to be affecting the compression (as here), or (if imposed by flag) causes decoder complexity increase (by introducing the necessity to implement both modes).

JCTVC-I0558 AHG7: High-level syntax for explicit memory bandwidth restriction [M.

Ueda, S. Fukushima (JVC Kenwood), K. Kondo, T. Suzuki (Sony)] [late]

This contribution presents high-level syntax for memory bandwidth restriction and a restriction method to limit maximum memory bandwidth explicitly.

Simulation results reportedly show that both proposed methods provide average 0.3% / 1.0% / 2.0% BD-BR loss compared to the HM6.0 anchor under RA and LB conditions in the case of restricting 4x8 and 8x4 bi-prediction / 4x8, 8x4 and 8x8 bi-prediction / 4x8, 8x4 PU and 8x8 bi-prediction, respectively.

JCTVC-I0577 AHG7: Cross-verification of JCTVC-I0558 on high-level syntax for explicit memory bandwidth restriction [M. Zhou (TI)] [late]

Overall discussion on memory bandwidth reduction Decision: Remove inter 4x4 disable flag and inter 4x4 mode.

There is a general agreement that restrictions for memory bandwidth reductions are desirable, and that this can be achieved for a reasonable penalty.

A BoG (T Suzuki) was asked to further discuss the proposals and suggest one or two preferred solutions See BoG Report JCTVC-I0584.

5.19 Alternative coding modes

Dans le document Td corrigé JCT-VC - ITU pdf (Page 164-168)