(V4L) Freeing captured frames: Invalid argume

[Blaz Malnersic]

Hello,

after starting camserv 0.50 (RedHat RPM) I get following:
2002-07-21 22:06:15 [video_init] image height: default:240 max:480 min:120 config:240 used:240

(V4l) Filling capture frames: Invalid argument
(V4l) Filling capture frames: Invalid argument
2002-07-21 22:06:15 [picloop] Too many bad snaps!  Aborting!
(V4L) Freeing captured frames: Invalid argument
(V4L) Freeing captured frames: Invalid argument
2002-07-21 22:06:15 [picloop] Exiting
2002-07-21 22:06:15 [picloop] BOGUS DEINIT CALL IN PICTURE TAKER!
2002-07-21 22:06:15 [v4l] Deinitialized without initializing V4L device

2002-07-21 22:06:15 [picloop] Could not de-initialize video device!
2002-07-21 22:06:22 [mainloop] Accepted new socket: 192.168.10.254

I see appliaction is listening on 9192, and video_basic works but I have trouble when I use Creative Webcam 5 (aka Philips 730) as video source. EffectTV or camserv work just fine.
Does anybody know what could be wrong?

Thanks

[Toby Gray]

I have the very same problem with my philips PCVC680K webcam.

It appears to be failing on setting the VIDIOCMCAPTURE flag on the video 4 linux filehandle. And thats as far as I can see for the moment (I'm not the worlds best C programmer)

I'm going to have a fiddle, but I'm not promising nothing.

Toby

[Toby Gray]

Me again :)

Just check out the latest CVS and it will work fine.

If you care: its due to the way it handels pallets, and the fact that the philips webcams use YUV20P as its pallet and camserv ver 0.50 expects RGB.

I would like to bring to the attention of the developer that the line:
'*  Comitted patch from Walter Haidinger to fixup log entry formats, and YUV palette.'

In the Changelog distributed with camstream 0.50 implies (to me at least) that the patch for YUV palette cams has been included in 0.50, which it is not.

It could just be me reading it wrong though :)

Toby