NOTE: This is in reference to a rebuild compile for a Synology NAS....
I managed to get the rebuild branch to compile all the way through. Now, when I try to use the tensorflow models (which I got from the script) using the config (from the script), I get this error...
Still works like a champ with the standard tflite detector... I'm SO close! Still get warnings about SSE4.1 and SSE4.2 as well, but that seems to be common as I see other people commenting on it.
Update - Did a new build overnight, just in case the interrupted build was the problem. Used the 'no-cache' flag to force it to build clean. No difference. The tflite detector functions fine but the tensorflow detector throws 404's everywhere. It's a step in the right direction though. At least it doesn't "blow up" like it did before.
Figured out you have to leave all of the lines in the config.yaml file. You can't comment out the stuff you're not using. This one is on me.
NOTE: This is in reference to a rebuild compile for a Synology NAS....
I managed to get the rebuild branch to compile all the way through. Now, when I try to use the tensorflow models (which I got from the script) using the config (from the script), I get this error...
INFO server/server.go:138 HTTP Request {"status": 404, "took": 0.018610838, "request": "/detect", "method": "POST", "package": "server.request", "request-id": "DS418Play/InkKHkGhVK-000008", "remote": "192.168.0.3:46276"}
The config file is:
doods: detectors:
Still works like a champ with the standard tflite detector... I'm SO close! Still get warnings about SSE4.1 and SSE4.2 as well, but that seems to be common as I see other people commenting on it.
Update - Did a new build overnight, just in case the interrupted build was the problem. Used the 'no-cache' flag to force it to build clean. No difference. The tflite detector functions fine but the tensorflow detector throws 404's everywhere. It's a step in the right direction though. At least it doesn't "blow up" like it did before.
Figured out you have to leave all of the lines in the config.yaml file. You can't comment out the stuff you're not using. This one is on me.