Continuous recording but it should be only on motions

[gianpyc]

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue.

I confirm that I have read the FAQ before opening this issue.

motionEyeOS Version

I am running motionEyeOS version: motionEye Version | 0.42.1 Motion Version | 4.3.2

Board Model

I am using the following board/model: Raspberry PI 4B+ 4gb

Camera

I am using the following type of camera: (choose from V4L2, MMAL, Network Camera, Fast Network Camera and Simple MJPEG Camera).

My camera model is: unifi uvc micro g2 The camera is confiigured as standalone manner and I get the stream using rest protocol

Network Connection

My motionEyeOS unit is connected to the network via: Ethernet

Peripherals

I am using the following peripherals that I consider relevant to this issue:

External Hard Disk in which I record the motions

Log Files

I consider the following log files relevant to this issue:

motioneye.log

motioneye.conf.txt camera-1.conf.txt

Issue

I have a fresh installation of motioneye in which I've connected a single camera that should records only on motions. However, I noticed that the camera starts recording even if no "real" motion is got and the recording threads start ending after a long time. This causes long registration storage on the hard disk that goes to be filled soon. I tried several settings but without success.

[starbasessd]

Unfortunately you didn't post the settings you are using for your camera. The settings I find most reliable for my cameras for my purposes are: The most significant ones are:

---

Frame Change Threshold: 0.1% (the percentage of pixels changing between frames) Auto Threshold Tuning: OFF (Never has been quite reliable IMO) Auto Noise Detection: ON (data noise in a frame) Despeckle Filter: ON (Handy on night views) Motion Gap: 2 (Minimum gap between detections in seconds) Captured Before: 15 (Create a frame buffer of that many frames per camera, to be able to put the pre-trigger frames into the movie) Captured After: 15 ( keep trigger on in case the movement detection stops momentarily) Minimum Motion Frames: 2 (the number of consecutive frames that change that it takes for the motion detection to decide there is a valid trigger)

---

They can be interactive and interfering with each other. If Motion Gap is too short, and Captured After too large, you never see an end to the trigger event. If Minimum Motion Frames is too small, you can trigger on 'false positive' motion detections. One thing to use while setting up (but not long term, as it takes more processor power, and time per frame) is to turn Show Frame Changes: ON. this will show the area that motion is seeing pixel changes, to help you see what it thinks is movement. If it is in an area that you don't want or need to be detected, you can turn on Mask (but this is not an option to turn the auto "SMART" function, as the AI isn't that good, IMO. Use Editable) It will still record the video from that area, but just not use anything it that area to determine motion. I use it on several outdoor cameras to mask tree leaves areas, and to not trigger on car traffic. If this helps, or you would like more info on a specific item, let me know.

[starbasessd]

BTW, I run my cameras in production at 15 Frames Per Second, (and the Before and After numbers are 15 to give me 1 second of extra video at the beginning and end. I can do this on 6 cameras on my motionEye Hub because I run in on a Lenovo M73 I5 PC (2.9GHz Quad Core) and a backup/test server on a VirtualBox VM running Debian Bullseye 11 with 4 cores at 3GHz on a Ryzen 1700. You may be able to get 15 Frames Per Second on a Pi4-4GB for your camera. I wouldn't push it much beyond that, though. Again, if any of this helps, or you would like more info on a specific item, let me know.

[gianpyc]

Thanks for your suggestion. Atm, I'm testing the settings that you suggested to see how they behave and it seems that they are working fine. Another problem that I saw, but this not related to motioneye, was the fact that I had old background process of motioneye that were running creating recordings that were not linked to my last settings :(((

[starbasessd]

Reboot is a wonderful function :)

[gianpyc]

:DDD