Hi, I have problems too since the codecparsers get integrated in gstreamer-vaapi. For example, if I try to play a MPEG-4 (Divx) file I get a crash: libva: va_openDriver() returns 0 *** stack smashing detected ***: gstpenang terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x55)[0xb64db3d5] /lib/libc.so.6(+0x11737b)[0xb64db37b] /usr/lib/gstreamer-0.10/libgstvideoparsersbad.so(+0x132e5)[0xb14592e5] /usr/lib/gstreamer-0.10/libgstvideoparsersbad.so(+0x8ae7)[0xb144eae7] /usr/lib/gstreamer-0.10/libgstvideoparsersbad.so(+0xb152)[0xb1451152] /usr/lib/libgstbase-0.10.so.0(+0xcdb1)[0xb4be8db1] /usr/lib/libgstreamer-0.10.so.0(gst_pad_set_caps+0x1ac)[0xb77a5c2c] /usr/lib/libgstreamer-0.10.so.0(+0x1aea0)[0xb776aea0] /usr/lib/libgstreamer-0.10.so.0(+0x56fc4)[0xb77a6fc4] /usr/lib/libgstreamer-0.10.so.0(+0x57925)[0xb77a7925] /usr/lib/libgstreamer-0.10.so.0(gst_pad_push+0x158)[0xb77aabf8] /usr/lib/gstreamer-0.10/libgstcoreelements.so(+0x21a04)[0xb49eda04] /usr/lib/libgstreamer-0.10.so.0(+0x85c62)[0xb77d5c62] /usr/lib/libgstreamer-0.10.so.0(+0x87009)[0xb77d7009] <div class="gmail_extra"> <div class="gmail_quote">On 10 December 2012 18:33, Beauchesne, Gwenole <<a href="mailto:gwenole.beauchesne@intel.com" target="_blank">gwenole.beauchesne@intel.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, gst-vaapi pulls in newer code from gst-plugins-bad master, not 0.10 as features and more important bug fixes that may break compatibility happen there. gst-vaapi codecparsers will live forever for 0.10 based branches, and will be removed for 1.x integration. Please try the attached patch. Thanks, Gwenole. ________________________________________ From: Yuan, Feng Sent: 10 December 2012 09:17 To: Beauchesne, Gwenole Cc: <a href="mailto:libva@lists.freedesktop.org">libva@lists.freedesktop.org</a>; Li, Jocelyn; Zhong, CongX Subject: codec parser issues between gst-plugins-bad and gstreamer-vaapi <div class="HOEnZb"><div class="h5"> Hi Gwenole, We saw codec parser moved into gstreamer-vaapi as a submodule for a few weeks. PRC QA team reported some bugs of playbin2 errors but manual pipeline works good. e.g. <a href="https://bugs.freedesktop.org/show_bug.cgi?id=55305" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=55305</a>. After Cong tracked this bug, he found the issue was caused by codec parser which may get confused when APIs exist both in gst-plugins-bad and gst-vaapi. Plugin <h264parse>, which is a gst-plugins-bad element, it calls API *gst_h264_parser_parse_sps* in gsth264parser.c to parse SPS data which should be in libgstcodecparser.so. The problem is that this API also exist in gstream-vaapi as submodule which was a built-in in <a href="http://libgstvaapi-0.10.so" target="_blank">libgstvaapi-0.10.so</a>. This API may get unexpected result since *GstH264SPS* has different definitions between gst-plugins-bad and gstreamer-vaapi. This issue blocked us, it seems we have to rebuild gst-plugins-bad every time by force copy codec-parser from gst-vaapi to gst-plugins-bad. Do you have any better idea to solve this issue? BTW, Why codec-parser was moved into gst-vaapi?Is it the reason that gst-plugins-bad accept patches slow or something? How long would codec-parser be in gst-vaapi, Temporally or always? Thanks, Wind </div></div> _______________________________________________ Libva mailing list <a href="mailto:Libva@lists.freedesktop.org">Libva@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/libva" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libva</a> </blockquote></div> -- Javier Jardón Cabezas </div>