sebastiantombs
Known around here
Read the rest of my last post. BI initializes DS at startup telling it to use custom models and where they are.
Read the rest of my last post. BI initializes DS at startup telling it to use custom models and where they are.
So you can specify which custom model for each situation and ignore the rest.
So are you saying every camera AI instance uses all custom models unless you specify which one you want and then it only uses what you specify for each camera?
That is correct. I am using custom models and if I tell each camera to only use one model, my detection times are the same as if I didn't have the custom model.
So if I put in custom models box for the a particular camera dark;objects:0 then it only uses the dark model and the times are the same as prior to having the custom model.
This setup then allows one to only use dark at night and default DS during the day. In my field of view the custom model seems to work best, so I have objects:0 in most of my cameras.
So you know, without a doubt that it downloaded a perfect image and when it was moved into your model directory that was also a perfect operation. Confirming it's good simply by downloading again seems to be a fairly painless, quick double check to me. Especially given that you're having a problem not many others have.
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.