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

robpur

Getting comfortable
Joined
Jul 31, 2014
Messages
274
Reaction score
1,321
Location
Washington State
Could it be the ports that the camera uses?
As in a possible port conflict? No. Perhaps I wasn't clear when I said that AI fails when the camera is connected. What I meant is that AI fails when the camera is connected to the AI system, not just to the network. The new camera and AI work fine running beside each other, as long as I don't tell BI to drop the new camera images into the aiinput folder and define the camera in AI Tool then all is well. Currently I'm running zone crossing on the new camera until I can get the AI issue worked out.
 

balucanb

Getting the hang of it
Joined
Sep 19, 2020
Messages
146
Reaction score
23
Location
TX
Since I am new to Docker I have a question, for those running Docker, Do you use Kubernetes and do you deploy docker stacks to kubernetes by default? Should you? what is the benefit? Why would you not do this? Thanks

Also what have messed up here? there is no longer any info showing (deepstack tab) on name and version and the log is full of errors Can you help please.
AI-log.JPGDS tab.JPG
 
Last edited:

austwhite

Getting the hang of it
Joined
Jun 7, 2020
Messages
93
Reaction score
92
Location
USA
I have just installed this tool, following the guide and also following Rob's (The Hookup) YouTube video on the same.
I have everything working, but I find that it takes some time for Blue Iris to trigger. I am using a clone camera as I am recording a substream 24/7 from this camera as well as using it for a trigger.

Has anyone else experienced such delays with Blue Iris initially triggering and saving the image?

As a note: I have Deepstack running on a Ubuntu VM successfully and the AITool is running on the same machine as Blue Iris. The delay seems to be the trigger from Blue Iris, not the processing of the image.
 

kosh42efg

n3wb
Joined
Aug 14, 2020
Messages
29
Reaction score
13
So the saving of the image into the folder from BI? Have you changed the time down from the default 1 minute in the jpeg options?
 

austwhite

Getting the hang of it
Joined
Jun 7, 2020
Messages
93
Reaction score
92
Location
USA
So the saving of the image into the folder from BI? Have you changed the time down from the default 1 minute in the jpeg options?
I have the default 1 minute set down to 5 seconds, and the break time on the trigger is 4 seconds.
On the motion sensor settings, I have it set to a fairly sensitive level with a min object size of 300 and min contrast 27.
I also unticked all advanced options.
Edit: Make time is set to 0.5 in Motion Sensor options.
 

joshwah

Pulling my weight
Joined
Apr 25, 2019
Messages
298
Reaction score
146
Location
australia
Anyone have any ideas why everytime I rebuild a new release and copy and paste the files into my live folder i lose all my camera settings? i.e. cancel URL, trigger URLs, etc. it's soo annoying needing to redo them every few days...
 

ZAPme

n3wb
Joined
Dec 15, 2020
Messages
6
Reaction score
0
Location
USA
New guy here. Sorry if this has been explained already - I could not find anything.... :confused:
Looking for AITool / docker HELP running deepquestai/deepstack:gpu and deepquestai/deepstack:latest - the cpu version (latest) works fine in docker (WSL2/Ubuntu). I cannot get the gpu version to receive data from AITool. I configured AI Server URLs as localhost:8383,localhost:8384 for cpu and gpu respectively.
I am getting this error in AITool ...Problem with AI URL: All is running on the same WIN10 PC. Why is the cpu version connecting fine on port 8383 but not the gpu version on port 8384 ???
Thank you for any hints... !
 

robpur

Getting comfortable
Joined
Jul 31, 2014
Messages
274
Reaction score
1,321
Location
Washington State
Testing to resolve the all URLs are in use message has continued. I ran with my three old Hikvision cameras for nearly two days without trouble. During that time the new Reolink camera in the driveway was saving images into the aiinput folder, and it was defined in AI Tool, but a box was unchecked so that the images would not be processed by AI. Today I checked the box to start processing the driveway images and the problem came back. The three Hikvision cameras work just fine until I walk in front of the new camera. At that point AI Tool sends the image to DS, receives a result, sees a positive response, and then performs an alert action. Everything looks good up until that point. However, after processing starts for the next image the log shows "All URL's are in use or disabled, waiting...|506|5||17" and AI processing will not continue until I restart AI Tool.

