View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000277 | JVT JM H.264/AVC reference software | decoder | public | 2011-08-17 11:47 | 2011-08-22 18:05 |
| Reporter | Mostafa Shahverdy | Assigned To | Karsten Suehring | ||
| Priority | urgent | Severity | crash | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Product Version | JM 18.0 | ||||
| Summary | 0000277: using RTP mode, when droping some packets with rtp_loss.exe decoder can not decode. | ||||
| Description | I am using this scheme: encoding>>rtp_loss>>decoding encoding goes fine, rtp_loss.exe goes fine too, here it is the output of rtp_loss: $ ./rtp_loss.exe test.264 test2.264 60 3 lost packet 0000004 But the problem is that decoder fails, here is the output: Setting Default Parameters... Parsing Configfile decoder.cfg ............... ----------------------------- JM 18.0 (FRExt) ----------------------------- -------------------------------------------------------------------------- Input H.264 bitstream : test.264 Output decoded YUV : test_dec.yuv Input reference file : test_rec.yuv -------------------------------------------------------------------------- POC must = frame# or field# for SNRs to be correct -------------------------------------------------------------------------- Frame POC Pic# QP SnrY SnrU SnrV Y:U:V Time(ms) -------------------------------------------------------------------------- Warning: RTP sequence number discontinuity detected Segmentation fault in all levels OutFileMode is set to RTP: ********************************************************************* OutFileMode = 1 # Output file mode, 0:Annex B, 1:RTP ********************************************************************* | ||||
| Steps To Reproduce | ./lencode.exe ./rtp_loss.exe test.264 test2.264 60 3 {Then I manualy remove test.264 and rename test2.264 to test.264 :D} ./ldecode.exe config files are attached to this report. | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
I think this is a true bug! This works fine with Jm 16.2. But in JM 18 not :( |
|
|
The error detection loop was broken with the recent MVC dpb changes. JM 17.x might also work. Rewriting the whole logic (including the structure of the decoding loops) is on the todo list for quite a while. Unfortunately I didn't have much time to work on JM recently. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-08-17 11:47 | Mostafa Shahverdy | New Issue | |
| 2011-08-17 11:48 | Mostafa Shahverdy | File Added: config_files.zip | |
| 2011-08-20 15:26 | Mostafa Shahverdy | Note Added: 0000498 | |
| 2011-08-22 18:05 | Karsten Suehring | Note Added: 0000499 | |
| 2011-08-22 18:05 | Karsten Suehring | Assigned To | => Karsten Suehring |
| 2011-08-22 18:05 | Karsten Suehring | Status | new => acknowledged |
