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.

In HTM 7.0r1, when performing VSO, sometimes distortion value can exceed the range of 32-bit integer.

This problem can be solved by changing the variable type "Dist" from 32-bit integer to 64-bit integer.

The bug-fix provides 0.1% bit-saving for synthesized views.

In H.7.3.4 Slice header syntax,

... else if( layer_id ) {

slice_ic_enable_flag slice_ic_disable_merge_zero_idx_flag

} ...

should be replaced by

... else if( layer_id ) {

slice_ic_enable_flag if( slice_ic_enable_flag ) {

slice_ic_disable_merge_zero_idx_flag

}

} ...

in order to align with the HTM software implementation.