Thanks for the reply. I do have objects:0 as indicated in my previous posts. It does not appear to be working as some other posters have indicated as well.you need:
objects:0
not
object:0
check that
One thing I hadn't considered is the possibility that the parameter might be case-sensitive (Objects:0 vs. objects:0). I'll try all lower-case and see if that makes a difference.you need:
objects:0
not
object:0
check that
Thank you!Confirmed that the detection model string is case-sensitive. After changing from Objects:0,dark to objects:0,dark the dark model is the only one running.
Yes, that will take care of it!
still not working...Guys, if you don't want to use the dark model in a particular schedule, just put a semi colon in the models box on the AI tab of the camera. No need for names, objects or numbers at all.
I tried ";" only / "dark:0;" / "dark:0" => same resultJust a semi colon, not spaces, and remove any objects associated with the dark model, IE Car, People, etc. Dark model objects all start with a capital letter.
Punctuation symbols may be an issue for international installs. To disable custom models you need only enter a non-existent custom model name. Try entering ‘none’ instead of the semicolon.I tried ";" only / "dark:0;" / "dark:0" => same result
set main_path=C:\DeepStack\MyModels
to reflect the path you've entered in Blue Iris Settings > AI tab > 'Custom models folder'.set show_option=1
DS_custom_toggle.bat [hide|unhide]
.