Winter time is a good time for some nature observation. Yesterday I had a woodpecker (picture) in front of my kitchen window. During the recent weeks there were long-tailed tits, a wren and other rarely seen birds. So I thought, it might be a good idea to capture some of these events :) I still own a Logitech C910 USB camera which allows HD video capturing up to 1080p. So I checked the web for some software that would begin video capturing in the case of motion detection and found motion, already available for Debian users. So I gave it a try. I tested all available resolutions of the camera together with the capturing results. I found that the resulting framerate of both the live stream and the captured video is highly depending on the resolution and some few configuration options. Below is a summary of my tests and the results I've achieved so far.
Logitech C910 HD camera
Just a bit of data regarding the camera. AFAIK it allows for fluent video streams up to 720p.
$ dmesg [..] usb 7-3: new high-speed USB device number 5 using ehci-pci usb 7-3: New USB device found, idVendor=046d, idProduct=0821 usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=1 usb 7-3: SerialNumber: 91CF80A0 usb 7-3: current rate 0 is different from the runtime rate 16000 usb 7-3: current rate 0 is different from the runtime rate 32000 uvcvideo: Found UVC 1.00 device
(046d:0821) input: UVC Camera (046d:0821) as /devices/pci0000:00/0000:00:1a.7/usb7/7-3/7-3:1.2/input/input17 $ lsusb [..] Bus 007 Device 005: ID 046d:0821 Logitech, Inc. HD Webcam C910 [..] $ v4l2-ctl -V -d /dev/video1 Format Video Capture: Width/Height : 1280/720 Pixel Format : 'YUYV' Field : None Bytes per Line: 2560 Size Image : 1843200 Colorspace : SRGB
uvcvideo kernel module is loaded and the user in question is part of the video group.
Installation and start
Installation of the software is as easy as always:
apt-get install motion
It is possible to run the software as a service. But for testing, I copied /etc/motion/motion.conf to ~/.motion/motion.conf, fixed its permissions (you cannot copy the file as user - it's not world readable) and disabled the daemon mode.
Note that in my case the correct device is /dev/video1 because the laptop has a built-in camera, that is /dev/video0. Also the target directory should be writeable by my user:
videodevice /dev/video1 target_dir ~/Videos
Then running motion from the command line ...
$ motion [..]  [NTC] [ALL] motion_startup: Motion 3.2.12+git20140228 Started [..]  [NTC] [ALL] motion_init: Thread 1 started , motion detection Enabled  [NTC] [ALL] main: Thread 1 is device: /dev/video1 input -1  [NTC] [VID] v4l2_get_capability: ------------------------ cap.driver: "uvcvideo" cap.card: "UVC Camera (046d:0821)" cap.bus_info: "usb-0000:00:1a.7-1" cap.capabilities=0x84000001 ------------------------  [NTC] [VID] v4l2_get_capability: - VIDEO_CAPTURE  [NTC] [VID] v4l2_get_capability: - STREAMING  [NTC] [VID] v4l2_select_input: name = "Camera 1", type 0x00000002, status 00000000  [NTC] [VID] v4l2_select_input: - CAMERA [..]  [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 1 items
... will begin to capture motion detection events and also output a live stream. CTRL+C will stop it again.
The live stream is available by pointing the browser to localhost:8081. However, the stream seems to run at 1 fps (frames per second) and indeed does. The stream gets more quality by this configuration:
stream_motion on stream_maxrate 100
The first option is responsible, that the stream only runs at one fps if there is no motion detection event. Otherwise the framerate increases to its maximum value, which is either the one given by stream_maxrate or the camera limit. The quality of the stream picture can be increased a bit further too by increasing the stream_quality value. Because I neither need the stream nor the control feed I disabled both:
stream_port 0 webcontrol_port 0
By default there is video and picture capturing if a motion event is detected. I'm not interested in these pictures, so I turned them off:
FYI: If you want a good picture quality, then the value of quality should very probably be increased.
This is the really interesting part :) Of course if I will "shoot" some birds (with the camera), then a small image of say 320x240 pixels is not enough. The camera allows for a capture resolution up to 1920x1080 pixels (1080p). It is advertised for fluent video streams up to 720p (1280x720 pixels). So I tried the following resolutions: 320x240, 640x480, 800x600, 640x360 (360p), 1280x720 (720p) and 1920x1080 (1080p). These are easily configured by the width and height variables. For example the following configures motion for 1280x720 pixels (720p):
width 1280 height 720
The result was really disappointing. No event is captured with more then 20 fps. At higher resolutions the framerate drops even further and at the highest resolution of 1920x1080 pixels, the framerate is only two(!) fps. Also every created video runs much too fast and even faster by increasing the framerate variable. Of course its default value of 2 (fps) is not enough for fluent videos. AFAIK the C910 can run with 30 fps at 1280x720 pixels. So increasing the value of framerate, the maximum framerate recorded, is a must-do. (If you wanna test yourself, check the log output for the value following
The solution to the issue, that videos are running too fast, however is to increase the pre_capture value, the number of
pre-captured (buffered) pictures from before motion was detected. Even small values like 3..5 result in a distinctive improvement of the situation. Though increasing the value further didn't have any effect. So the values below should almost get the most out of the camera and result in videos in normal speed.
framerate 100 pre_capture 5
Videos in 1280x720 pixels are still captured with 10 fps and I don't know why. Running guvcview, the same camera allows for 30 fps in this resolution (even 60 fps in lower resolutions). However, even if the framerate could be higher, the resulting video runs fluently. Still the quality is just moderate (or to be honest, still disappointing). It looks "pixelated". Only static pictures are sharp. It took me a while to fix this too, because I first thought, the reason is the camera or missing hardware support. It is not :) The reason is, that ffmpeg is configured to produce a moderate(?)-quality video. The relevant variables are ffmpeg_bps and ffmpeg_variable_bitrate. I got the best results just changing the latter:
Finally the resulting video quality is promising. I'll start with this configuration setting up an observation camera for the bird feeding ground.
There is one more tweak for me. I got even better results by enabling the auto_brightness feature.
So the complete configuration looks like this (only those options changed to the original config file)
daemon off videodevice /dev/video1 width 1280 height 720 framerate 100 auto_brightness on ffmpeg_variable_bitrate 2 target_dir /home/user/Videos stream_port 0 #8081 stream_motion on stream_maxrate 100 webcontrol_port 0 #8080