Opened 5 years ago

Closed 5 years ago

#726 closed defect (fixed)

Encoder's reconstructed yuv file doesn't match decoder's reconstructed yuv file at rev=ea822544

Reported by: tsukuba.takeshi Owned by:
Priority: minor Milestone: VTM-7.1
Component: VTM Version:
Keywords: Cc: ksuehring, XiangLi, fbossen, jvet@…


MD5 of encoder log matches that of decoder log. However, number of output frames at Encoder does not match decoder's. In addition, MD5 of encoder's reconstructed yuv does not match the decoder's.

For example, when following command is used, number of output frames is 13 while decoder's one is 2.

$./EncoderApp -c encoder_randomaccess_vtm.cfg -q 37 -i RaceHorses_416x240_30.yuv -b str.bin -o rec.yuv --InputBitDepth=8 --InputChromaFormat=420 -fr 30 -wdt 416 -hgt 240 --Level=2.1 -f 2 -fs 0 -ip 32 --SEIDecodedPictureHash=1 --PrintHexPSNR=1

$./DecoderApp -b str.bin -o dec.yuv

rec.yuv's md5sum is : 5889462b0be03be255a441a84b351aec *rec.yuv
dec.yuv's md5sum is : 9e4378e39443426ed40ef962cc883e3d *dec.yuv

Change history (4)

comment:1 Changed 5 years ago by ksuehring

EncApp::xWriteOutput() is trying to write pictures that don't exist.

I traced the issue back to

May be similar to this decoder issue:

comment:2 follow-up: Changed 5 years ago by Vadim

Merge request 1154 may fix this problem.

Can you please try it?

comment:3 in reply to: ↑ 2 Changed 5 years ago by tsukuba.takeshi

Thanks a lot. Fixed encoder generated the same reconstructed file as decoder's at our side.

comment:4 Changed 5 years ago by ksuehring

  • Resolution set to fixed
  • Status changed from new to closed

The MR was merged.

Note: See TracTickets for help on using tickets.