[Bug 772905] New: Internal data flow error when raw video file playing piped to v4l2sink

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=772905

            Bug ID: 772905
           Summary: Internal data flow error when raw video file playing
                    piped to v4l2sink
    Classification: Platform
           Product: GStreamer
           Version: 1.8.2
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: balazs.kreith at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Hi,

I would like to redirect a raw videofile to /dev/video1.
/dev/video1 is virtual device created by v4l2loopback
(https://github.com/umlaeute/v4l2loopback). 
The following pipeline seems ok:

gst-launch-1.0 multifilesrc location=foreman_cif.yuv ! videoparse width=352
height=288 format=2 framerate=25/1 ! videoconvert ! fakesink

Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

But changing it to v4l2sink device=/dev/video1, the result:

gst-launch-1.0 multifilesrc location=foreman_cif.yuv ! videoparse width=352
height=288 format=2 framerate=25/1 ! videoconvert ! v4l2sink device=/dev/video1

Setting pipeline to PAUSED ...
libv4l2: error getting pixformat: Invalid argument
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstMultiFileSrc:multifilesrc0:
Internal data flow error.
Additional debug info:
gstbasesrc.c(2948): gst_base_src_loop ():
/GstPipeline:pipeline0/GstMultiFileSrc:multifilesrc0:
streaming task paused, reason error (-5)
Execution ended after 0:00:00.000594754
Setting pipeline to PAUSED ...
Setting pipeline to READY ...

(gst-launch-1.0:6639): GStreamer-CRITICAL **: gst_object_unref: assertion
'((GObject *) object)->ref_count > 0' failed
Setting pipeline to NULL ...
Freeing pipeline ...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.