Open GoogleCodeExporter opened 9 years ago
I'll check and fix compilation, but scaling a hardcoded thing and I do not have
enough knowledge in gstreamer to fix this.
Original comment by gorinich...@gmail.com
on 5 Oct 2009 at 9:22
Seems that it was enough to remove the array definitions and set them to [].
Now compiles, need to check if it works later.
Attached a patch that removes the errors.
There are still some warnings like :
** (valac:22889): CRITICAL **: vala_class_add_hidden_method: assertion `self !=
NULL'
failed
But not sure if that will cause a problem..
Original comment by fred.tre...@googlemail.com
on 5 Oct 2009 at 12:44
Attachments:
With the patch :
v4lsink 'videotestsrc ! ffmpegcolorspace ! video/x-raw-yuv,width=640,height=480
!
V4l2SinkLoopback'
and
mplayer tv:// -tv driver=v4l2:device=/dev/video0
worked (oh, I did change the hardcoded /dev/video1 dev value.. )
Tonight I will try to check if skype can work with this.
For
v4lsink 'videotestsrc ! ffmpegcolorspace !
video/x-raw-yuv,width=640,height=480,format=\(fourcc\)UYVY ! V4l2SinkLoopback'
I get
** (v4lsink:8588): CRITICAL **: file /home/fred/dev/src/v4lsink/gst-app.vala.c:
line
101: uncaught error: could not parse caps
"video/x-raw-yuv,width=640,height=480,format=\(fourcc\)UYVY"
Will come back with resolution or a propper bugreport
Original comment by fred.tre...@googlemail.com
on 6 Oct 2009 at 7:30
[deleted comment]
I'm a bit lost, and can think of no better way to ask my question: why does it
not work this way?
v4l2loopback> make
v4l2loopback> sudo make install
v4l2loopback> sudo modprobe v4l2loopback device=/dev/video5
v4l2loopback> gst-launch videotestsrc ! v4l2sink device=/dev/video5 &
v4l2loopback> gst-launch v4l2src device=/dev/video5 ! ximagesink
Best Regards,
-SM
Original comment by smai...@alaya.com
on 16 Jun 2010 at 12:01
It worked before vala got upgraded
Original comment by gorinich...@gmail.com
on 16 Jun 2010 at 12:05
Really, just like my examples in comment 5?
v4l2loopback> make
v4l2loopback> sudo make install
v4l2loopback> sudo modprobe v4l2loopback device=/dev/video5
v4l2loopback> gst-launch videotestsrc ! v4l2sink device=/dev/video5 &
v4l2loopback> gst-launch v4l2src device=/dev/video5 ! ximagesink
Note I am refering to the v4l2sink which ships with gstreamer. If so, that
would be very good news, and I hope to see a fixed version soon. This seems to
fill a huge gap in gstreamer.
-SM
Original comment by smai...@alaya.com
on 16 Jun 2010 at 7:40
I never could make gstreamer native sink work, that is why I wrote this when I
had need in such sink.
Original comment by gorinich...@gmail.com
on 16 Jun 2010 at 7:53
afaik I could register this sink in gstreamer locally and use it just like in
example given.
Original comment by gorinich...@gmail.com
on 16 Jun 2010 at 7:55
[deleted comment]
I'm curious why you could never make the native gstreamer sink work. One thing
I noticed is that, when I tried the v4l2loopback device with all gstreamer
plugins,
v4l2loopback> gst-launch videotestsrc ! v4l2sink device=/dev/video5 &
it said it could not negotiate the pixmap format, before even doing this step
v4l2loopback> gst-launch v4l2src device=/dev/video5 ! ximagesink
This begs the question: why does the v4l2loopback device negotiate at all at
this point? Shouldn't it rather accept whatever the upstream dictates, and
leave it to (in my example, the gst) v4l2src to negotiate downstream on its
behalf. Does my question make sense? =)
-SM
Original comment by smai...@alaya.com
on 16 Jun 2010 at 9:59
Comments, gz?
Original comment by smai...@alaya.com
on 20 Jun 2010 at 10:56
v4l2 devices negotiate at initialization, that is the sink one who should defer
initialization until it got data format
Original comment by gorinich...@gmail.com
on 20 Jun 2010 at 11:01
Original issue reported on code.google.com by
fred.tre...@googlemail.com
on 5 Oct 2009 at 9:17