Hey all,
I thought I would try a little experiment with the computer controlled cmaera today, but alas so many issues.
The plan was to use Gem to capture single jpeg frames at each state of camera movement. The problem is I can't get pix_video to show anything! There are 4 video4l devices on this machine, I'm using /dev/video0 xawtv sees the video fine if I choose NTSC, and composite. No matter what I send to pix_video I can't get it to texture anything.
I spent the most time with the "mode ntsc $1" messages w/out luck.
Is anyone using pix_video with a video4linux device (this is a bt848) with gem CVS?
Also I could not compile Gem 0.90 from gem.iem.at because it fails to find GL on this system! (a fedora core2 I did not set up myself..) I just installed the nvidia driver today. I'll try copying the pix_video src from 0.90 into my CVS src I guess.
Thanks B.
Oh and I get:
driverID (0) must not exceed 0
In the console when I create pix_video and anytime I send the driver message with any arguments. Obviously "0" does not exceed "0" as this message suggests. onto hacking the 0.90 stuff into CVS, if indeed anything there has changed at all.
Hey all,
I thought I would try a little experiment with the computer controlled cmaera today, but alas so many issues.
The plan was to use Gem to capture single jpeg frames at each state of camera movement. The problem is I can't get pix_video to show anything! There are 4 video4l devices on this machine, I'm using /dev/video0 xawtv sees the video fine if I choose NTSC, and composite. No matter what I send to pix_video I can't get it to texture anything.
I spent the most time with the "mode ntsc $1" messages w/out luck.
Is anyone using pix_video with a video4linux device (this is a bt848) with gem CVS?
Also I could not compile Gem 0.90 from gem.iem.at because it fails to find GL on this system! (a fedora core2 I did not set up myself..) I just installed the nvidia driver today. I'll try copying the pix_video src from 0.90 into my CVS src I guess.
Thanks B.
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
B. Bogart wrote:
Oh and I get:
driverID (0) must not exceed 0
In the console when I create pix_video and anytime I send the driver message with any arguments. Obviously "0" does not exceed "0" as this message suggests. onto hacking the 0.90 stuff into CVS, if indeed anything there has changed at all.
what is new is, that now configure checks whether it can find the apropriate header-files for video4linux and disables v4l if it can't find them.
what is the output of configure, and how does your Base/configLinux.h look like ?
mfg.asd.r IOhannes
IOhannes m zmoelnig wrote:
B. Bogart wrote:
what is new is, that now configure checks whether it can find the apropriate header-files for video4linux and disables v4l if it can't find them.
ah, yes: and the src/Gnu/configure has not been updated to reflect these changes. so if possible try the src/configure (this is the way to go; i'd like to abandon src/Gnu/)
mfg.asd.r IOhannes
Hi Johannes,
this was happening on the FC2 machine at work. v4l was installed and working (since I could see all 4 tuners with xawtv). The old build system from 0.90 could not find openGL so I could not use that. The CVS version of gem would compile fine, but pix_video would send that error message I posted to the list device something must not be lesser than 0. but it was 0.
So to get around it I used all the old 0.90 *video*.cpp|h files in the cvs version. Then it built fine using the 0.90 pix_video stuff and it worked like a charm.
So the CVS version: On FC2, compiles fine, pix_video is non functional
0.90 version: On FC2, will not compile (can't find openGL), pix_video IS functional.
I ordered two capture cards last week and I'll be dropping them into my debian machine at home in the next couple days. I hope this issue was specific to FC2 and that I will not have to merge the old pix_video stuff into Gem CVS again...
wish me luck.
B.
IOhannes m zmoelnig wrote:
IOhannes m zmoelnig wrote:
B. Bogart wrote:
what is new is, that now configure checks whether it can find the apropriate header-files for video4linux and disables v4l if it can't find them.
ah, yes: and the src/Gnu/configure has not been updated to reflect these changes. so if possible try the src/configure (this is the way to go; i'd like to abandon src/Gnu/)
mfg.asd.r IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-
B. Bogart -
IOhannes m zmoelnig