Opened 4 years ago
Closed 4 years ago
#1293 closed defect (fixed)
availability flags availableFlagConstK are not initialized
| Reported by: | chhuanb | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | spec | Version: | |
| Keywords: | Cc: | ksuehring, bbross, XiangLi, fbossen, jvet@… |
Description
Availability flags availableFlagConstK are not initialized in 8.5.5.6 and may be used with a undefined value in 8.5.5.2.
Besides, a typo was found in the output process.
Suggest fix:
8.5.5.6 Derivation process for constructed affine control point motion vector merging candidates
Inputs to this process are:
–
Output of this process are:
– the availability flags of the constructed affine control point motion vector merging candidiates availableFlagConstK, with K = 1..6,
– ...
The availability flags of the constructed affine control point motion vector merging candidiates availableFlagConstK, with K = 1..6 are initialized to be equal to zero.
The first (top-left) control point motion vector cpMvLXCorner[ 0 ] ...
Change history (1)
comment:1 Changed 4 years ago by jlchen
- Resolution set to fixed
- Status changed from new to closed
Good catch! I think the fixes are valid, and will be fixed in S2001-vH release.
The initialization process will be added as follows:
The availability flags of the constructed affine control point motion vector merging candidates availableFlagConstK, with K = 1..6 are initialized to be equal to FALSE.