Typo in input cpIdx range in subclause 8.5.5.1

[chhuanb]

The input cpIdx range to subclause 8.5.5.9 is 0..2 in subclause 8.5.5.1. It should be changed to 0..numCpMv-1.

Modification as follow:

– For xSbIdx = 0..numSbX − 1, ySbIdx = 0..numSbY − 1, the following applies:
predFlagLX[ xSbIdx ][ ySbIdx ] = predFlagLX[ 0 ][ 0 ] (661)
– When predFlagLX[ 0 ][ 0 ] is equal to 1, the derivation process for motion vector arrays from affine control point motion vectors as specified in subclause 8.5.5.9 is invoked with the luma coding block location ( xCb, yCb ), the luma coding block width cbWidth, the luma prediction block height cbHeight, the number of control point motion vectors numCpMv, the control point motion vectors cpMvLX[ cpIdx ] with cpIdx being 0..2numCpMv − 1, the reference index refIdxLX and the number of luma coding subblocks in horizontal direction numSbX and in vertical direction numSbY as inputs, the luma motion vector array mvLX[ xSbIdx ][ ySbIdx ], the chroma motion vector array mvCLX[ xSbIdx ][ ySbIdx ] with xSbIdx = 0..numSbX − 1, ySbIdx = 0 .. numSbY − 1, the prediction refinement utility flag cbProfFlagLX, and motion vector difference array diffMvLX[ xIdx ][ yIdx ] with xIdx = 0..cbWidth / numSbX − 1, yIdx = 0 .. cbHeight / numSbY − 1 as outputs.

[jlchen]

Good catch! will be included in JVET-S001-vE release.