79man / v4lsink

Automatically exported from code.google.com/p/v4lsink
0 stars 0 forks source link

filesource not working with V4l2SinkLoopback #9

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Build and/or install v4lsink (deb package or mercurial) (I have modified the 
source by overwriting video1 to video0 in gst-v4lsink-loopback.vala)
2. Build and install v4l2loopback (modprobe v4l2loopback)
3. v4lsink 'filesrc location=1.yuv ! videoparse width=160 height=120 ! 
V4l2SinkLoopback'
4. mplayer tv:// -tv device=/dev/video0

What is the expected output? What do you see instead?
I expect the yuv video to show up in mplayer's screen but I get:
"v4l2: ioctl get format failed: Invalid argument
v4l2: ioctl set mute failed: Invalid argument
v4l2: 0 frames successfully processed, 0 frames dropped."

v4lsink shows no error:
** (v4lsink:12839): DEBUG: gst-app.vala:17: app_construct
** (v4lsink:12839): DEBUG: gst-v4lsink-loopback.vala:26: v4lSink register
** (v4lsink:12839): DEBUG: gst-v4lsink-loopback.vala:19: v4lSink plugin_init
** (v4lsink:12839): DEBUG: gst-v4lsink-loopback.vala:48: v4lSink construct
** (v4lsink:12839): DEBUG: gst-app.vala:26: app setup_pipeline
** (v4lsink:12839): DEBUG: gst-v4lsink-loopback.vala:60: device opened
** (v4lsink:12839): DEBUG: gst-v4lsink-loopback.vala:62: got caps
** (v4lsink:12839): DEBUG: gst-v4lsink-loopback.vala:72: set format
** (v4lsink:12839): DEBUG: gst-app.vala:21: app_constructed

What version of the product are you using? On what operating system?

Ubuntu linux (lucid)
2.6.32-23-generic kernel
valac 0.7.6
v4lsink (fetched from mercurial)
v4l2loopback (fetched from mercurial)

Please provide any additional information below.

./v4lsink 'filesrc location=1.yuv ! videoparse width=160 height=120 ! 
xvimagesink'
works perfectly. I see the movie in an X11 window.

./v4lsink 'filesrc location=1.yuv ! videoparse width=160 height=120 ! filesink 
location=2.yuv'
works as well. Movie saved to 2.yuv.

Original issue reported on code.google.com by nag...@gmail.com on 4 Jul 2010 at 2:12