Bug 64629 - lost frames when decoding MR7_BT_B.h264
Summary: lost frames when decoding MR7_BT_B.h264
Status: RESOLVED NOTOURBUG
Alias: None
Product: libva
Classification: Unclassified
Component: intel (show other bugs)
Version: unspecified
Hardware: Other All
: highest blocker
Assignee: Zhong Cong
QA Contact: Ouping Zhang
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-15 10:28 UTC by Zhong Cong
Modified: 2015-11-23 14:02 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Zhong Cong 2013-05-15 10:28:19 UTC
WARN: gst-vaapi lost frames
./MR7_BT_B.h264 0.070016 0.543362 0.398084 0.845141 0.582178 0.873562 60 59 2 Lost_Frames
Comment 1 zhenxiang.li 2013-11-04 09:19:14 UTC
env:
----------------------------------------------------
Libva:          (master)73a11b3e249da35ede92560eb089239252721351
Libva_intel_driver:             (master)01b39f7ef75c028a99a02e98af6ec9ca2a9c6773
Gstreamer10:            (1.0)4e880d4d1e151ea64f83c28b5c3e1bbc06c57903
Gst_plugins_base10:             (1.0)2dd3f028c1e6dea799d7496639f53220818b20b1
Gst_plugins_good10:             (1.0)643d425f51f81b56deec16c01162637546708ee5
Gst_plugins_bad10:              (1.0)0587ab41b4f9979e9cfc11011ed5c970569ee3d3
Gst_plugins_ugly10:             (1.0)c7c911b8320576429e4a4234a1e29ec7436e6814
Gst_plugins_vaapi10:            (master)61bb68a6e3be0752245f0b4157cbdfbbc1a93c41

Gstreamer010:           (0.10)76fc67b18c38e7f6c9cfacc4e4d0ed11d3b2c548
Gst_plugins_base010:            (0.10)1e1e6eaf3f0dd11f6618154d9739cbe3e007d206
Gst_plugins_good010:            (0.10)5af6f5bfb6c3619a9ccc3b1681579aeb90e8b89a
Gst_plugins_bad010:             (0.10)cef47d85294a0dca38631f938b81a3f0dd6891bd
X264:           (master)1ca7bb943d15165a4b9631002a655587d923be63
Gst_plugins_ugly010:            (0.10)5ddd97ff27ffeb03298be3a02ed18e8c2674d365
Gst_plugins_vaapi010:           (0.4)29b25914d9fe1a3ca05f04b406c73c582431caa0

both staging and master libva branch have this problem, and log info is as below:
gst010_decoding:
----------------------------------------------------
0:00:00.282997656 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2303:find_long_term_reference: found no long-term reference picture with LongTermPicNum = 0
0:00:00.283024032 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2506:exec_picture_refs_modification_1: list 0 entry 0 is empty
0:00:00.299724852 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2303:find_long_term_reference: found no long-term reference picture with LongTermPicNum = 0
0:00:00.299738750 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2506:exec_picture_refs_modification_1: list 0 entry 0 is empty
0:00:00.333183494 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2303:find_long_term_reference: found no long-term reference picture with LongTermPicNum = 0
0:00:00.333200343 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2506:exec_picture_refs_modification_1: list 0 entry 1 is empty
0:00:00.416695415 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2287:find_short_term_reference: found no short-term reference picture with PicNum = 7
0:00:00.416711499 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2506:exec_picture_refs_modification_1: list 0 entry 0 is empty
0:00:00.416820047 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2287:find_short_term_reference: found no short-term reference picture with PicNum = 7
0:00:00.416832871 21039      0x143dc50 ERROR                  vaapi gstvaapidecoder_h264.c:2506:exec_picture_refs_modification_1: list 0 entry 1 is empty
vaapisink Current fps: 63.52, Total avg fps: 63.52

gst10_decoding:
------------------------------------------------------
ERROR: from element /GstPipeline:pipeline0/GstH264Parse:h264parse0: GStreamer encountered a general stream error.
Additional debug info:
gstbaseparse.c(3038): gst_base_parse_loop (): /GstPipeline:pipeline0/GstH264Parse:h264parse0:
streaming stopped, reason error
Comment 2 Jocelyn Li 2013-11-04 14:01:19 UTC
Is this for gst-vaapi 0.4 or gst-vaapi 1.0?
Comment 3 Zhong Cong 2013-11-05 01:03:24 UTC
this is for gst-vaapi 0.4, and it's still not fixed. This issue is not so important.
Comment 4 Shuang He 2013-11-05 02:23:07 UTC
According to last paragraph of Comment 1, I would think this bug is for gst-vaapi master
Comment 5 zhenxiang.li 2013-11-05 03:22:53 UTC
It is also for gst-vaapi-master, the dumped .yuv file size is much smaller than the yuv file produced by sw, and then lost frame occured in decoding this file:
gst-launch-1.0 filesrc location=Base_Ext_Main_profile/MR7_BT_B.h264 ! h264parse ! vaapidecode ! vaapisink sync=false

log:
ERROR: from element /GstPipeline:pipeline0/GstH264Parse:h264parse0: GStreamer encountered a general stream error.
Additional debug info:
gstbaseparse.c(3038): gst_base_parse_loop (): /GstPipeline:pipeline0/GstH264Parse:h264parse0:
streaming stopped, reason error
Comment 6 Adrien SCH. 2014-04-30 08:20:48 UTC
"This issue is not so important." !! What about network sources ? This behavior an happen a lot of times!
Comment 7 janardana 2015-09-27 05:05:39 UTC
I am also hitting same issue with below pipeline : 


GST_DEBUG=3 gst-launch-1.0 flvmux name=mux streamable=true ! rtmpsink sync=true location="rtmp://xxxxxxx" rtspsrc location="rtsp://admin:admin@192.168.0.162:554/cam/realmonitor?channel=1&subtype=0"   ! rtph264depay ! queue ! h264parse ! vaapidecode ! queue ! vaapiencode_h264 rate-control=cbr tune=high-compression ! mux.



How can it be "not so important" ? I am seeing this issue every few mins when decoding video from my ip camera.
Comment 8 haihao 2015-11-23 14:02:54 UTC
This is a gst-vaapi related bug, please try the latest gst-vaapi. If you still experience this issue, please file a new bug against https://bugzilla.gnome.org/enter_bug.cgi?product=gstreamer-vaapi


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.