Opened 14 years ago Closed 12 years ago #109 closed defect (fixed)One potential bug may lead to mismatch
Description
At encoder, both skip mode and direct mode are checked in xCheckRDCostSkip(). When the encoder selects the bi-predicted direct mode and this CU has no residue (it will only happen with CABAC, when the encoder thinks this direct mode will cost less bits than skip mode), the variables should be reset as the skip mode. Change History (8)comment:1 follow-up: ↓ 2 Changed 14 years ago by dthoangcomment:2 in reply to: ↑ 1 Changed 14 years ago by dthoang
Replying to dthoang:
Please disregard the above. After debugging, a different cause for mismatch was found. comment:3 follow-up: ↓ 4 Changed 14 years ago by fbossen
Does this still apply to version 3.1? comment:4 in reply to: ↑ 3 Changed 14 years ago by libin
Replying to fbossen:
No, I do not think it still applies to HM-3.1. comment:5 Changed 13 years ago by davidf
Updating component after adding WD (Text) tickets comment:6 Changed 13 years ago by davidf
comment:7 Changed 13 years ago by davidf
comment:8 Changed 12 years ago by ksuehring
looks like this should have been closed already Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber, Participant
|
I am debugging a similar mismatch issue and question why TEncSearch::encodeResAndCalcRdInterCU() takes rpcYuvResiBest as a parameter. This function can modify rpcYuvResiBest but not update the corresponding reconstruction Yuv buffer. This looks like the root cause of this mismatch bug.