I've tried resizing the image and changing their quality but that didn't help. I tried a different model of Reolink camera and also a spare Hikvision but they all behave the same way. At this point I can't find a way to add a fourth camera to the AI system.
 

Tinbum

Pulling my weight
Joined
Sep 5, 2017
Messages
446
Reaction score
126
Location
UK
For those running the Windows GPU I noticed Deepstack only uses about 1% of the GPU processing power so this could be of interest if you run the VorlonCD version of AITool. Note AITool will only start one instance at the moment.

From @OlafenwaMoses

You can run N number of DeepStack instances as far as you use different ports for each of the instances.

e.g

deepstack --VISION-DETECTION True --PORT 81

deepstack --VISION-DETECTION True --PORT 82

deepstack --VISION-DETECTION True --PORT 83

deepstack --VISION-DETECTION True --PORT 84

deepstack --VISION-DETECTION True --PORT 85
 

balucanb

Getting the hang of it
Joined
Sep 19, 2020
Messages
146
Reaction score
23
Location
TX
Testing to resolve the all URLs are in use message has continued. I ran with my three old Hikvision cameras for nearly two days without trouble. During that time the new Reolink camera in the driveway was saving images into the aiinput folder, and it was defined in AI Tool, but a box was unchecked so that the images would not be processed by AI. Today I checked the box to start processing the driveway images and the problem came back. The three Hikvision cameras work just fine until I walk in front of the new camera. At that point AI Tool sends the image to DS, receives a result, sees a positive response, and then performs an alert action. Everything looks good up until that point. However, after processing starts for the next image the log shows "All URL's are in use or disabled, waiting...|506|5||17" and AI processing will not continue until I restart AI Tool.

I've tried resizing the image and changing their quality but that didn't help. I tried a different model of Reolink camera and also a spare Hikvision but they all behave the same way. At this point I can't find a way to add a fourth camera to the AI system.
So robpur I was having a similar issue but want to clarify before I give you bad info on what I did 1. the "4th" camera is actually loaded just throwing errors or 2. You can only add 3 total cameras to the system?
 

Tinbum

Pulling my weight
Joined
Sep 5, 2017
Messages
446
Reaction score
126
Location
UK
I've tried to replicate it and it also happens with mine as well. It doesn't happen with the CPU' Docker deepstack but I've not tried it with the Windows CPU version.

I don't think it's creating much of a problem as its less than a half a second difference but I've opened an issue on Github.
They are working on this issue.
 

Ripper99

n3wb
Joined
Dec 12, 2020
Messages
10
Reaction score
2
Location
Canada
I have just installed this tool, following the guide and also following Rob's (The Hookup) YouTube video on the same.
I have everything working, but I find that it takes some time for Blue Iris to trigger. I am using a clone camera as I am recording a substream 24/7 from this camera as well as using it for a trigger.

Has anyone else experienced such delays with Blue Iris initially triggering and saving the image?

As a note: I have Deepstack running on a Ubuntu VM successfully and the AITool is running on the same machine as Blue Iris. The delay seems to be the trigger from Blue Iris, not the processing of the image.
When you followed the tutorial by The Hookup have "enable motion detector" and "direct to disk recording" as options for your substream cameras however later in the video for the HD stream cameras that will produce recordings based on triggers you do not clone these cameras because if you did then you would have both "enable motion detector" and "direct to disk recording" and you don't need that on the HD streams.

Watch the video here and you do NOT want motion selected on HD stream cameras and if you are cloning from other cams you will have that. I followed the video The Hookup has and have Deepstack running in docker on a ESXI server and then I have BlueIris and AItool running on the same machine with 14 cameras and everything seems to work fine and trigger right away, I also reviewed this guys notes to confirm everything
 

robpur

