How about you remove the cutom models from the folder you don't need. I've always done that. That should work, correct?
I wish Ken would fully clear this up.How about you remove the cutom models from the folder you don't need. I've always done that. That should work, correct?
Email him and ask.I wish Ken would fully clear this up.
I have most cameras using "ipcam-general" , some using "ipcam-combined", one using "license-plate" and one using "delivery". I just want to make sure that they aren't going to start using all 4 on all cameras since I've specified the model I want to use for each camera. So is this behavior changed now, and if so why?
Some cameras stop as soon as they've found an object, others keep going because I have some non-existent object specified in the "to cancel" field. Again, is this behavior changed and if so why?
I don't usually update unless it's necessary, so I'm definitely holding off. But at some point if I do, I need to know if/how this is changing.
Can't answer the "why" part, but this change occured with 5.8.7.8, see below:Some cameras stop as soon as they've found an object, others keep going because I have some non-existent object specified in the "to cancel" field. Again, is this behavior changed and if so why?
Can't answer the "why" part, but this change occured with 5.8.7.8, see below:
5.8.7.8
Improvements have been made to the heuristics used when deciding which image among all analyzed to use for final alert confirmation or cancellation. It is no longer necessary to place a “dummy” object into the the “to cancel” box for processing to continue regardless of a single confirmed object.ipcamtalk.com
Hmm...I'm surprised that is still working: from the sounds of that 5.8.7.8 write-up it shouldn't actually add any additional analysis by doing so. Strange that you can still "force" the added images.Sadly this feature didn't improve my image for selection and I need to keep a dummy object in the to cancel.
Hmm...I'm surprised that is still working: from the sounds of that 5.8.7.8 write-up it shouldn't actually add any additional analysis by doing so. Strange that you can still "force" the added images.
Perhaps what happens in your case is that the "best" image occurs towards the end of a long string of consecutive analyses.
Same problem with 5.8.8.latest. First time the entire PC locked up and I had to force a power off and restart. Seven and nine days later the PC restarted after running out of virtual memory - somewhere around 80 GB. Both time the committed memory was less than 12 GB and holding steady the night before. Looking at the log files a bunch of processes could not obtain more memory. When this started happening BI was using ~75GB. within an hour BI was using an additional 4-5GB. Very soon after the second warning message the PC restarted.For those that grab updates just because (as I do because I'm not quite so worried about bad things happening around here that I'd miss footage of), and I enjoy checking out the new changes. None of the 5.8.8.x has worked for me so far up to and including 5.8.8.6 as BI just randomly shuts down with any of them. No biggie, since BIT starts it right back up. But, each time I've downgraded back to 5.8.7.11, which works very well (for me), any camera that is using another camera's Audio has the "Enable audio channel" unticked, so I need to go into each of them and re-tick it. Just a head's up...