Custom query (96 matches)
Results (61 - 63 of 96)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#68 | fixed | MV clipping bug in the sub-PU MPI default MV generation | tech | jicheng |
Description |
In HTM11, there is a MV clipping operation in the sub-PU MPI default MV generation, which is obviously a bug and should be removed to align with the WD. (This kind of bug was previously solved by NTT_BUG_FIX_TK54, but here it is introduced again by MPI_SUBPU_DEFAULT_MV_H0077_H0099_H0111_H0133.) In TComDataCU.cpp, line 4499, the following coded should be removed: clipMv( cMv ); |
|||
#69 | fixed | Missing of DcVal process and unclear DcOffset usage | tech | Tomohiro Ikai |
Description |
In I.8.4.4.3 (I.8.4.4.3 Segmental depth intra coding process) in 3D-HEVC Draft Text 4 (H1001_v2), dcPred is derived but not used. It seems dcPred related process for recSamples is missing. The fix is not clear but the attached H1001_v2_opt1 may help. To me, the DcOffset usage is not clear in the following points. So the editorial improvement and some fix is to be desired. (1) In SDC, DcOffset is not added to predSamples in I.8.4.4.2.9 but it is added in I.8.4.4.3. The reason why we should have two DcOffset related subclause is not clear to me. If we uses I.8.4.4.2.9 in both cases, the text can be much clear (See H1001_v2_opt2) (2) In SDC, the variable DcVal is derived and used. But the derivation of DcVal is not clear. Specifically, When SDC is on, dcOffsetAvailFlag is false. Then DcOffset is not used both in DLT on case and in DLT off case. But when DLT is on, possibly we should add DcOffset before Idx2DepthValue[] (dcOffsetAvail should be true in this part?). (3) DLT handling is separately specified in I.8.4.4.2.9 and I.8.4.4.3. That is difficult to understand so it should be specified either in I.8.4.4.3 or in I.8.4.4.2.9. (4) If predModeIntra is not equal to INTRA_DMM_WFULL or INTRA_DMM_CPREDTEX, dcPred[0] is derived. But it is unclear whther DcOffset should be added in this case. |
|||
#70 | fixed | Inconsistence between HTM and 3D-HEVC text in IvDC pruning | tech | HongbinLiu |
Description |
In derivation process for luma motion vectors for merge mode, pruning of IvDC with A1 and B1 is incosistent between HTM and 3D-HEVC text. In HTM, if A1 or B1 is identical with IVMC (or T), it is marked as unavailable and is not used for pruning with IvDC. However, in the 3D-HEVC text, even in this case, A1 or B1 is still used for purning with IvDC, which is not reasonable and should be aligned with HTM. |