hey all,
I'm doing a workshop in HK in about 13 days.
I wanted to demo pix_video, but I can't seem to get things working on my eee pc.
The device is working with v4l2, I can get a feed from mplayer with:
mplayer tv:// -tv driver=v4l2:device=/dev/video0:fps=30
seems generic enough. Here is the output regarding video format:
Opening video decoder: [raw] RAW Uncompressed Video VDec: vo config request - 640 x 480 (preferred colorspace: Packed YUY2) VDec: using Packed YUY2 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 640x480 => 640x480 Packed YUY2 Selected video codec: [rawyuy2] vfm: raw (RAW YUY2)
I'm working with an svn copy of GEM updated yesterday. I'm configuring with:
./configure --prefix=/usr --without-libv4l1 --with-libv4l2-libs=/usr/lib/ --with-libv4l2-includes=/usr/include/
and GEM complains about the camera when I start pix_video (and I get no video image):
v4l: VDIOCGCHAN: Invalid argument
This device/camera must only have one channel?
I can't tell if I'm using v4l1 or 2. configure tells me v4l: yes not matter if its v4l1 or v4l2 I enable. I also have a vague memory that configure should tell me what v4l its using, like:
v4l: yes (libv4l2)
but I can't get that output with any combination of flags. Did I imagine it?
Anyhow let me know if anyone has a working uvc webcam in gem (linux-intrepid) or better yet working eeepc webcam.
Thanks all.
Here is a link to what I'm doing here in HK:
http://www.videotage.org.hk/projects/20090514_dreamingmachine.htm
I'll have to make another post about some issues with pix_crop, and pix_buffer save, which forced me to change some aspects of the project!
..b..
The way I fixed this on MSI Wind which uses UVC driver as well is to compile latest version of the v4l2 object that includes some changes I forwarded to the maintainer (I think it is part of the pdp or pidip, can't remember any more). That worked perfectly fine even though I had similar problems with Gem. IIRC when I was inquiring about this the last time I think the reply was that currently v4l2 is not supported well under Gem (although please take this with a boulder of salt as this has been a while ago).
Hope this helps!
Best wishes,
Ico
-----Original Message----- From: gem-dev-bounces@iem.at [mailto:gem-dev-bounces@iem.at] On Behalf Of ben@ekran.org Sent: Sunday, May 10, 2009 7:34 PM To: gem-dev@iem.at Subject: [GEM-dev] uvc webcam (eee pc 900 built in) with pix_video?
hey all,
I'm doing a workshop in HK in about 13 days.
I wanted to demo pix_video, but I can't seem to get things working on my eee pc.
The device is working with v4l2, I can get a feed from mplayer with:
mplayer tv:// -tv driver=v4l2:device=/dev/video0:fps=30
seems generic enough. Here is the output regarding video format:
Opening video decoder: [raw] RAW Uncompressed Video VDec: vo config request - 640 x 480 (preferred colorspace: Packed YUY2) VDec: using Packed YUY2 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 640x480 => 640x480 Packed YUY2 Selected video codec: [rawyuy2] vfm: raw (RAW YUY2)
I'm working with an svn copy of GEM updated yesterday. I'm configuring with:
./configure --prefix=/usr --without-libv4l1 --with-libv4l2-libs=/usr/lib/ --with-libv4l2-includes=/usr/include/
and GEM complains about the camera when I start pix_video (and I get no video image):
v4l: VDIOCGCHAN: Invalid argument
This device/camera must only have one channel?
I can't tell if I'm using v4l1 or 2. configure tells me v4l: yes not matter if its v4l1 or v4l2 I enable. I also have a vague memory that configure should tell me what v4l its using, like:
v4l: yes (libv4l2)
but I can't get that output with any combination of flags. Did I imagine it?
Anyhow let me know if anyone has a working uvc webcam in gem (linux-intrepid) or better yet working eeepc webcam.
Thanks all.
Here is a link to what I'm doing here in HK:
http://www.videotage.org.hk/projects/20090514_dreamingmachine.htm
I'll have to make another post about some issues with pix_crop, and pix_buffer save, which forced me to change some aspects of the project!
..b..
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Ivica Ico Bukvic wrote:
Gem. IIRC when I was inquiring about this the last time I think the reply was that currently v4l2 is not supported well under Gem (although please take this with a boulder of salt as this has been a while ago).
this has changed with the advent of libv4l (which is now in debian)
at least here on my eepc 901 the camera works out of the box with Gem (no special configure tweaks needed)
I'm working with an svn copy of GEM updated yesterday. I'm configuring with:
./configure --prefix=/usr --without-libv4l1 --with-libv4l2-libs=/usr/lib/ --with-libv4l2-includes=/usr/include/
see above: no special switches should be needed (if libv4l is installed)
and GEM complains about the camera when I start pix_video (and I get no video image):
v4l: VDIOCGCHAN: Invalid argument
This device/camera must only have one channel?
yes, but how is Gem supposed to know? anyhow, it shouldn't really matter, as the driver will either ignore the channel-change request or you could set it to "channel 0".
I can't tell if I'm using v4l1 or 2. configure tells me v4l: yes not matter if its v4l1 or v4l2 I enable. I also have a vague memory that configure should tell me what v4l its using, like:
v4l: yes (libv4l2)
your memory might be correct, but the world moves on and configure-scripts get updated.
i'll check back on my eee which version of libv4l i'm using.
fgamsdr IOhannes
Thanks Johannes.
I tried a straight:
svn update && svn revert . && aclocal && autoconf && ./configure && make
same issue.
I've attached the webcam lsusb -v info, maybe the 901 has a different camera?
I'm linking with libv4l-0 0.5.7-1~intrepid1
Let me know if you have any ideas, otherwise I'll leave this off the demo list.
Thanks all. .b.
Ivica Ico Bukvic wrote:
Gem. IIRC when I was inquiring about this the last time I think the reply was that currently v4l2 is not supported well under Gem (although please take this with a boulder of salt as this has been a while ago).
this has changed with the advent of libv4l (which is now in debian)
at least here on my eepc 901 the camera works out of the box with Gem (no special configure tweaks needed)
I'm working with an svn copy of GEM updated yesterday. I'm configuring with:
./configure --prefix=/usr --without-libv4l1 --with-libv4l2-libs=/usr/lib/ --with-libv4l2-includes=/usr/include/
see above: no special switches should be needed (if libv4l is installed)
and GEM complains about the camera when I start pix_video (and I get no video image):
v4l: VDIOCGCHAN: Invalid argument
This device/camera must only have one channel?
yes, but how is Gem supposed to know? anyhow, it shouldn't really matter, as the driver will either ignore the channel-change request or you could set it to "channel 0".
I can't tell if I'm using v4l1 or 2. configure tells me v4l: yes not matter if its v4l1 or v4l2 I enable. I also have a vague memory that configure should tell me what v4l its using, like:
v4l: yes (libv4l2)
your memory might be correct, but the world moves on and configure-scripts get updated.
i'll check back on my eee which version of libv4l i'm using.
fgamsdr IOhannes
ben@ekran.org wrote:
Thanks Johannes.
I tried a straight:
svn update && svn revert . && aclocal && autoconf && ./configure && make
same issue.
I've attached the webcam lsusb -v info, maybe the 901 has a different camera?
I'm linking with libv4l-0 0.5.7-1~intrepid1
at least there is a difference in here: i have libv4l 0.5.9-1
the webcams seem to be fairly the same, though i get
ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC WebCam / CNF7129
whereas yuo have
ID 04f2:b071 Chicony Electronics Co., Ltd
most likely this difference is due to the kernel used: i am running 2.6.29-2 (debian squeeze/sid); intrepid has 2.6.27.11.14
now after ages of recompiling Gem on my eee with the steps as you describe them, i do: pd -lib Gem examples/04.video/00.SimpleTest.pd and click on "1" to start rendering.
i see myself (lo! it works), and this is what i read: pd-console:
video driver 0: video4linux2 video driver 0: video4linux video driver 0: ieee1394 for linux
[...]
v4l2: changed size from 64x64 to 640x480 v4l2: GEM: pix_video: Opened video connection 0xC
and on the console (stderr):
v4l2: vidioc_s_crop: Invalid argument v4l2: VIDIOC_S_FMT: Invalid argument
that's it. everything's happy (though i wonder how to get the advertised 1.3 mega pixels out of my camera with a fixed resolution of 640x480)
for whatever reasons i have some more kernels installed on my system: 2.6.28-1 same result as with 2.6.29-2 (lo! it still works) 2.6.26-2 same result as with 2.6.29-2 (alas! still no problems)
i notice that on 2.6.26-2, my camera is still shown as
ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC WebCam / CNF7129
so either the models to differ, or squeeze/sid is simply more verbose than intrepid. (googling a bit suggests the latter; e.g. the first hit for "CNF7129" is about the eeepc900 (!) webcam)
obviously this doesn't really help you at all. afair, cyrille has managed to use the webcam of his eee as well...
fgmadsr IOhannes
hello Ben,
i don't have a eee, but i do have exactely the same camera on my laptop.
my ./configure output somthing like this : use v4l : yes (libv4l)
using ubuntu 8.10 (intrepid) and the same version than your of libv4l.
when creating a pix_video object, i've got in the pd log : video driver 0: video4linux2 video driver 1: video4linux video driver 2: ieee1394 for linux
pix_video help patch is working out of the box.
i can't understand why it's not working for you.
Cyrille
ben@ekran.org a écrit :
Thanks Johannes.
I tried a straight:
svn update && svn revert . && aclocal && autoconf && ./configure && make
same issue.
I've attached the webcam lsusb -v info, maybe the 901 has a different camera?
I'm linking with libv4l-0 0.5.7-1~intrepid1
Let me know if you have any ideas, otherwise I'll leave this off the demo list.
Thanks all. .b.
Ivica Ico Bukvic wrote:
Gem. IIRC when I was inquiring about this the last time I think the reply was that currently v4l2 is not supported well under Gem (although please take this with a boulder of salt as this has been a while ago).
this has changed with the advent of libv4l (which is now in debian)
at least here on my eepc 901 the camera works out of the box with Gem (no special configure tweaks needed)
I'm working with an svn copy of GEM updated yesterday. I'm configuring with:
./configure --prefix=/usr --without-libv4l1 --with-libv4l2-libs=/usr/lib/ --with-libv4l2-includes=/usr/include/
see above: no special switches should be needed (if libv4l is installed)
and GEM complains about the camera when I start pix_video (and I get no video image):
v4l: VDIOCGCHAN: Invalid argument
This device/camera must only have one channel?
yes, but how is Gem supposed to know? anyhow, it shouldn't really matter, as the driver will either ignore the channel-change request or you could set it to "channel 0".
I can't tell if I'm using v4l1 or 2. configure tells me v4l: yes not matter if its v4l1 or v4l2 I enable. I also have a vague memory that configure should tell me what v4l its using, like:
v4l: yes (libv4l2)
your memory might be correct, but the world moves on and configure-scripts get updated.
i'll check back on my eee which version of libv4l i'm using.
fgamsdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Thanks Cyrille.
I got a fresh checkout from svn thinking maybe some configure issue was there. Very interestingly I am getting different pix_video outputs on instantiation:
video driver 0: video4linux
no videot4linux2
This is after doing this on a fresh co:
aclocal && autoconf && ./configure --prefix=/usr && make
I'm confused...
Ah, well configure tells me whats up:
checking for PKG_LIBV4L1_CFLAGS... checking for PKG_LIBV4L1_LIBS... checking for libv4l1-config... no checking for v4l1_open in -llibv4l1... no checking for PKG_LIBV4L2_CFLAGS... checking for PKG_LIBV4L2_LIBS... checking for libv4l2-config... no checking for v4l2_open in -llibv4l2... no
hmmm...
apt-get install --reinstall libv4l-0
does not make a difference.
seems gcc agrees:
gcc -llibv4l2 /usr/bin/ld: cannot find -llibv4l2
ummmm..
file /usr/lib/libv4l2.so.0 /usr/lib/libv4l2.so.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
I'm lost... but seems like little to do with Gem. I'll look into v4l issues on intrepid.
Thanks all for trying.
.b.
hello Ben,
i don't have a eee, but i do have exactely the same camera on my laptop.
my ./configure output somthing like this : use v4l : yes (libv4l)
using ubuntu 8.10 (intrepid) and the same version than your of libv4l.
when creating a pix_video object, i've got in the pd log : video driver 0: video4linux2 video driver 1: video4linux video driver 2: ieee1394 for linux
pix_video help patch is working out of the box.
i can't understand why it's not working for you.
Cyrille
ben@ekran.org a écrit :
Thanks Johannes.
I tried a straight:
svn update && svn revert . && aclocal && autoconf && ./configure && make
same issue.
I've attached the webcam lsusb -v info, maybe the 901 has a different camera?
I'm linking with libv4l-0 0.5.7-1~intrepid1
Let me know if you have any ideas, otherwise I'll leave this off the demo list.
Thanks all. .b.
Ivica Ico Bukvic wrote:
Gem. IIRC when I was inquiring about this the last time I think the reply was that currently v4l2 is not supported well under Gem (although please take this with a boulder of salt as this has been a while ago).
this has changed with the advent of libv4l (which is now in debian)
at least here on my eepc 901 the camera works out of the box with Gem (no special configure tweaks needed)
I'm working with an svn copy of GEM updated yesterday. I'm configuring with:
./configure --prefix=/usr --without-libv4l1 --with-libv4l2-libs=/usr/lib/ --with-libv4l2-includes=/usr/include/
see above: no special switches should be needed (if libv4l is installed)
and GEM complains about the camera when I start pix_video (and I get no video image):
v4l: VDIOCGCHAN: Invalid argument
This device/camera must only have one channel?
yes, but how is Gem supposed to know? anyhow, it shouldn't really matter, as the driver will either ignore the channel-change request or you could set it to "channel 0".
I can't tell if I'm using v4l1 or 2. configure tells me v4l: yes not matter if its v4l1 or v4l2 I enable. I also have a vague memory that configure should tell me what v4l its using, like:
v4l: yes (libv4l2)
your memory might be correct, but the world moves on and configure-scripts get updated.
i'll check back on my eee which version of libv4l i'm using.
fgamsdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
did you install libv4l-dev? i think it's your problem...
c
ben@ekran.org a écrit :
Thanks Cyrille.
I got a fresh checkout from svn thinking maybe some configure issue was there. Very interestingly I am getting different pix_video outputs on instantiation:
video driver 0: video4linux
no videot4linux2
This is after doing this on a fresh co:
aclocal && autoconf && ./configure --prefix=/usr && make
I'm confused...
Ah, well configure tells me whats up:
checking for PKG_LIBV4L1_CFLAGS... checking for PKG_LIBV4L1_LIBS... checking for libv4l1-config... no checking for v4l1_open in -llibv4l1... no checking for PKG_LIBV4L2_CFLAGS... checking for PKG_LIBV4L2_LIBS... checking for libv4l2-config... no checking for v4l2_open in -llibv4l2... no
hmmm...
apt-get install --reinstall libv4l-0
does not make a difference.
seems gcc agrees:
gcc -llibv4l2 /usr/bin/ld: cannot find -llibv4l2
ummmm..
file /usr/lib/libv4l2.so.0 /usr/lib/libv4l2.so.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
I'm lost... but seems like little to do with Gem. I'll look into v4l issues on intrepid.
Thanks all for trying.
.b.
hello Ben,
i don't have a eee, but i do have exactely the same camera on my laptop.
my ./configure output somthing like this : use v4l : yes (libv4l)
using ubuntu 8.10 (intrepid) and the same version than your of libv4l.
when creating a pix_video object, i've got in the pd log : video driver 0: video4linux2 video driver 1: video4linux video driver 2: ieee1394 for linux
pix_video help patch is working out of the box.
i can't understand why it's not working for you.
Cyrille
ben@ekran.org a écrit :
Thanks Johannes.
I tried a straight:
svn update && svn revert . && aclocal && autoconf && ./configure && make
same issue.
I've attached the webcam lsusb -v info, maybe the 901 has a different camera?
I'm linking with libv4l-0 0.5.7-1~intrepid1
Let me know if you have any ideas, otherwise I'll leave this off the demo list.
Thanks all. .b.
Ivica Ico Bukvic wrote:
Gem. IIRC when I was inquiring about this the last time I think the reply was that currently v4l2 is not supported well under Gem (although please take this with a boulder of salt as this has been a while ago).
this has changed with the advent of libv4l (which is now in debian)
at least here on my eepc 901 the camera works out of the box with Gem (no special configure tweaks needed)
I'm working with an svn copy of GEM updated yesterday. I'm configuring with:
./configure --prefix=/usr --without-libv4l1 --with-libv4l2-libs=/usr/lib/ --with-libv4l2-includes=/usr/include/
see above: no special switches should be needed (if libv4l is installed)
and GEM complains about the camera when I start pix_video (and I get no video image):
v4l: VDIOCGCHAN: Invalid argument
This device/camera must only have one channel?
yes, but how is Gem supposed to know? anyhow, it shouldn't really matter, as the driver will either ignore the channel-change request or you could set it to "channel 0".
I can't tell if I'm using v4l1 or 2. configure tells me v4l: yes not matter if its v4l1 or v4l2 I enable. I also have a vague memory that configure should tell me what v4l its using, like:
v4l: yes (libv4l2)
your memory might be correct, but the world moves on and configure-scripts get updated.
i'll check back on my eee which version of libv4l i'm using.
fgamsdr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
ben@ekran.org wrote:
Thanks Cyrille.
I got a fresh checkout from svn thinking maybe some configure issue was there. Very interestingly I am getting different pix_video outputs on instantiation:
video driver 0: video4linux
no videot4linux2
This is after doing this on a fresh co:
aclocal && autoconf && ./configure --prefix=/usr && make
I'm confused...
Ah, well configure tells me whats up:
checking for PKG_LIBV4L1_CFLAGS... checking for PKG_LIBV4L1_LIBS... checking for libv4l1-config... no checking for v4l1_open in -llibv4l1... no checking for PKG_LIBV4L2_CFLAGS... checking for PKG_LIBV4L2_LIBS... checking for libv4l2-config... no checking for v4l2_open in -llibv4l2... no
do you have "pkg-config" installed? (make sure you do).
this is what should work: $ pkg-config --libs libv4l1 -lv4l1
hmmm...
apt-get install --reinstall libv4l-0
does not make a difference.
seems gcc agrees:
gcc -llibv4l2
obivous, as it should read "-lv4l2". the configure-script is a bit at loss, as it need "libv4l1" as argument to pkg-config and (lib)v4l1 as library to link against.
so i really guess the problem is a missing pkg-config.
/usr/bin/ld: cannot find -llibv4l2
ummmm..
fmgas.dr IOhannes
-
ben＠ekran.org -
cyrille henry -
IOhannes m zmoelnig -
Ivica Ico Bukvic