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 > > [email protected] 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 >>> [email protected] >>> http://lists.puredata.info/listinfo/gem-dev > _______________________________________________ GEM-dev mailing list [email protected] http://lists.puredata.info/listinfo/gem-dev
