Opened 5 years ago
Closed 5 years ago
#445 closed defect (fixed)
Decoder crashes when the maximum MTT depth is 0
| Reported by: | KuiFan | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | VTM-6.0 |
| Component: | VTM | Version: | VTM-6.0rc1 |
| Keywords: | Cc: | ksuehring, XiangLi, fbossen, jvet@… |
Description
The decoder of the latest VTM-6.0rc1 crashes when one of MaxBTDepth, MaxBTDepthISliceL, and MaxBTDepthISliceC is set to 0 in the encoding configuration.
This is caused by the mismatched maximum BT/TT size when MaxBTDepth is equal to 0.
This issue can be reproduced with the following command lines:
EncoderApp.exe -c encoder_randomaccess_vtm.cfg -i RaceHorses_416x240_30.yuv -wdt 416 -hgt 240 -fr 30 -q 37 -f 2 --MaxBTDepthISliceL=0 DecoderApp.exe -b str.bin -o dec.yuv
Change history (3)
comment:1 follow-up: ↓ 2 Changed 5 years ago by XiangLi
- Version set to VTM-6.0rc1
comment:2 in reply to: ↑ 1 Changed 5 years ago by KuiFan
Replying to XiangLi:
This looks the same issue reported in #425. Could you check whether https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/merge_requests/831 fixes the issue?
Yes, #425 fixes the issue.
comment:3 Changed 5 years ago by XiangLi
- Milestone set to VTM-6.0
- Resolution set to fixed
- Status changed from new to closed
Fixed as suggested.
Note: See TracTickets for help on using tickets.
This looks the same issue reported in #425. Could you check whether https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/merge_requests/831 fixes the issue?