View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000206 | JVT JM H.264/AVC reference software | decoder | public | 2010-04-06 09:39 | 2010-05-27 14:03 |
Reporter | xin ni | Assigned To | Karsten Suehring | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | JM-17.0 | ||||
Fixed in Version | JM 17.1 | ||||
Summary | 0000206: misjudgement of a new frame when "p_Vid->active_pps->bottom_field_pic_order_in_frame_present_flag" equal to 1 | ||||
Description | I have tested a stream, it's profile is baseline. in some slices, "p_Vid->active_pps->bottom_field_pic_order_in_frame_present_flag" is equal to 1, so currSlice->delta_pic_order_cnt[1] will have a value not equal to 0. But because JM17 use Slice data structue repeatedly from ppSliceList and doesn't reset delta_pic_order_cnt, so i find a later slice which has bottom_field_pic_order_in_frame_present_flag equal to 0, but still has a delta_pic_order_cnt[1] not equal to 0. This will casue JM17 misjudge a new frame start point in is_new_picture. That is because JM will jugde "(p_old_slice->delta_pic_order_cnt[1] != currSlice->delta_pic_order_cnt[1])". Think of a case that one slice has a non-zero delta_pic_order_cnt[1] while another slice in the same picture has a zero delta_pic_order_cnt[1]. | ||||
Additional Information | I have modified JM17 by adding statement to reset delta_pic_order_cnt before read_new_slice, and it seems to work correctly now. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2010-04-06 09:39 | xin ni | New Issue | |
2010-05-27 14:03 | Karsten Suehring | Note Added: 0000366 | |
2010-05-27 14:03 | Karsten Suehring | Status | new => resolved |
2010-05-27 14:03 | Karsten Suehring | Fixed in Version | => JM 17.0-dev |
2010-05-27 14:03 | Karsten Suehring | Resolution | open => fixed |
2010-05-27 14:03 | Karsten Suehring | Assigned To | => Karsten Suehring |