Quoting Steven Brunasso <sbrunasso@xxxxxxxx>: > Well the output is just > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > For 230400 bytes. > > Is this an image..?? Yes. 320x240*3 = 230400. rawtoppm -bgr 320 240 yourfile.dat > foo.ppm should do the trick... Just remember: first few frames from IBM camera (and some other cameras) are too dark or too bright because the camera needs several frames to adjust itself (AGC, shutter speed etc.) to the lighting. It was just powered on, after all. But I would expect you to see at least *something*. If you access the /dev/video using read() then your app should handle EOF correctly (by ignoring it). The driver will return zero-sized reads in some cases. Maybe that's a bad idea, but nobody accesses video devices using read() anyway :-) Dmitri > Quoting Steven Brunasso <sbrunasso@xxxxxxxx>: > > > Does anyone have a quick program for ibmcam to save file to disk perhaps? > > cat < /dev/video0 > file.dat > > The file will contain BGR24 frames, *with no separators* between them. You > must know your image size to decode it properly. But it will work. You can > use raw2ppm or something for that. -- Linux: the choice of a GNU generation. (ksh@xxxxxxxxxxx put this on Tshirts in '93)
Attachment:
pgpWwnzWQxutE.pgp
Description: PGP signature
