GNOME Bugzilla – Bug 738677
Seeking failure while using navseek in pipeline
Last modified: 2015-02-25 18:25:55 UTC
The pipeline with navseek element is failing to seek. How to reproduce: gst-launch-1.0 filesrc location=sample ! demuxer ! parser ! vaapidecode ! navseek ! vaapisink Use left/right arrows to seek the video. Pipeline will fail in the first seek itself with the following error: 0:00:00.665635553 10894 0x1c04b70 ERROR vaapidecode gstvaapidecode.c:806:gst_vaapidecode_parse_frame: parse error -1 0:00:00.698381311 10894 0x1c04b70 ERROR vaapidecode gstvaapidecode.c:806:gst_vaapidecode_parse_frame: parse error -1 ERROR: from element /GstPipeline:pipeline0/GstVaapiDecode:vaapidecode0: No valid frames decoded before end of stream The software decode+render pipeline is working fine. Note: Test applications are working fine with seek , this issue is only reproducible while using navseek. So just keeping Severity as "normal" for now.
I have tested current master gstreamer-vaapi (gst-1.5, master too) and it works fine. I tested it with a custom gst-launch-1.0 and also with gst-play-1.0 --videosink="navseek ! vaapisink" I found also that clutterautovideosink ignores the messages from navseek, but glimagesink works fine as vaapisink (except where the GLTextureUploadMeta is negotiated).
This get fixed as a side effect of commit 82e12a933e5a10443e30ee044b28f439480065bc commit 7ca05917591b3477a7d68a1e5adc308737b9e3e0 :) lets close this., Thanks
Well, actually :S It works mostly *excepting* 'r' for reverse playback. But let's keep track of that on bug 742922