I was using the latest Raspbian buster release, which provides ffmpeg compiled with support for the Pi H.264 decoder (the h264_mmal codec is available): Raspberry Pi boards are equipped with a hardware H.264 decoder, and it seemed Motion wasn't making use of it. ![]() The Pi is configured to run using the conservative CPU governor, locking the CPU clock speed to 600Mhz (in order to reduce power consumption and heat output), but even then the usage seemed excessive. By default the camera outputs 1080p resolution with H.265 encoding, so I set up a secondary (slave) stream at VGA resolution with H.264 encoding, but even using that still resulted in over 60% CPU usage with Motion running. I noticed that the CPU utilization was rather high. ![]() ![]() I recently acquired a cheap "IPCAM-100" IP security camera and connected it to an Raspberry Pi 3+ running Motion software package to detect events and record video.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |