#1578 closed defect (fixed)

VTM 18.0 compiled on Linux in debug mode with range extension decodes incorrectly some v2 conformance streams

Reported by: iole_moccagatta Owned by:
Priority: major Milestone: VTM-18.1
Component: VTM Version:
Keywords: Cc: ksuehring, fbossen, iole_moccagatta, vzakharc, yuwenhe, jvet@…

Description

VTM 18.0 compiled on Linux in debug mode with range extension decodes incorrectly 10/128 v2 conformance streams.

These are some incorrectly decoded streams:
12b420vvc1_A_Alibaba_2
16b444errc_A_Qualcomm_2
16b444SPerrc_A_Qualcomm_2
16b444vvc1_A_Alibaba_2

The full list is in the attached log file.

Same when using the latest VTM (89c013aa3ee3638cc5184a30b7db603ef326dd34).

Attachments (1)

VVCv2_list_VTM18.0_v2_debug.txt (115.4 KB) - added by iole_moccagatta 21 months ago.

Download all attachments as: .zip

Change history (4)

Changed 21 months ago by iole_moccagatta

comment:1 Changed 21 months ago by iole_moccagatta

  • Component changed from 360Lib to VTM

this is a VTM bug.

comment:2 Changed 21 months ago by iole_moccagatta

VTM 18.0 with range extension support + https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM/-/merge_requests/2326 decodes correctly all V2 conformance streams.

comment:3 Changed 20 months ago by fbossen

  • Milestone set to VTM-18.1
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.