mirror of
https://github.com/blakeblackshear/frigate.git
synced 2026-06-22 04:11:53 +03:00
e9432d55e8
Some checks are pending
CI / AMD64 Build (push) Waiting to run
CI / ARM Build (push) Waiting to run
CI / Jetson Jetpack 6 (push) Waiting to run
CI / AMD64 Extra Build (push) Blocked by required conditions
CI / ARM Extra Build (push) Blocked by required conditions
CI / Synaptics Build (push) Blocked by required conditions
CI / Assemble and push default build (push) Blocked by required conditions
get_relative_coordinates() previously logged "Not applying mask due to invalid coordinates. X,Y is outside ..." without naming the camera, so on a multi-camera setup the user had to guess which one to fix. Add an optional camera_name kwarg with default "" (no behavior change for existing callers). The global object-mask path in FrigateConfig.validate_config passes camera_name=camera_config.name since it already has it in scope, so legacy configs with absolute pixel coordinates now get an actionable log line: Not applying mask due to invalid coordinates for camera back. 9000,9000 is outside of the detection resolution 800x400. Use the editor in the UI to correct the mask. Existing wording is preserved verbatim except for the inserted " for camera <name>" segment. Runtime behavior is unchanged. Co-authored-by: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| camera | ||
| __init__.py | ||
| auth.py | ||
| base.py | ||
| camera_group.py | ||
| classification.py | ||
| config.py | ||
| database.py | ||
| env.py | ||
| logger.py | ||
| mqtt.py | ||
| network.py | ||
| profile_manager.py | ||
| profile.py | ||
| proxy.py | ||
| telemetry.py | ||
| tls.py | ||
| ui.py | ||