Bug 68307

Summary:	[HSW gst-vaapi-master]File trancoding from Camera JPEG to H.264 failed
Product:	libva	Reporter:	zhenxiang.li <zhenxiang.li>
Component:	intel	Assignee:	Wind Yuan <feng.yuan>
Status:	VERIFIED FIXED	QA Contact:	Sean V Kelley <seanvk>
Severity:	normal
Priority:	medium	CC:	feng.yuan, ouping.zhang, xunx.fang, zhenxiang.li
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description zhenxiang.li 2013-08-20 07:48:32 UTC

Environment:
--------------
Platform: (HSW)
libva: (staging) d540f278465929f3a31030e3f18fdc95ceecffa5
intel-driver: (staging) 42bb613e72d235bcbe141c906dec9431e4c29661
gstreamer: (1.0 ) ce7aef3def12c6b0bbe0c7a0c39f7415d64ad646
gst-base: (1.0) ffc5262119c9277fcc0c5455e0fdc727338ce3a7
gst-bad: (1.0) 61885ba1bcb6f2ff21d3909d83aca46fec3da8d9
gst-good: (1.0) c52279fed1f72fa7d4e18008b490a988ac04b8dd
gst-ugly: (1.0) 3baded20ffcabb9e0077e009bba8002400698271
gst-plugins-vaapi: (master)5142e9e606d7c87fa2c33a60576c3722900fc752

Bug Info:
--------------
File trancoding from Camera JPEG to H.264 failed;
It can create 2.mp4 by executing this command(in steps 3), but the file size is 0 Bytes;

Log details:

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
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstVaapiDecode:vaapidecode0: GStreamer error: negotiation problem.
Additional debug info:
gstvideodecoder.c(1983): gst_video_decoder_chain (): /GstPipeline:pipeline0/GstVaapiDecode:vaapidecode0:
encoder not initialized

** (gst-launch-1.0:16479): CRITICAL **: gst_vaapi_decoder_flush: assertion `decoder != NULL' failed
Execution ended after 1055476072 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Reproduce steps:
--------------
1. xinit &
2. make sure video0 is under the folder dev
3. gst-launch-1.0 v4l2src num-buffers=500 device="/dev/video0" !image/jpeg,width=1280,height=720,framerate=30/1 ! vaapidecode ! vaapiencodeh264 ! qtmux faststart=true ! filesink location=2.mp4

Comment 1 Wind Yuan 2013-08-21 08:31:36 UTC

This bug was already fixed.
please pull the code, and make sure include following 2 commits:
commit 2027173b3f9de3a936b3dc24736bee5628d54b98
Author: Wind Yuan <feng.yuan@intel.com>
Date:   Thu Aug 15 17:59:37 2013 +0800

    jpeg: fix compile miss on va_dec_jpeg.h

commit bf38be076b89f1ce6c92b1eca5853330ae2ef948
Author: Wind Yuan <feng.yuan@intel.com>
Date:   Fri Aug 9 18:40:21 2013 +0800

    h264encoder: add max reflist0/1 count

Comment 2 zhenxiang.li 2013-08-22 01:51:32 UTC

It reproduced, the transcoding on HSW still failed, and the logs included the above two commits.

env:
libva: d540f278465929f3a31030e3f18fdc95ceecffa5
intel-driver: 42bb613e72d235bcbe141c906dec9431e4c29661
Gstreamer:
(1.0)ce7aef3def12c6b0bbe0c7a0c39f7415d64ad646
gst-plugins-base:
(1.0)cd3995640cc91f9502711ac95b9807a1ed6f2759
gst-plugins-bad:
(1.0)61885ba1bcb6f2ff21d3909d83aca46fec3da8d9
gst-plugins-good:
(1.0)c52279fed1f72fa7d4e18008b490a988ac04b8dd
gst-plugins-ugly:
(1.0)3baded20ffcabb9e0077e009bba8002400698271
Gst-vaapi:
(master)6fc31017ef2f86fbfd7b9629064929bdd5025f84

Comment 3 Wind Yuan 2013-08-22 02:29:59 UTC

does the commit_id exactly the same? I have merge a fix into commit bf38be076b89f1ce6c92b1eca5853330ae2ef948
You need to re-pull again.

Comment 4 Wind Yuan 2013-08-22 05:36:57 UTC

It's the jpeg build issue. Just added another patch to fix it.
please update to commit
commit 5c05121a1d90326f3575a2b1e3a0434a90d394e1
Author: Wind Yuan <feng.yuan@intel.com>
Date:   Thu Aug 22 13:03:51 2013 +0800

    jpeg: fix compile flags in jpeg check

Thanks,
Wind

Comment 5 zhenxiang.li 2013-08-23 02:00:25 UTC

No reproduced again, close it!

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.