[Config Support]: Zone configuration, coordinate system changes size periodically #12026
Answered
by
NickM-27
Basketkase
asked this question in
Config Support
Replies: 1 comment 3 replies
-
this can be due to the way that the detect resolution is found automatically, and one of the reasons that it is recommended to set detect resolution explicitly. In any case, the next version of frigate saves the coordinates in a relative format so the input resolution does not matter |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
Hello!
I'm trying to configure a zone for my backyard, but the coordinates that are being used seem to change sometimes between 720p and the actual camera resolution of 2592x1944.
The first time I configured the zone in the config tool the points generated were positioned within 1280x720. But when I saved the config and restarted the zone was scaled way down in the debug view because (I assume) the camera's resolution is 2592x1944.
Here's the config when it was using the lower resolution:
1227,720,959,256,460,173,0,543,0,720
When I reconfigured the zone again the zone creator used the correct resolution to set the points. After a save and restart it showed up properly in the ui and worked for a week or 2.
Here's the config with the higher resolution:
coordinates: 2508,1944,1954,716,887,517,0,1461,0,1944
A few days ago however it seems like the zones are back to using 1280x720 as the size of the frame and my zone is scaled up.
Does anyone have any idea why the zones are changing like this? The mse stream view each time displays the correct higher resolution when viewed so I don't think the camera is changing its resolution over time.
I'm not sure what extra info or screenshots are needed, I can share a screenshot of the debug view with the scaled up zone if that would be helpful.
My setup (which isn't in the dropdowns):
TrueNAS Scale
I'm not sure what logs would be relevant, but taking a look at my logs there's lots of errors relating to the camera stream! Which is strange because the stream works fine from Home Assistant and in the frigate ui... I attached an hour or 2 of logs from today just in case they contain something helpful.
Version
0.13.2-6476f8a
Frigate config file
Relevant log output
Frigate stats
Operating system
Other
Install method
Docker Compose
Object Detector
Coral
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions