In the current HTM, motion/disparity vectors are clipped before storing them in some cases although they should be clipped before generating prediction signals. In other words, motion/disparity vectors in the motion storage should not be clipped.

At least, I found such wrong clippings in TComDataCU::xAddVspCand, TComDataCU::xAddIvMRGCand, TComDataCU::xGetInterMergeCandidates (6 places), TComDataCU::getDisMvpCandNBDV (2 places), TComDataCU::estimateDVFromDM, TComDataCU::xCheckSpatialNBDV, TComDataCU::getInterViewMergeCands (3 places). After removing these clipping, it becomes necessary to add clipping in TComPrediction::xPredInterUniARP since NBDV becomes a non-clipped vector.