Sounds like a good plan. Like I posted, dark.pt seems to work better both day and night. I'll go to each camera and enter Objects:0. Like this?Yes because it is running two models.
I found that dark works better even during the day. So in the camera AI tab under Custom models, put in Objects:0 and it will skip the default detection. Or put in dark:0 during the day so it only uses default.
Only use one model and the detection will come down. The :0 tells it to ignore that model.
Other settings look okay?Yes, that will take care of it!
I've emailed Ken... we'll see.WOW - something is way out of whack. Those times are way too long.
Have you reported it? I haven't heard back from support yet.I'm seeing similar results. Simply adding the dark.pt file to MyModels results in non dark processing jumping from about 200ms to 3000ms+ even when I don't add dark to the camera AI custom models section.
Yes. I sent a bug report about 5 minutes ago.Have you reported it? I haven't heard back from support yet.
So if I have a custom model in MyModels and don't list that model in the "Cutom models" box of a camera, the model is still used any ways? That doesn't make sense.It will use any model in the "models' directory. To prevent that put a semicolon, ; , in the models box of the AI setup on each camera.
That's the point. I haven't mentioned ANY models in the AI setup of any camera. Simply turning on the "Use custom model folder" in the global settings and adding dark.pt to that folder results in DS going from 200 ms to 5000 ms for image processing.If you've mentioned models in the AI setup, which you sort of have to do when using models, it will always look there for a model when analyzing. Give the semicolon a try.