From: <sh...@op...> - 2010-08-14 22:57:03
|
Hi, And thanks for taking the time to answer. I can see your point. However, motion does two things very well: 1. It can record to a file and stream to a http port at the same time. 2. It can overlay date/time and other information on the recorded video in a simple to configure manner. I couldn't find another Linux command line software which does this - that is why I prefer using motion although I don't use the motion detection features. Also, could I configure one of the threshold options to at least do the least amount of work while it detects motion? (sort of reduce motion detection to a minimum) Sebastian On 08/14/2010 11:14 PM, Dick Middleton wrote: > On 08/14/10 22:52, sh...@op... wrote: >> Anybody knows something about this? > > Not really except to say that motion is primarily about motion detection > (hence the name). Turning it off rather defeats the object. > >> On 08/13/2010 04:24 PM, sh...@op... wrote: >>> I would like to use motion with a cctv system - but I wanted to record >>> continuously. I am recording from a usb webcam, in 800x600, 10fps, >>> mpeg4. I also have "output_all on". Now, on an Atom N450 processor, this >>> is eating about 35% cpu for a single camera. This seems a little high >>> for a single camera > > 10 fps is quite a lot. I run 4 webcams at ~5fps each on a 1.2G Via which uses > about 60%. Seems similar ball-park. > > - ffmpeg and mencoder seem to need a lot less for >>> recording with similar parameters. > > but they are not doing motion detection et al. > > Is 'output_all on' switching off any >>> motion detection processing, > > No, it's about output. > > or is there any other option I could use to >>> make sure that motion doesn't work on analysing the stream and trying to >>> detect motion (and consuming CPU time this way)? > > Dick > |