Custom query (96 matches)
Results (94 - 96 of 96)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#80 | fixed | Inconsistency of signaling condition for depth_dc_sign_flag between WD and HTM-12.0 | tech | tsukuba.takeshi |
Description |
In I.7.3.8.5.2 Coding unit extension syntax, depth_dc_sign_flag is signaled when depth_dc_abs[x0+k][y0+j][i] is greater than 0 as follows:
On the other hand,in HTM-12.0, it is signaled when the absolute value of DcOffset is greater than 0 as follows: Void TDecSbac::xParseDimDeltaDC( Pel& rValDeltaDC, UInt uiNumSeg ) {
} Signaling condition for depth_dc_sign_flag in WD should be aligned with HTM-12.0 as follows:
|
|||
#72 | fixed | Bi-prediction disabling for DBBP: A potential bug when the derived direction for merge DBBP is PRED_BI | tech | zxgvideo |
Description |
In the current WD text, I only found the following limitation for the prediction direction of DBBP. I.7.4.9.6 It is a requirement of bitstream conformance that, when dbbp_flag[ x0 ][ y0 ] is equal to 1, inter_pred_idc[ x0 ][ y0 ] shall not be equal to PRED_BI. However, the HTM has forced any inherited bi-prediction MV in DBBP to be forward prediction. I think, a bug-fix should be added on I.8.5.3.2.1, point 14 as following
|
|||
#73 | fixed | A text bug for the post filtering of DBBP | Xianguo Zhang | zxgvideo |
Description |
The current 3D-HEVC text specifies following post filtering conditions for DBBP if( ( lFlag | | cFlag | | rFlag ) && ( !lFlag | | !cFlag | | !rFlag ) )
if( ( tFlag | | cFlag | | bFlag ) && ( !tFlag | | !cFlag | | !bFlag ) )
However, the condition in "if" is opposite to the HTM11.0. It should be changed to if( !(( lFlag | | cFlag | | rFlag ) && ( !lFlag | | !cFlag | | !rFlag ) ) )
if( !(( tFlag | | cFlag | | bFlag ) && ( !tFlag | | !cFlag | | !bFlag) ) )
In further, because the condition in "if" can be simplified, I suggest it is changed to if( lFlag != cFlag | | cFlag != rFlag )
if( tFlag != cFlag | | cFlag != bFlag )
|