Getting comfortable
Joined
Jul 31, 2014
Messages
274
Reaction score
1,321
Location
Washington State
So robpur I was having a similar issue but want to clarify before I give you bad info on what I did 1. the "4th" camera is actually loaded just throwing errors or 2. You can only add 3 total cameras to the system?
If three of my cameras are set up in AI Tool then everything works correctly. If I add a fourth camera in AI Tool everything works correctly until the fourth camera sees motion. After that AI Tool stops sending images to DS.

I've reported the issue on Gethub and have been pointed to a development version of AI Tool that has a very different way of adding DS URLs but I haven't had time to try it yet.
 

balucanb

Getting the hang of it
Joined
Sep 19, 2020
Messages
146
Reaction score
23
Location
TX
If three of my cameras are set up in AI Tool then everything works correctly. If I add a fourth camera in AI Tool everything works correctly until the fourth camera sees motion. After that AI Tool stops sending images to DS.

I've reported the issue on Gethub and have been pointed to a development version of AI Tool that has a very different way of adding DS URLs but I haven't had time to try it yet.
Ok. I was having a similar issue however I have 8 cameras, I can't say for sure because I didn't put 2&2 together until I read your post, but with me I added a new camera which was a Reolink, after I added it in BI, I noticed in AI-Tool the trigger statement had been added automatically and was different than all my others, again I did not add it it just was there, I left it alone B/C I was getting alerts in Telegram but that is when I started getting the same error as you, I changed the trigger on the Reolink to match all the other cameras and I didn't see the error anymore. *** But I was having unrelated computer issues on my BI box and during the same time I did a clean install and started over, I did change all the triggers AFTER the re install also and I have not seen the error since. My explanation /(maybe) answer could be wrong but you may want to check it and see if it helps.
 

robpur

Getting comfortable
Joined
Jul 31, 2014
Messages
274
Reaction score
1,321
Location
Washington State
Ok. I was having a similar issue however I have 8 cameras, I can't say for sure because I didn't put 2&2 together until I read your post, but with me I added a new camera which was a Reolink, after I added it in BI, I noticed in AI-Tool the trigger statement had been added automatically and was different than all my others, again I did not add it it just was there, I left it alone B/C I was getting alerts in Telegram but that is when I started getting the same error as you, I changed the trigger on the Reolink to match all the other cameras and I didn't see the error anymore. *** But I was having unrelated computer issues on my BI box and during the same time I did a clean install and started over, I did change all the triggers AFTER the re install also and I have not seen the error since. My explanation /(maybe) answer could be wrong but you may want to check it and see if it helps.
You may be on to something there. I just checked and I see that I made a stupid mistake. In older versions of AI Tool the trigger line was out in the open where you could see it. Now you have to click on the Settings button next to Actions before entering the Trigger URLs. When setting up the new camera I forgot all about the trigger URL and didn't enter my user name and password. I just fixed the line but I'm not at home and therefore can't do a walk test. I'll give it a try after work. Thanks for the tip!
 

CAL7

Getting the hang of it
Joined
Nov 26, 2020
Messages
64
Reaction score
26
Location
Florida
I endorse the Dane Creek notes. As a total newbie, I found his hints to be very helpful. His process is 95% from The Hookup video, but he incorporates some newer techniques since the video was produced.

... do not clone these cameras because if you did then you would have both "enable motion detector" and "direct to disk recording" and you don't need that on the HD streams.
@Ripper99 Would you please clarify "clone" terminology? Following The Hookup video, I set mine with one camera using the HD mainstream and a second that uses the low-res substream as its mainstream. I believe everything is working as I intended, i.e. the low-res records continuously and uses motion detection (with AITOOL & Deepstack) to trigger the HD camera. From your comment I quoted above, do I interpret this as NOT a cloned camera setup?
 

austwhite

Getting the hang of it
Joined
Jun 7, 2020
Messages
93
Reaction score
92
Location
USA
When you followed the tutorial by The Hookup have "enable motion detector" and "direct to disk recording" as options for your substream cameras however later in the video for the HD stream cameras that will produce recordings based on triggers you do not clone these cameras because if you did then you would have both "enable motion detector" and "direct to disk recording" and you don't need that on the HD streams.

