[tool] [tutorial] Free AI Person Detection for Blue Iris

juched said:
That is what 5.3.3 does. My substream is used for motion and now it grabs the image from the main stream and sends that to AITool folder.
Click to expand...

Thats new. So can it record the substream continuously? I'll have a play around today.
 
I had to revert BI back from 5.3.3.6 to 5.3.2.11 because every time I got a motion trigger, BI would CTD.

Now that I'm back at 5.3.2.11, I'm getting tons of these errors. ??

DTypeTimeIdxDetailMemberName
Warning10/12/2020 6:14:39 PM231InsertHistoryItem>> Warning: It took a long time to add a history item @ 1053ms, (Count=16847, Min=1ms, Max=2145ms, Avg=80ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:49:46 PM230InsertHistoryItem>> Warning: It took a long time to add a history item @ 1238ms, (Count=16534, Min=1ms, Max=2145ms, Avg=85ms), StackDepth=22, TID=1, TCNT=24: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:47:31 PM229InsertHistoryItem>> Warning: It took a long time to add a history item @ 1198ms, (Count=16512, Min=1ms, Max=2145ms, Avg=87ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:44:09 PM228InsertHistoryItem>> Warning: It took a long time to add a history item @ 1391ms, (Count=16428, Min=1ms, Max=2145ms, Avg=82ms), StackDepth=22, TID=1, TCNT=30: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:43:33 PM227InsertHistoryItem>> Warning: It took a long time to add a history item @ 1485ms, (Count=16411, Min=1ms, Max=2145ms, Avg=80ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:39:05 PM226InsertHistoryItem>> Warning: It took a long time to add a history item @ 1451ms, (Count=16315, Min=1ms, Max=2145ms, Avg=75ms), StackDepth=22, TID=1, TCNT=28: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:35:44 PM225InsertHistoryItem>> Warning: It took a long time to add a history item @ 1777ms, (Count=16242, Min=1ms, Max=2145ms, Avg=77ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:25:04 PM224InsertHistoryItem>> Warning: It took a long time to add a history item @ 1164ms, (Count=15918, Min=1ms, Max=2145ms, Avg=95ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:23:39 PM223InsertHistoryItem>> Warning: It took a long time to add a history item @ 1464ms, (Count=15876, Min=1ms, Max=2145ms, Avg=97ms), StackDepth=22, TID=1, TCNT=30: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:11:44 PM222InsertHistoryItem>> Warning: It took a long time to add a history item @ 1380ms, (Count=15519, Min=1ms, Max=2145ms, Avg=105ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:06:57 PM221InsertHistoryItem>> Warning: It took a long time to add a history item @ 1312ms, (Count=15382, Min=1ms, Max=2145ms, Avg=108ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:58:28 PM220InsertHistoryItem>> Warning: It took a long time to add a history item @ 1119ms, (Count=15134, Min=1ms, Max=2145ms, Avg=111ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:58:18 PM219InsertHistoryItem>> Warning: It took a long time to add a history item @ 1415ms, (Count=15129, Min=1ms, Max=2145ms, Avg=111ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:57:38 PM218InsertHistoryItem>> Warning: It took a long time to add a history item @ 1418ms, (Count=15110, Min=1ms, Max=2145ms, Avg=107ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:55:50 PM217InsertHistoryItem>> Warning: It took a long time to add a history item @ 1198ms, (Count=15057, Min=1ms, Max=2145ms, Avg=106ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:48:49 PM216InsertHistoryItem>> Warning: It took a long time to add a history item @ 1178ms, (Count=14852, Min=1ms, Max=2145ms, Avg=102ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:39:49 PM215InsertHistoryItem>> Warning: It took a long time to add a history item @ 1372ms, (Count=14583, Min=1ms, Max=2145ms, Avg=83ms), StackDepth=22, TID=1, TCNT=28: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
 
WildDoktor said:
I had to revert BI back from 5.3.3.6 to 5.3.2.11 because every time I got a motion trigger, BI would CTD.

Now that I'm back at 5.3.2.11, I'm getting tons of these errors. ??

DTypeTimeIdxDetailMemberName
Warning10/12/2020 6:14:39 PM231InsertHistoryItem>> Warning: It took a long time to add a history item @ 1053ms, (Count=16847, Min=1ms, Max=2145ms, Avg=80ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:49:46 PM230InsertHistoryItem>> Warning: It took a long time to add a history item @ 1238ms, (Count=16534, Min=1ms, Max=2145ms, Avg=85ms), StackDepth=22, TID=1, TCNT=24: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:47:31 PM229InsertHistoryItem>> Warning: It took a long time to add a history item @ 1198ms, (Count=16512, Min=1ms, Max=2145ms, Avg=87ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:44:09 PM228InsertHistoryItem>> Warning: It took a long time to add a history item @ 1391ms, (Count=16428, Min=1ms, Max=2145ms, Avg=82ms), StackDepth=22, TID=1, TCNT=30: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:43:33 PM227InsertHistoryItem>> Warning: It took a long time to add a history item @ 1485ms, (Count=16411, Min=1ms, Max=2145ms, Avg=80ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:39:05 PM226InsertHistoryItem>> Warning: It took a long time to add a history item @ 1451ms, (Count=16315, Min=1ms, Max=2145ms, Avg=75ms), StackDepth=22, TID=1, TCNT=28: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:35:44 PM225InsertHistoryItem>> Warning: It took a long time to add a history item @ 1777ms, (Count=16242, Min=1ms, Max=2145ms, Avg=77ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:25:04 PM224InsertHistoryItem>> Warning: It took a long time to add a history item @ 1164ms, (Count=15918, Min=1ms, Max=2145ms, Avg=95ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:23:39 PM223InsertHistoryItem>> Warning: It took a long time to add a history item @ 1464ms, (Count=15876, Min=1ms, Max=2145ms, Avg=97ms), StackDepth=22, TID=1, TCNT=30: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:11:44 PM222InsertHistoryItem>> Warning: It took a long time to add a history item @ 1380ms, (Count=15519, Min=1ms, Max=2145ms, Avg=105ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:06:57 PM221InsertHistoryItem>> Warning: It took a long time to add a history item @ 1312ms, (Count=15382, Min=1ms, Max=2145ms, Avg=108ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:58:28 PM220InsertHistoryItem>> Warning: It took a long time to add a history item @ 1119ms, (Count=15134, Min=1ms, Max=2145ms, Avg=111ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:58:18 PM219InsertHistoryItem>> Warning: It took a long time to add a history item @ 1415ms, (Count=15129, Min=1ms, Max=2145ms, Avg=111ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:57:38 PM218InsertHistoryItem>> Warning: It took a long time to add a history item @ 1418ms, (Count=15110, Min=1ms, Max=2145ms, Avg=107ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:55:50 PM217InsertHistoryItem>> Warning: It took a long time to add a history item @ 1198ms, (Count=15057, Min=1ms, Max=2145ms, Avg=106ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:48:49 PM216InsertHistoryItem>> Warning: It took a long time to add a history item @ 1178ms, (Count=14852, Min=1ms, Max=2145ms, Avg=102ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:39:49 PM215InsertHistoryItem>> Warning: It took a long time to add a history item @ 1372ms, (Count=14583, Min=1ms, Max=2145ms, Avg=83ms), StackDepth=22, TID=1, TCNT=28: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Click to expand...

What is CTD? Try setting your pre trigger to 5 seconds at least.
 
Hello Everyone,
I have a new issue in migrating from AiTool 1.67 to the VorlonCD fork:
[23:18:35.343]: TelegramUpload> ERROR: Could not upload image C:\BlueIris\aiinput\AIGarageCam1.20201011_123151515.jpg to Telegram: chat not found [ChatNotFoundException] Mod: <TelegramUpload>d__32 Line:1460:33

I have the same Telegram token that I use in AiTool and same chat id: I have tried the chat id with and without -
Any thoughts? What am I missing or forgetting?

Thanks in advance.
Jim
 
Eatoff said:
How do we get the alert cancels to work? I have gone back to the single camera setup (from the duplicate camera setup), and I have the timeline full of all the false alerts.

this is what i have in the trigger cancel box:

{user}&pw={passwort}
Click to expand...
You need to send the trigger cancel, please see my earlier post at the top of this page.
http://xxxxxxx/admin?camera=XXX&flagalert=0&user=admin&pw=xxxx

You need to replace the XXX's with the relevant info
 
WildDoktor said:
I had to revert BI back from 5.3.3.6 to 5.3.2.11 because every time I got a motion trigger, BI would CTD.

Now that I'm back at 5.3.2.11, I'm getting tons of these errors. ??

DTypeTimeIdxDetailMemberName
Warning10/12/2020 6:14:39 PM231InsertHistoryItem>> Warning: It took a long time to add a history item @ 1053ms, (Count=16847, Min=1ms, Max=2145ms, Avg=80ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:49:46 PM230InsertHistoryItem>> Warning: It took a long time to add a history item @ 1238ms, (Count=16534, Min=1ms, Max=2145ms, Avg=85ms), StackDepth=22, TID=1, TCNT=24: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:47:31 PM229InsertHistoryItem>> Warning: It took a long time to add a history item @ 1198ms, (Count=16512, Min=1ms, Max=2145ms, Avg=87ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:44:09 PM228InsertHistoryItem>> Warning: It took a long time to add a history item @ 1391ms, (Count=16428, Min=1ms, Max=2145ms, Avg=82ms), StackDepth=22, TID=1, TCNT=30: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:43:33 PM227InsertHistoryItem>> Warning: It took a long time to add a history item @ 1485ms, (Count=16411, Min=1ms, Max=2145ms, Avg=80ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:39:05 PM226InsertHistoryItem>> Warning: It took a long time to add a history item @ 1451ms, (Count=16315, Min=1ms, Max=2145ms, Avg=75ms), StackDepth=22, TID=1, TCNT=28: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:35:44 PM225InsertHistoryItem>> Warning: It took a long time to add a history item @ 1777ms, (Count=16242, Min=1ms, Max=2145ms, Avg=77ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:25:04 PM224InsertHistoryItem>> Warning: It took a long time to add a history item @ 1164ms, (Count=15918, Min=1ms, Max=2145ms, Avg=95ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:23:39 PM223InsertHistoryItem>> Warning: It took a long time to add a history item @ 1464ms, (Count=15876, Min=1ms, Max=2145ms, Avg=97ms), StackDepth=22, TID=1, TCNT=30: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:11:44 PM222InsertHistoryItem>> Warning: It took a long time to add a history item @ 1380ms, (Count=15519, Min=1ms, Max=2145ms, Avg=105ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 5:06:57 PM221InsertHistoryItem>> Warning: It took a long time to add a history item @ 1312ms, (Count=15382, Min=1ms, Max=2145ms, Avg=108ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:58:28 PM220InsertHistoryItem>> Warning: It took a long time to add a history item @ 1119ms, (Count=15134, Min=1ms, Max=2145ms, Avg=111ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:58:18 PM219InsertHistoryItem>> Warning: It took a long time to add a history item @ 1415ms, (Count=15129, Min=1ms, Max=2145ms, Avg=111ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:57:38 PM218InsertHistoryItem>> Warning: It took a long time to add a history item @ 1418ms, (Count=15110, Min=1ms, Max=2145ms, Avg=107ms), StackDepth=22, TID=1, TCNT=26: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:55:50 PM217InsertHistoryItem>> Warning: It took a long time to add a history item @ 1198ms, (Count=15057, Min=1ms, Max=2145ms, Avg=106ms), StackDepth=22, TID=1, TCNT=27: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:48:49 PM216InsertHistoryItem>> Warning: It took a long time to add a history item @ 1178ms, (Count=14852, Min=1ms, Max=2145ms, Avg=102ms), StackDepth=22, TID=1, TCNT=29: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Warning10/12/2020 4:39:49 PM215InsertHistoryItem>> Warning: It took a long time to add a history item @ 1372ms, (Count=14583, Min=1ms, Max=2145ms, Avg=83ms), StackDepth=22, TID=1, TCNT=28: C:\AITOOL-VORLONCD\AITool.Database.SQLITE3
Click to expand...

Are you running the latest version as their was a version that did that if I recall correctly?
 
jj2473 said:
Hello Everyone,
I have a new issue in migrating from AiTool 1.67 to the VorlonCD fork:
[23:18:35.343]: TelegramUpload> ERROR: Could not upload image C:\BlueIris\aiinput\AIGarageCam1.20201011_123151515.jpg to Telegram: chat not found [ChatNotFoundException] Mod: <TelegramUpload>d__32 Line:1460:33

I have the same Telegram token that I use in AiTool and same chat id: I have tried the chat id with and without -
Any thoughts? What am I missing or forgetting?

Thanks in advance.
Jim
Click to expand...
Is your Token also correct. You've not mixed a O with a 0 or vice versa have you?
 
Does anyone have the cancel alert actually being sent? My URL works in browser but I never could figure out to get the tool to send the darn thing on a false positive. Feel like it's broken or I'm missing something to enable it in AI? but no one has confirmed either way really... lol I'm on latest built release.
 
B-Murda said:
Does anyone have the cancel alert actually being sent? My URL works in browser but I never could figure out to get the tool to send the darn thing on a false positive. Feel like it's broken or I'm missing something to enable it in AI? but no one has confirmed either way really... lol I'm on latest built release.
Click to expand...

I believe there’s a bug with the cancel URL field that [mention]Chris Dodge [/mention]is fixing in the next release.
 
VorlonCD: Is it possible to get more debug info about a Telegram failure? I have two cameras facing the street in front of my house. If a car drives by they each detect and send to Telegram (about 2 seconds between the two images). The first sends fine, the second one fails with this in the error log.

Also, is there a means to decipher the release version from Github and the one displayed on the front screen of the app? Mine is showing 1.67.8.33855. And it seems all of the version show a built on date of 9/30/2020.

[12.10.2020, 23:46:23]: Trigger>> -> ERROR sending image to Telegram.
[12.10.2020, 23:48:14]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 04:40:10]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 07:05:39]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 07:08:50]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 07:13:39]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 07:17:39]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 07:18:28]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 07:26:16]: Trigger>> -> ERROR sending image to Telegram.
[13.10.2020, 07:50:03]: Trigger>> -> ERROR sending image to Telegram.
{/QUOTE]
Click to expand...
 
blulite said:
VorlonCD: Is it possible to get more debug info about a Telegram failure? I have two cameras facing the street in front of my house. If a car drives by they each detect and send to Telegram (about 2 seconds between the two images). The first sends fine, the second one fails with this in the error log.

Also, is there a means to decipher the release version from Github and the one displayed on the front screen of the app? Mine is showing 1.67.8.33855. And it seems all of the version show a built on date of 9/30/2020.
Click to expand...
If you dont see the actual error above each of those lines and it just failed silently it probablly means your chatid or token is blank in settings. If not just try saving the camera again. I'll add better checking around that for next release.
 
Village Guy said:
Its not easy to read your error log but I do notice that it seems to be complaining about Deepstack registration. Have you registered deepstack and tested that you can bring it up on your browser without errors. In addition if you are starting from scratch you may wish to install the original app from @GentlePumpkin to become familiar with usage. I personally still use the original version at this time! For me reliability is more important than additional features. I plan to move to the more featured version in the next few months and am hoping by that time it will have most if not all the kinks ironed out.
Click to expand...
So the problem seems to have fixed itself.?? I swear my computer is possessed or something. But to answer your questions- yes Deepstack is registered and it brings everything up in a browser as it is supposed to. Not starting from scratch so much as I have been switching back and forth from the original and the VorlonCD version, I have had differing degrees of success with both versions and installing a clean copy of each version and just copying over the original files both "seem" to work...mostly. I went back wiped all (i think) the files installed the original again and (different issue) for 24 hours only 3 of my 6 cameras were sending alerts?? then this morning everything was working fine. WTH! :) I am perplexed, I checked the whole set up, BI, AI-Tool, Deepstack and could not see anything that was different than it ever was so I really don't know why it was screwing up but right now all is good. Think I will go back and install the latest VorlonCD version for S&G to see if it act any different.
 
Chris Dodge said:
If you dont see the actual error above each of those lines and it just failed silently it probablly means your chatid or token is blank in settings. If not just try saving the camera again. I'll add better checking around that for next release.
Click to expand...
Telegram is working all of the time, except when a car passes in front of my house. I see the two “flagged” events in BI, I can see the two events in the AItool history. I just never get the second Telegram message and I get the error listed above in the error log.
 
WildDoktor said:
CTD = Crash to Desktop
My pre-trigger is 16 seconds on the sd camera (not sure I need that) and 20 seconds on the hd camera.
Click to expand...
Ok, thanks. I worked with Ken to have a CTD fixed when my cameras triggered in 5.3.3.2. He fixed it in 5.3.3.4 and it doesn't CTD anymore. However, I did turn off the Create Hi-Res alert image checkbox as I was changing my config. Do you have that checkbox on?
 
juched said:
Ok, thanks. I worked with Ken to have a CTD fixed when my cameras triggered in 5.3.3.2. He fixed it in 5.3.3.4 and it doesn't CTD anymore. However, I did turn off the Create Hi-Res alert image checkbox as I was changing my config. Do you have that checkbox on?
Click to expand...
Interesting; yes, I have that checkbox on. I suppose I could update BI and uncheck that box and see what happens, but that won't happen until probably tomorrow night.
 
blulite said:
Telegram is working all of the time, except when a car passes in front of my house. I see the two “flagged” events in BI, I can see the two events in the AItool history. I just never get the second Telegram message and I get the error listed above in the error log.
Click to expand...

I just switched back to 1.67. I get both alerts now. Nothing has changed except the aitool version which I am running.
 
Question for anyone that knows.

So I have my trigger and cancel alert URLs setup and working now.
I have my alerts set to re-trigger after 3 seconds unless active still and my image set to capture every 3.5 seconds.
The issue I have is sometimes the trigger image does not match the AI image because of delay processing or the fact that BI may only show one on the alert but it took 2 images.

For example BI takes snap, adds to thumbnail, while AI is processing another image is taken. The first image ends up as canceled because say a car JUST started into scene so motion was hit but not enough for AI to know it's a car. The second image knows it's a car so now it triggers. Well BI only made the one entry despite 2 images so when it triggers the email is the first image with maybe nothing in it of enough value. Funny part now is the alert is cleared from timeline due to the cancel but flagged cause I'm still using flags for trigger at the moment but this is because the same issue, multiple images but 1 entry in BI.

Anyway I know in the example you could just modify the motion to require being in the view more before trigger but that was just my example. It happens in other cases where you wouldn't want to do this so trying to understand if my times need to be adjusted or some way to make BI use all the images and not just the one etc.

What am I doing wrong or can I change to improve this? I only want multiple images in case the first misses. I may see if Ken can set an image time limit too (for times when it is constant motion I don't need non-stop alerts and maybe dynamic mask don't help since it can move a lot). Like mowing the yard and being lazy to not want to disable alerts. Well I can get hundreds of emails LOL. I only need 1 if it's a legit one and still part of the same alert but that's another issue.

Thanks!
 
You must log in or register to reply here.
Top Bottom