@NickM-27 commented on GitHub (Jun 28, 2025):
If it's the embeddings process using the CPU then it's impossible to be related to motion detection
@MarcA711 commented on GitHub (Aug 6, 2025):
AFAIK, this file is required by Rockchip's Toolkit for neural networks. Without this file, the Toolkit…
@github-actions[bot] commented on GitHub (Sep 6, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@NickM-27 commented on GitHub (Jun 30, 2025):
Thanks for the thoughtful feature request, unfortunately there are some things here that make this not ideal:
The face library page should be used…
@NickM-27 commented on GitHub (Jul 16, 2025):
can you not just copy the value of that file somewhere else, and map it from that file to /proc/device-tree/complatible in the container?
@NickM-27 commented on GitHub (Jun 28, 2025):
embeddings has nothing to do with motion detection. You should create a support discussion, and take a look at the docs https://docs.frigate.video/con…
@noitman commented on GitHub (Jun 28, 2025):
I am 100% certain that motion detection is causing the spike in CPU usage, because I observed the same result even when semantic search was disabled.
@mikenorgate commented on GitHub (Jul 17, 2025):
Unfortunately not, Kubernetes takes full control of /proc and can't map anything there
@NickM-27 commented on GitHub (Aug 6, 2025):
@MarcA711 let me know what you think on this
@hawkeye217 commented on GitHub (Nov 19, 2025):
Your GPU likely can't process streams of that resolution. Additionally, as noted on your closed discussion, this resolution probably higher than…
@NickM-27 commented on GitHub (Nov 19, 2025):
If I set the resolution to 1280x720, would that even help LPR be able to see a license plate better?
in general yes, if the other stream is not a…
@broyuken commented on GitHub (Nov 19, 2025):
I set the detect resolution to 4096x1248 and my logs just fill up and the camera stops working