Custom query (96 matches)
Results (19 - 21 of 96)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#98 | fixed | Disabling of depth intra skip | tech | tech |
Description |
The encoder writes the skip_intra_flag syntax element to the bitstream although SkipIntraEnabledFlag is equal to 0. The bug might be fixed by the following replacement in TEncEntropy.cpp (untested): Replace Void TEncEntropy::encodeDIS( TComDataCU* pcCU, UInt uiAbsPartIdx, Bool bRD ) { if ( !pcCU->getSlice()->getIsDepth() ) { return; } with Void TEncEntropy::encodeDIS( TComDataCU* pcCU, UInt uiAbsPartIdx, Bool bRD ) { if( !pcCU->getSlice()->getDepthIntraSkipFlag() ) { return; } |
|||
#75 | fixed | Discrepancy in VSP bi-pred handling | tech | Tomohiro Ikai |
Description |
There seems to be a discrepancy between spec and software. The spec reads that bipred prevention is applied regardless of VSP flag:
refIdxL1 = −1 (I 112) predFlagL1 = 0 (I 113) However, the software (in TDecEntropy.cpp and TEncSearch.cpp)disbles it in the case VSP flag is true as follows. #if H_3D_VSP
->getVSPFlag(uiSubPartIdx) == 0)) #else
#endif We should remove it (spec should be right). In CTC and IBP(with MTK_I0072_IVARP_SCALING_FIX) experiment, there are no differences by this fix. No change is quite natural because VSP PU cannot be bi-prediction in the current specification. If looking at predFlagLXVSP setting logic(See I.8.5.3.2.13 Derivation process for a view synthesis prediction merge candidate), when predFlagL0VSP is 1, predFlagL1VSP cannot be 1. When predFlagL0VSP is 0, the PU is not bi-prediction. The same logic is applied in VSP inhericance case. Lastly, even if VSP was able to be bi-prediction, we should prevent 8x4/4x8 bipred in VSP as well to preserve motion data storing implemenation. |
|||
#23 | fixed | Disparity vector derivation of VSP mode in depth coding | tech | hongbin.liu |
Description |
In section H.8.5.4, NBDV is used to derive an initial disparity vector for both texture and depth. However, in HTM-6.1,NBDV is not called for depth, instead, (0, 0) is always used as an initial disparity vector. As shown in the following codes, in function TComDataCU::getInterMergeCandidates, NBDV is called only when "bNoPdmMerge" is false, and "bNoPdmMerge" is fasle for texture but is true for depth.
#if FCO_DVP_REFINE_C0132_C0170
#endif
#if MERL_VSP_C0152
#endif );
A suggested revision is to change if(!bNoPdmMerge) to if(!bNoPdmMerge | | ( getSlice()->getIsDepth() && getSlice()->getViewId() ) ) |