Bug 59540 - [gst-vaapi] Decoding error with BA3_SVA_C.264(Extended profile)
Summary: [gst-vaapi] Decoding error with BA3_SVA_C.264(Extended profile)
Status: VERIFIED WONTFIX
Alias: None
Product: libva
Classification: Unclassified
Component: intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: xiaowei
QA Contact: Sean V Kelley
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-18 03:07 UTC by Du Yan
Modified: 2013-02-18 04:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Du Yan 2013-01-18 03:07:59 UTC
Environment:
----------------------
Platform: IVB HSW
Libva staging:
commit 21649988d6b532cc96f633db017d1e4369f640e9
Intel-driver staging:
commit d206b47a6ac86c089149ecd71b01eea6ebda5796
Gst-vaapi: qa
commit 6672fcd1f74ee62b4e7772b9f5929152058f25ea


Bug Info:
------------------
decoding error with BA3_SVA_C.264

Setting pipeline to PAUSED ...
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /opt/X11R7/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0
Pipeline is PREROLLING ...
ERROR: from element /GstPipeline:pipeline0/GstH264Parse:h264parse0: GStreamer encountered a general stream error.
Additional debug info:
gstbaseparse.c(2890): gst_base_parse_loop (): /GstPipeline:pipeline0/GstH264Parse:h264parse0:
streaming stopped, reason not-supported
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...


Steps:
------------------
1. xinit&
2. gst-launch-0.10 filesrc location=/home/AVC_conformance/Base_Ext_Main_profile/BA3_SVA_C.264 ! h264parse ! vaapidecode ! vaapisink sync=false
Comment 1 xiaowei 2013-01-29 04:46:50 UTC
issue won't fix, H264 extended profile is not supported by driver and gst-vaapi will report this error and return before decoding.


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.