[Detector Support]: How can Detect FPS exceed the frame rate of the underlying camera feed? #9899
Unanswered
pbix
asked this question in
Detector Support
Replies: 2 comments 1 reply
-
Frigate runs detection on regions, which are portions of the camera frame. Sometimes these detections can be done multiple times on a single camera frame. In this case detection fps really means detections per second. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Confusing indeed. On a windy day, some of my cameras pick of many moving tree shadows, and this can even go over 40 FPS (that was the first clue before finding this topic that it cannot be real, no way the detect stream of the camera could have so many frames per second) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
I want to start by saying that this is an really great project and I have been using it for several years and learned a lot in the process. This post is not about a problem really but rather for my continuing education.
I spend time studying the meaning of the information on the Frigate system page. In my setup I observe on occasion that the detect FPS exceeds the available camera frame rate. I have observed this situation often when it is windy and there is continuous motion in the field of view and only on exterior cameras.
I am confused. How can the detect FPS be higher than the underlying camera feed? What is the meaning of this (0 skipped) indication?
In my setup the main camera feed is set at 5 FPS (used for recording) in the camera and the low res sub feed is set at 2FPS (used for detect). On the system screen in Frigate the capture feed shows 3.1 FPS and the Detect shows 6.8 FPS as show in the screen shot below. The Detect FPS is the one the varies, the Capture never changes. Its confusing that the numbers in Frigate do not agree with what is programmed in the camera. This is an Amcrest camera.
If anyone can explain these discrepancy it would help me and perhaps others.
Version
0.13.1-34fb1c2
Frigate config file
N/A
docker-compose file or Docker CLI command
N/A
Relevant log output
Operating system
Proxmox
Install method
Docker Compose
Coral version
CPU (no coral)
Any other information that may be helpful
Beta Was this translation helpful? Give feedback.
All reactions