System Environment: ---------------------------------------- Platform: IVB Libva: staging branch 7157ffc1bc3dfd5b8d08acccd9f5b87cead46e0f Intel-driver: staging branch 1fd62ffd336293dce7d091bcea8399a40ccea21e Gst-plugins-ugly: 0.10 branch 9afc696e5fa9fb980e02df5637f022796763216f Gst-plugins-bad: 0.10 branch 91f508fc14f5cb4aca63bab6609abd29a2dfe0ab Gst-plugins-good: 0.10 branch 16dfcbe706d8d3dddfbc00c60145a1381a77fdc3 Gst-plugins-base: 0.10 branch 3359117536a062af9a0e946a603fd45e4c49560e Gstreamer: 0.10branch c1fa5ba9fd993a1f4cd1a843773bdcb4889edbfe Gst-vaapi: 0.4 branch e49e04a6aa9618b46d7a349a66372a16f3c690b3 Bug Info: ---------------------------------- Setting pipeline to PAUSED ... Pipeline is PREROLLING ... ** (gst-launch-0.10:15353): CRITICAL **: gst_vaapidecode_flush: assertion `decode->decoder' failed Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock Got EOS from element "pipeline0". Execution ended after 66451 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline .. Reproduce steps: --------------------------------- 1. xinit& 2. gst-launch-0.10 filesrc location=/home/gst_AVC_conformance/Mux_Stream/H264_1280x720_frame5581.mpeg ! mpegdemux ! vaapidecode ! vaapidownload ! filesink location="123.yuv" Actually result: After the above steps, there is no “123.yuv”
Modify the mpegdemux to mpegtsdemux ,then it can dump the yuv file. Reproduce steps: --------------------------------- 1. xinit& 2. gst-launch-0.10 filesrc location=/home/gst_AVC_conformance/Mux_Stream/H264_1280x720_frame5581.mpeg ! mpegtsdemux ! vaapidecode ! vaapidownload ! filesink location="123.yuv"
Using the cmd, the bug is not reproduced ------------------------ cmd: gst-launch-0.10 filesrc location=/home/gst_AVC_conformance/Mux_Stream/H264_1280x720_frame5581.mpeg ! mpegtsdemux ! vaapidecode ! vaapidownload ! filesink location="123.yuv"
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.