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

Trying to figure out what the new Audio Detector is hearing compared to what I am hearing. #8078

Closed
thewan056 opened this issue Oct 6, 2023 · 2 comments · Fixed by #8080
Closed
Labels
enhancement New feature or request

Comments

@thewan056
Copy link

Describe what you are trying to accomplish and why in non technical terms
I want to be able to figure out what frigate thinks it is hearing with the audio detector. I am trying some obvious sounds that I know what that sound is, but frigate is not detecting them no matter how sensitive I set it or the threshold of that specific sound type. It maybe possible that what it thinks it hears is different from what i think i heard.

Describe the solution you'd like
Maybe an option to enable all types of audio events in the config or maybe in the camera debug UI that temporarily enables it and a section in the debug camera UI that shows what it thinks it hears. Maybe the top 3 or the top 5 with the highest percentage. Then we can narrow it down and use them in the config. Right now I am putting everything I think is related to that sound which I feel is too excessive.

Describe alternatives you've considered
Filling out the config with 500+ types of sounds and seeing what sticks. I know, but I am a little desperate after trying out so many sound types and seeing my list slowly and slowly expand.

Additional context
Add any other context or screenshots about the feature request here.

@thewan056
Copy link
Author

I was hoping for it to be part of the same debug ui for the current object detection instead of requiring users to wade through logs but i guess this is ok too.

@NickM-27
Copy link
Sponsor Collaborator

NickM-27 commented Oct 7, 2023

that would require a lot more data to be sent constantly via mqtt / webscoket which is inefficient and doesn't match other existing MQTT paradigms

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

Successfully merging a pull request may close this issue.

2 participants