Watch the video here and you do NOT want motion selected on HD stream cameras and if you are cloning from other cams you will have that. I followed the video The Hookup has and have Deepstack running in docker on a ESXI server and then I have BlueIris and AItool running on the same machine with 14 cameras and everything seems to work fine and trigger right away, I also reviewed this guys notes to confirm everything
I didn't mean clone as in cloning with in BLue Iris, I meant duplicate camera. Either way, the issue I have is not excessive motion detection, it is delayed processing of the motion. The whole thing works as expected, except it takes 5 seconds before the first motion event triggers the HD recording.

Sorry for the confusion of terms
 

austwhite

Getting the hang of it
Joined
Jun 7, 2020
Messages
93
Reaction score
92
Location
USA
I endorse the Dane Creek notes. As a total newbie, I found his hints to be very helpful. His process is 95% from The Hookup video, but he incorporates some newer techniques since the video was produced.



@Ripper99 Would you please clarify "clone" terminology? Following The Hookup video, I set mine with one camera using the HD mainstream and a second that uses the low-res substream as its mainstream. I believe everything is working as I intended, i.e. the low-res records continuously and uses motion detection (with AITOOL & Deepstack) to trigger the HD camera. From your comment I quoted above, do I interpret this as NOT a cloned camera setup?
@Ripper99 is correct. My use of the word "clone" was not actually a clone camera. Blue Iris has a function for cloning a camera. What Rob (and myself and others following the same process) are doing is actually creating a new camera in Blue Iris with just the substream for the detection and 24/7 recording. A true clone camera would be cloned within BI with identical streams to the original camera. This would not work for Rob's 24/7 stream as the HD of the clone would be recorded 24/7. A clone would only be used if you are only recording motion events the AITool flags.
I will use the clone option for my indoor cameras when I set them up as they do not need to record 24/7.
 
Last edited:

robpur

Getting comfortable
Joined
Jul 31, 2014
Messages
274
Reaction score
1,321
Location
Washington State
Ok. I was having a similar issue however I have 8 cameras, I can't say for sure because I didn't put 2&2 together until I read your post, but with me I added a new camera which was a Reolink, after I added it in BI, I noticed in AI-Tool the trigger statement had been added automatically and was different than all my others, again I did not add it it just was there, I left it alone B/C I was getting alerts in Telegram but that is when I started getting the same error as you, I changed the trigger on the Reolink to match all the other cameras and I didn't see the error anymore. *** But I was having unrelated computer issues on my BI box and during the same time I did a clean install and started over, I did change all the triggers AFTER the re install also and I have not seen the error since. My explanation /(maybe) answer could be wrong but you may want to check it and see if it helps.
Did a test and the trigger was the issue. All four of the cameras are working with AI now. It was a dumb mistake that cost me time and effort. I guess I wasn't balicudb at the moment :)

As mentioned the development version of AI Tool has a different way of specifying AI server URLs. It looks like not only can you add multiple servers as you could before, but you can also associate cameras with specific servers. We haven't seen an official AI Tool release for a while but it's good to know that progress is being made and good things are on the way. The development version supports AWS Rekognition Server and DOODS AI Server as well as DeepStack.

1609196565240.png
 

CAL7

Getting the hang of it
Joined
Nov 26, 2020
Messages
64
Reaction score
26
Location
Florida
@Ripper99 is correct. My use of the word "clone" was not actually a clone camera. Blue Iris has a function for cloning a camera. What Rob (and myself and others following the same process) are doing is actually creating a new camera in Blue Iris with just the substream for the detection and 24/7 recording. A true clone camera would be cloned within BI with identical streams to the original camera. This would not work for Rob's 24/7 stream as the HD of the clone would be recorded 24/7.
Thanks @austwhite and @Ripper99 . This was a huge source of confusion to me when I was trying to figure this out, just a couple of weeks ago. It would have save me a ton of time if I had found a simple paragraph like you just gave me.
 
Top