Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

detect not using fps setting #11715

Closed
gniting opened this issue Jun 3, 2024 · 1 comment
Closed

detect not using fps setting #11715

gniting opened this issue Jun 3, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@gniting
Copy link
Contributor

gniting commented Jun 3, 2024

Describe what you are trying to accomplish and why in non technical terms
Limit detect fps to 5

Describe the solution you'd like
detect should use 5 fps and cause fffmpeg to use less CPU

Describe alternatives you've considered
N/A

Additional context
Even though I have the following in my camera and global config, fps is higher than 5

...
detect:
   enabled: true
   fps: 5
...
cameras:
  office:
     enabled: true
     ffmpeg:
       inputs:
       - path: rtsp:https://@192.168.7.14:554/cam/realmonitor?channel=2&subtype=0
         roles:
         - record
         - detect
     detect:
       fps: 5

image

@gniting gniting added the enhancement New feature or request label Jun 3, 2024
@hawkeye217
Copy link
Collaborator

This is not problematic and is expected. Detect "FPS" is a bit of a misnomer, as there can be multiple detection regions on the same frame from your camera.

This is labeled differently in the next version of frigate to avoid this confusion.

Closing this, as this is not an issue and not a feature request.

@hawkeye217 hawkeye217 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants