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?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.
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.
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.
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?
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.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.
I also reviewed this guys notes to confirm everything
... 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.
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 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?
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.
@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.
Can someone help me understand the AITool service? I've set up the service according to the instructions, and it appears to be active. But I'm not sure how to monitor it when running as a service. Is there a way to open the UI so I can look at the history/logs? If I double click and start the program manually, does that create another instance of the program that might interfere with the service, or does it just bring up the UI for the already running program? What is the best way to take a look at the UI when the service is running?
I have it working exactly like this. However I think you need to have a Windows Insider build to enable WSL to access the GPU as per here.New guy here. Sorry if this has been explained already - I could not find anything....
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... !
I did similar to start with. I have evolved now to having this per camera:See above...