Replies: 1 comment
-
Looks like the commit that introduced this new "low-end machine unfriendly" approach is 876c043 (identified by bisecting). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Did you read the guide?
Yes
What is the base version number of Motion being used?
4.5.x
What was the install method?
Installed via package tool
What is base architecture?
ARM-32bit
What is the distro being used?
Raspbian
Disto version number
bullseye
Camera type(s) being used?
Network camera with HTTP
Describe the issue/problem and steps to reproduce
Using
motion
on RPi 3 combined with network camera (HTTP serving a JPG image for every request). I don't need motion detection or stream saving - only taking image snapshots in regular intervals of 60 seconds. Looks like somewhere between version 4.2.2 and 4.5.1 some logic has changed andmotion
no longer allows a "quiet" mode in which the HTTP requests would be fired off only when needed (or simply looking at the value ofminimum_frame_time 30
). Version 4.5.1 requests the updates at the minimal rate of 1 image per second which is way beyond my need.It would be great if the old behaviour could be brought back as it would really help me to tame CPU time on my Raspberry Pi.
Motion log output at log_level 8
Beta Was this translation helpful? Give feedback.
All reactions