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

Run detection on image before sending to Frigate+ #12605

Closed
knobunc opened this issue Jul 25, 2024 · 1 comment
Closed

Run detection on image before sending to Frigate+ #12605

knobunc opened this issue Jul 25, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@knobunc
Copy link

knobunc commented Jul 25, 2024

Describe what you are trying to accomplish and why in non technical terms
I want to be able to have full types and boundaries visible in training images to be sent Frigate+ so that I can more easily and accurately train.

I have several cars that are always present on one of my more active cameras, so when I need to train an image from that camera, I have to accurately select the car and license plates, along with whatever I am really training for. Often two people, their faces, and a dog.

It would be excellent if all of that data could be sent to Frigate+ rather than just the one boundary and type that happens today.

Describe the solution you'd like
I think it would make sense to run a detection for all types and boundaries visible in the image locally before it is sent to Frigate+.

Describe alternatives you've considered
The Frigate+ server could run the detection, but that needs a bunch of computation and needs the model to be present on the server along with acceleration hardware.

@knobunc knobunc added the enhancement New feature or request label Jul 25, 2024
@NickM-27 NickM-27 added the duplicate This issue or pull request already exists label Jul 25, 2024
@NickM-27
Copy link
Collaborator

This is a duplicate of #8229

@NickM-27 NickM-27 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants