View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000168 | JVT JM H.264/AVC reference software | decoder | public | 2009-03-17 06:20 | 2009-03-17 10:08 |
| Reporter | dannierzhong | Assigned To | |||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | JM 15.1 | ||||
| Summary | 0000168: The decoder always print warning:"warning: zero_byte shall exist" and "duplicate frame_num in short-term reference picture buff" | ||||
| Description | if set intraPeriod = 10, and SliceMode = 1, SliceArgument = 150: the decoder output as below: ----------------------------- JM 15.1 (FRExt) ----------------------------- Decoder config file : decoder.cfg -------------------------------------------------------------------------- Input H.264 bitstream : test.264 Output decoded YUV : test_dec.yuv Output status file : log.dec Input reference file : foreman_cif.yuv -------------------------------------------------------------------------- POC must = frame# or field# for SNRs to be correct -------------------------------------------------------------------------- Frame POC Pic# QP SnrY SnrU SnrV Y:U:V Time(ms) -------------------------------------------------------------------------- 00000(IDR) 0 0 28 38.1581 41.1418 44.2952 4:2:0 133 00002( P ) 4 1 28 37.5254 41.1306 44.1240 4:2:0 177 00001( b ) 2 2 30 37.0817 41.1441 44.3163 4:2:0 153 00004( P ) 8 2 28 37.5341 41.1543 43.7878 4:2:0 182 00003( b ) 6 3 30 36.8764 41.1775 44.0581 4:2:0 166 00006( P ) 12 3 28 37.5392 41.0011 43.8384 4:2:0 177 00005( b ) 10 4 30 36.8332 41.1036 43.9618 4:2:0 142 00008( P ) 16 4 28 37.5799 40.9333 43.8004 4:2:0 180 00007( b ) 14 5 30 36.7428 40.9227 43.8234 4:2:0 152 00010( I ) 20 5 28 12.1205 27.1831 27.4600 4:2:0 36 warning: zero_byte shall exist duplicate frame_num in short-term reference picture buffer Press any key to continue... Attached please find our encoder and decoder config files and test.264( raw yuv: foreman_cif.yuv). | ||||
| Tags | No tags attached. | ||||
|
2009-03-17 06:20
|
|
|
|
Data partitioning seems to be broken in the software. Please set PartitionMode to 0. |
|
|
In the test above, we didn't set the LossRate and RDOptimization = 1(default). We are doing experiments about UEP(Unequal Error Protection) of different Data partition, so Data Partitioning would be neccessary. In addition, we have known in this site that since JM 12.2 fix_v2 version the problem about Data Partition loss error have been fixed. So , does Data Partition broken really? How can I fix the problem without setting PartitionMode to 0? We will be appreciated if Data Partitioning could be supported in JM 15.1 version. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-03-17 06:20 | dannierzhong | New Issue | |
| 2009-03-17 06:20 | dannierzhong | File Added: problem_JM15.1.zip | |
| 2009-03-17 06:58 | Alexis Michael Tourapis | Note Added: 0000302 | |
| 2009-03-17 10:08 | dannierzhong | Note Added: 0000303 | |
| 2009-03-17 10:09 | dannierzhong | Note Edited: 0000303 |
