Opened 8 years ago
Closed 5 years ago
#21 closed defect (wontfix)
Motion vector overflow problem
| Reported by: | jonatan | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | JEM | Version: | |
| Keywords: | Cc: | ksuehring, XiangLi, jvet@… |
Description
In the JEM encoder there seems to be a problem in that some motion vectors that are evaluated becomes larger than what is possible to represent with "short". This causes an incorrect (overflown) motion vector to be evaluated. It does not seem to create any serious problem in the main branch but in the EE5 branch it currently causes the encoder to crash on some sequences.
To me it seems it would be better to consistently use "int" instead of "short" for the motion vectors so that no overflown motion vectors are evaluated. Making that change might be a better solution than making a local bug fix in the EE5 branch to avoid the crash. But since it is probably a quite substantial modification to the code (changing all motion vector occurrences from "short" to "int") I would like to hear others' opinions and suggestions.
Change history (1)
comment:1 Changed 5 years ago by ksuehring
- Resolution set to wontfix
- Status changed from new to closed
JEM is not maintained anymore. VTM is the currently supported reference software of VVC. If the report is still valid, please re-open and assign to VTM.