Hey,
I have a schleptop with a built-in camera (lenovo t400). Xawtv works
great, but I cannot get pix_video to start.
When I start it (trying out lots of different options), it says:
VIDIOCSCHAN: Invalid argument
Anyone have an idea how to fix Pixes/videoV4L.cpp so that it makes
the right ioctls?
thanks -august.
Here is my v4linfo:
### v4l2 device info [/dev/video0] ### general info VIDIOC_QUERYCAP driver : "uvcvideo" card : "Integrated Camera" bus_info : "usb-0000:00:1a.7-6" version : 0.1.0 capabilities : 0x4000001 [VIDEO_CAPTURE,STREAMING]
standards
inputs VIDIOC_ENUMINPUT(0) index : 0 name : "Camera 1" type : CAMERA audioset : 0 tuner : 0 std : 0x0 [] status : 0x0 []
video capture VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE) index : 0 type : VIDEO_CAPTURE flags : 0 description : "YUV 4:2:2 (YUYV)" pixelformat : 0x56595559 [YUYV] VIDIOC_G_FMT(VIDEO_CAPTURE) type : VIDEO_CAPTURE fmt.pix.width : 640 fmt.pix.height : 480 fmt.pix.pixelformat : 0x56595559 [YUYV] fmt.pix.field : NONE fmt.pix.bytesperline : 1280 fmt.pix.sizeimage : 614400 fmt.pix.colorspace : unknown fmt.pix.priv : 0
controls VIDIOC_QUERYCTRL(BASE+0) id : 9963776 type : INTEGER name : "Brightness" minimum : -128 maximum : 127 step : 1 default_value : 0 flags : 0 VIDIOC_QUERYCTRL(BASE+1) id : 9963777 type : INTEGER name : "Contrast" minimum : 0 maximum : 100 step : 1 default_value : 0 flags : 0 VIDIOC_QUERYCTRL(BASE+2) id : 9963778 type : INTEGER name : "Saturation" minimum : 0 maximum : 100 step : 1 default_value : 0 flags : 0 VIDIOC_QUERYCTRL(BASE+3) id : 9963779 type : INTEGER name : "Hue" minimum : -20 maximum : 20 step : 1 default_value : 0 flags : 0
### video4linux device info [/dev/video0] ### general info VIDIOCGCAP name : "Integrated Camera" type : 0x1 [CAPTURE] channels : 1 audios : 0 maxwidth : 1280 maxheight : 1024 minwidth : 48 minheight : 32
channels VIDIOCGCHAN(0) channel : 0 name : "Camera 1" tuners : 0 flags : 0x0 [] type : CAMERA norm : 0
tuner
audio
picture VIDIOCGPICT brightness : 32382 hue : 32768 colour : 0 contrast : 0 whiteness : 0 depth : 16 palette : YUYV
buffer
window VIDIOCGWIN x : 0 y : 0 width : 640 height : 480 chromakey : 0 flags : 0
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
august wrote:
Hey,
Anyone have an idea how to fix Pixes/videoV4L.cpp so that it makes the right ioctls?
please don't! "videoV4L" is the backend for video4linux-1 devices.
### v4l2 device info [/dev/video0] ###
whereas you have a video4linux-2 device. so videoV4L is not for you, but videoV4L2 is. it seems like the version of Gem you are using, is compiled without v4l2 support. you need libv4l-dev in order to enable it.
this will make v4l2 the default backend.
fgasdmr IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
august wrote:
Hey,
Anyone have an idea how to fix Pixes/videoV4L.cpp so that it makes the right ioctls?
please don't! "videoV4L" is the backend for video4linux-1 devices.
### v4l2 device info [/dev/video0] ###
whereas you have a video4linux-2 device. so videoV4L is not for you, but videoV4L2 is. it seems like the version of Gem you are using, is compiled without v4l2 support. you need libv4l-dev in order to enable it.
this will make v4l2 the default backend.
ok, I figgered as much out already in the mean time.
I recompiled Gem with v4l2, but now have the same problem as these two guys:
http://puredata.hurleur.com/sujet-2223-gem-pix-video-firewire-linux http://lists.puredata.info/pipermail/gem-dev/2008-09/003669.html
again, the camera works perfectly with xawtv, mplayer, openframeworks, and any other v4l2 app out there.
I'd also mention that the Gem code still uses an archaic ffmpeg version. I can compile without it, but it is a shame not to have those features.
http://lists.puredata.info/pipermail/gem-dev/2008-01/003300.html
fgasdmr IOhannes
¿que es fgasdmr?
¡thanks!
-august.
On 2010-04-18 14:50, august wrote:
-----BEGIN PGP SIGNED MESSAGE-----
I recompiled Gem with v4l2, but now have the same problem as these two guys:
it seems like those are just one guy...
http://puredata.hurleur.com/sujet-2223-gem-pix-video-firewire-linux http://lists.puredata.info/pipermail/gem-dev/2008-09/003669.html
and you tried both YUV and RGBA colorspaces?
I'd also mention that the Gem code still uses an archaic ffmpeg version.
if your Gem uses an archaic version of ffmpeg, then it's likely that you are using an archaic version of Gem :-)
FFMPEG support has been dropped totally since at least 0.92. the way to go is to use gmerlin_avdec (and i'm actually surprised that you don't)
fm,gadsr IOhannes
On Mon, 19 Apr 2010, IOhannes m zmoelnig wrote:
FFMPEG support has been dropped totally since at least 0.92. the way to go is to use gmerlin_avdec (and i'm actually surprised that you don't)
What happened with FFMPEG support ?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
I'm not completely clear on what gmerlin is, but I believe ffmpeg is an underlying component: http://gmerlin.sourceforge.net/avdec_frame.html
So if you compile with gmerlin support, you get a whole mess of decoding options.
-martin
On Mon, 2010-04-19 at 15:56 -0400, Mathieu Bouchard wrote:
On Mon, 19 Apr 2010, IOhannes m zmoelnig wrote:
FFMPEG support has been dropped totally since at least 0.92. the way to go is to use gmerlin_avdec (and i'm actually surprised that you don't)
What happened with FFMPEG support ?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801 _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
august -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Martin Eckart -
Mathieu Bouchard