Bug 68306

Summary: [gst-vaapi-master]File trancoding from Camera JPEG to H.264 failed
Product: libva Reporter: zhenxiang.li <zhenxiang.li>
Component: intelAssignee: 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:42:57 UTC 
Environment:
--------------
Platform: (IVB)
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), the file size is 8492407Bytes;
Nothing on the screen by executing this command(in steps 4).

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
4. gst-launch-1.0 filesrc location=2.mp4 ! qtdemux ! vaapidecode ! vaapisink sync=false
Comment 1 Wind Yuan 2013-08-21 08:27:24 UTC 
The issue has been fixed,Please re-pull the code.
Since I rebased the code and merge the patch with an old one. so please make sure git log contain 

commit bf38be076b89f1ce6c92b1eca5853330ae2ef948

Thanks,
Wind
Comment 2 zhenxiang.li 2013-08-23 01:33:17 UTC 
It has been fixed, 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.