Re: 'motion' does not save movies, only still pics
----- Original Message -----
> From: "Scott Ferguson" <scott.ferguson.debian.user@gmail.com>
> On 26/09/14 00:12, Rob Owens wrote:
> > One thing that may be a factor in my case is that my test webcam is
> > very slow. I am only getting one picture every 2 or 3 seconds when
> > motion is detected. I have framerate set to 2 fps. Maybe motion is
> > aware that my pics are too far apart in time and is deciding not to
> > combine them into a movie.
>
> Any clues in the logs? 'top' may help find any bottlenecks. Note that
> an older box will have problems with high frequency high resolution
> images - especially with USB < 3. A work around that problem might be
> any or all of:-
> ;reduce frequency of images
> ;reduce image resolution
> ;offload image processing to hardware
>
> What sort of motion are you wanting to detect at 2 fps? A break-in by
> Speedy Gonzales? ;p
> Be careful or your motion directory will quickly fill with a huge amount
> of pictures. I don't use the movie output version - though I've used it
> in the past. I found it an unnecessary use of resources - it's trivial
> to construct a movie from the relevant still images at a later date -
> just ensure that you email those images off-site immediately after a
> motion event is detected (if you're using motion for security purposes).
>
>
> It may be relevant that while I do have the deb-multimedia.org
> repository enabled on the Debian (Wheezy) systems that run motion, it's
> pinned to give preference to debian repositories:-
> $ cat /etc/apt/preferences.d/multimedia.pref
> Package: *
> Pin: origin *.deb-multimedia.org
> Pin-Priority: 200
2 fps was the default. I've just been testing basic functionality so far.
syslog shows ffmpeg errors. I have ffmpeg installed from deb-multimedia.org, and I'm guessing there's a difference in command options or something. I'll change that and report back. Thanks for the help.
-Rob
Reply to: