Hi, 2012/12/10 Yuan, Feng <[email protected]>: > Thanks for your reply. > Will you merge the patch into gst-vaapi?
If you tell me it works, yes. :) Otherwise, I didn't test the patch since I don't have the issue, but I understand the cause based on what you said. Thanks, Gwenole. >> -----Original Message----- >> From: Beauchesne, Gwenole >> Sent: Monday, December 10, 2012 5:34 PM >> To: Yuan, Feng >> Cc: [email protected]; Li, Jocelyn; Zhong, CongX >> Subject: RE: codec parser issues between gst-plugins-bad and gstreamer- >> vaapi >> >> 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: [email protected]; Li, Jocelyn; Zhong, CongX >> Subject: codec parser issues between gst-plugins-bad and gstreamer-vaapi >> >> 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. >> https://bugs.freedesktop.org/show_bug.cgi?id=55305. 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 libgstvaapi-0.10.so. >> 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 > _______________________________________________ > Libva mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/libva _______________________________________________ Libva mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libva
