![]() ![]() The high load average and SD card death is being caused by the high number of writes (images and video files) on the SD card. This slow frame rate is due to the high CPU needed by motion performing image processing on the low powered Pi. ![]() The cameras suffered from low frame rate (FPS), high load average, frequent lockups, and SD cards dying. I have spent countless hours writing scripts, web pages, and various hacks to build a robust 4 camera home security system using this setup. The problem with using motion on the Raspberry PiĪfter much experimentation and time trying to make it work, I found the motion solution is not that great in practice. Using this technique below, my camera system is now able to get closer to the full resolution for each Raspberry Pi camera which is 1920×1080 at 30 frames per second – and reliably running for years without issue. On the modest hardware on the Raspberry Pi, I was only able to reliably achieve 4-10 frames-per-second at 800×600, depending on the Raspberry Pi model in use. Motion requires some horsepower to handle the video processing to detect motion, and also to run the web server and other features. There are also variants of motion such as MotionEye or motionEyeOS which provide a nicer UI on top of motion. When you read about using Raspberry Pi cameras as part of your home security system, most of the information you will find will point you in the direction of running motion which is the de-facto standard for doing video motion detection on Linux. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |