Tom, > Hello again, >>> Tom, that would be nice, for now we are stuck with changing line 178:) >>> > I added command line arguments now (see: http://naaa.de/uvc_streamer.htm). > > You can adjust: > > * Frames per second (not very accurate, uses usleep) > * Resolution > * Devicename > * TCP port to listen on >
Ok, I tested all the options including different frame rates. Everything appears to work well. Again using VLC, my cpu for 160x120 was stuff all 320x240 was a little bit 640x480 was just a bit more (note I like using technical terms:)) Seriously, even at 640x480 my total cpu usage is only about 10-15%, that is for everything not the streamer. VLC is using about 1.3% and the streamer a lot less. I noticed that it does not matter which resolution I run at the delay in the video response is always the same 1-2 secs. It seemed a lot longer with Konqueror because that was continually writing and reading to/from the disk. VLC is not using the disk at all just reading the stream directly out of the tcp port, which is probably why it uses so much less resources. As per another suggestion I have just used Motion to pipe the camera into VLC i.e. not using uvc_streamer at all, and my cpu is at 100%. uvc_streamer is way more efficient for a local lan. Thanks, Brian PS. a clean exit option would be good. _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
