-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use hi-res stream for plate recognition. #36
Comments
Sounds to me like you need to use the main stream in frigate config. |
Running detection on the main stream in Frigate is enormously CPU intensive. Even though I have tuned the installation as per Frigate documentation, using this just for plate recognizer when object detection itself is working fine on the low-res stream is a massive waste of resources. Double-take listens for events from Frigate using the low-res stream and when it receives one, accesses the camera direct for a high-res snapshot which it uses for face recognition - discussion here. This would be a great addition to plate-recognizer and I'm sure a lot of people would use it. |
I agree with @RutgerDiehard, rather then using the snapshot it would be better to use the /clips/camera-eventid-clean.png, this is the full resolution image and also without any bounding box. I would say there is a much better chance of getting a plate on that then those grainy snapshots. |
I think the problem with that option is, the clean png isn't available until the event has ended. I guess we could use it if it's available and if not use the snapshot.. |
Hmm that's a good point. When does the event end, is it when a car becomes stationary or out of the picture? Maybe we can use snapshots for cars in motion and the full resolution image for cars that are stationary. |
"The event ends if the tracked object goes missing for more frames than the configured max_disappeared value." That was from Blake a while ago |
Cool. |
That'll only work while the event is in progress unfortunately. |
Ah ok - yeah I figured out as much. Guess I'll have to disable bounding box in snapshots per camera feed. Cheers. |
That's what I do. I also run my LPR camera on the main stream to get the best quality image for processing. |
What LPR camera are you using ? |
|
Very nice, that's the exact one I was looking at as well. 60mm varifocal I believe ? And not un-affordable either. How is it working for you ? I think the biggest issue with these is getting the angle right, but maybe not so much a problem with these. |
Once I got all the camera settings dialed in for my environment, it's been an amazing camera for LPR. You can't go wrong with it especially if you're willing to play around with the settings to get it correct. See the below link for discussions about it. https://ipcamtalk.com/threads/mini-review-5241-z12e-s2-replacement-for-the-5241-z12e.71898/ |
Hi! Couldn't we implement the
like doubletake has - to enable high-res snapshots from an external snapshot URL? This way the mainstream doesn't need to be used? |
As an update to this, I've managed to work around the low resolution of the Reolink substream (and poor plate recognition success) by using ffmpeg to re-encode the main 4k stream into a lower resolution detect stream (1280x720) - but still higher resolution than the substream from the camera - that plate recognition is much, much happier with. I do this in the go2rtc section of the Frigate config:
By using The camera section in Frigate config then looks like this:
|
I have a 4K camera that's used to capture person and car objects on my drive. Object detection is fairly reliable using the low-res stream from the camera fed to Frigate. However, plate recognition is very unreliable due to the low-res snapshot.jpg from Frigate. Other Frigate integrations (such as Double-Take for face recognition) allows high-res jpg captures directly from a camera for the highest quality processing once a Frigate snapshot.jpg event is received.
Is this something that is available for plate-recongnizer?
The text was updated successfully, but these errors were encountered: