GNOME Bugzilla – Bug 774182
[MVC][decode] fail to deal alignment as nal.
Last modified: 2017-02-01 17:01:39 UTC
1. Testing Steps: ======================================================================== gst-launch-1.0 -q filesrc location=/media/mvc/MVCDS-1.264 '!' h264parse '!' video/x-h264,stream-format=byte-stream,alignment=nal '!' vaapih264dec '!' vaapipostproc format=i420 deinterlace-mode=disabled '!' videoconvert '!' fdsink 2.Log: ======================================================================== libva info: VA-API version 0.39.4 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_39 libva info: va_openDriver() returns 0 libva info: VA-API version 0.39.4 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_39 libva info: va_openDriver() returns 0 0:00:00.439715983 24695 0x2227d40 ERROR vaapidecode gstvaapidecode.c:1103:gst_vaapidecode_parse_frame: parse error -1 0:00:00.439793564 24695 0x2227d40 ERROR vaapidecode gstvaapidecode.c:1103:gst_vaapidecode_parse_frame: parse error -1 ERROR: from element /GstPipeline:pipeline0/GstVaapiDecode_h264:vaapidecode_h264-0: No valid frames decoded before end of stream Additional debug info: gstvideodecoder.c(1176): gst_video_decoder_sink_event_default (): /GstPipeline:pipeline0/GstVaapiDecode_h264:vaapidecode_h264-0: no valid frames found ERROR: pipeline doesn't want to preroll. 3. Testing Env: ======================================================================== gst_plugins_vaapi: (master)d7231f66ccd7b460c3465c4fdff6694813397114 libva: (master)c4f37b5dc9f092f68a793c52ea169092f0ad6e44 Libva_intel_driver: (master)db93c4020d9b0aca8472f772e91570a641983c66 4. Frequency of Occurence: ======================================================================== 100%
This bug doesn't make much sense for me. The media doesn't have a NAL, and when the parser tries to parse it, it cannot find it, thus it fails. It's like forcing the error. What's the purpose of this test?
(In reply to Víctor Manuel Jáquez Leal from comment #1) > This bug doesn't make much sense for me. > > The media doesn't have a NAL, and when the parser tries to parse it, it > cannot find it, thus it fails. > > It's like forcing the error. > > What's the purpose of this test? @Victor, This test is our bi-weekly test, and we kept testing by using same cmd for a long time. I checked 1.9.2 tag without this error.
(In reply to Víctor Manuel Jáquez Leal from comment #1) > This bug doesn't make much sense for me. > > The media doesn't have a NAL, and when the parser tries to parse it, it > cannot find it, thus it fails. > It should work. It is the duty of h264parse to make nal stream as output if forced. > It's like forcing the error. > > What's the purpose of this test?
This is already fixed on master. The fix for bug 776979 also fixed this issue. I don't feel lent to merge this patch in branch 1.10 since it is a bit risky for a "stable" branch. Thus I'm closing this issue as duplicate. Thanks. *** This bug has been marked as a duplicate of bug 776979 ***