Opened 5 years ago
Last modified 4 years ago
#814 new defect
Encoder/Decoder mismatch found in RA configuration when decoding concatenate bitstreams
| Reported by: | luoda | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | VTM | Version: | VTM-7.1 |
| Keywords: | Cc: | ksuehring, XiangLi, fbossen, jvet@… |
Description
There is no mismatch when decoding Individual bitstreams but mismatches found when decoding concatenated bitstream.
Encoder command line for chunk 0 is:
bin/EncoderAppStatic -c cfg/encoder_randomaccess_vtm.cfg -c cfg/per-sequence/../per-class/classF.cfg -c cfg/per-sequence/../444/yuv444.cfg -c cfg/per-sequence/WebBrowsing_444.cfg --IBC=1 --PLT=1 --BDPCM=2 --HashME=1 --TileUniformSpacing=1 --UniformTileColsWidthMinus1=0 --UniformTileRowHeightMinus1=0 --SEIDecodedPictureHash=1 --PrintHexPSNR=1 --FramesToBeEncoded=33 --IntraPeriod=32 --FrameSkip=0 -q 22 --InputFile=/home/admin/local_sequences/sc_web_browsing_1280x720_30_8bit_300_444_r1.yuv -b WebBrowsing444_QP22_rap0.bin -o
Change history (3)
comment:1 follow-up: ↓ 2 Changed 5 years ago by ksuehring
comment:2 in reply to: ↑ 1 Changed 5 years ago by luoda
Replying to ksuehring:
How were the streams concatenated?
parcat was used to concatenate the bitstreams.
comment:3 Changed 4 years ago by ksuehring
- Milestone VTM-7.1 deleted
How were the streams concatenated?