GNOME Bugzilla – Bug 730047
ERROR: from element /GstPipeline:pipeline0/GstH264Parse:h264parse0: GStreamer encountered a general stream error
Last modified: 2014-05-13 09:05:36 UTC
1. Testing Env: ======================================================================== Libva: (master)0337703ffedc8562299c2d65acfae76c380043c6 Libva_intel_driver: (master)b48ba793b83096be87cc4a1258be80737f26fb3b 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)85a60441fa240a0cf884fcb91bb296636a22efe7 2. Testing Steps: ======================================================================== when running command: "gst-launch-1.0 filesrc location=/root/media_tools/decoder/Base_Ext_Main_profile/HPCAMOLQ_BRCM_B.264 '!' h264parse '!' vaapidecode '!' vaapisink sync=false" following error will arise. error log: ...... Setting pipeline to PAUSED ... Pipeline is PREROLLING ... 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 ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ... 3. Bisect information ======================================================================== regression fail. cannot find this issue on X11R7.stable.2014-05-09. bisect the component and find 85a60441fa240a0cf884fcb91bb296636a22efe7 commit causes this issue commit 85a60441fa240a0cf884fcb91bb296636a22efe7 Author: Gwenole Beauchesne <gwenole.beauchesne@intel.com> AuthorDate: Sat May 10 06:23:29 2014 +0200 Commit: Gwenole Beauchesne <gwenole.beauchesne@intel.com> CommitDate: Sat May 10 06:29:25 2014 +0200 decoder: h264: properly support grayscale formats. Request the correct chroma format for decoding grayscale streams. i.e. make lookups of the VA chroma format more generic, thus possibly supporting more formats in the future. This means that, if a VA driver doesn't support grayscale formats, it is now going to fail. We cannot safely assume that maybe grayscale was implemented on top of some YUV 4:2:0 with the chroma components all set to 0x80. So format(Base_Ext_Main_profile/HPCAMOLQ_BRCM_B.264) should be supported. 4. Frequency of Occurence: ======================================================================== 100%
The VA driver patches have been submitted. I have no intention to keep workarounds in gstreamer-vaapi for driver bugs. Closing as invalid.
you mean that's VA driver issue, right? But i uses mplayer to decode HPCAMOLQ_BRCM_B.264, cannot find this issue. command: "mplayer -nosound -fps 30 -vo vaapi -va vaapi HPCAMOLQ_BRCM_B.264"
I will fix mplayer/ffmpeg too. The current code in VA intel-driver is suboptimal, yet incorrect. If the bitstream is in grayscale format, we have to try and allocate YUV 4:0:0 surfaces instead. There is no need to care about the chroma components.
Understand. So close it as invalid.