CodeProject.AI Version 2.0

Thanks for the update. I installed 2.1.8, following the above instructions. Running the most recent version of BI (5.7.62), and get nothing but AI Error 404. I'll roll back BI to a previous version I know worked better and see what happens.
To confirm if it is a BI or CP.AI issues open up CP.AI Explorer and run a test, if it works using CP.AI Explorer then its a BI issues.

Explorer Link

1683232544630.png
 
  • Like
Reactions: David L
It was BI. I had already tested as you mentioned above. Rolling back to 5.7.4.2 resolved the immediate 404 issues. There are certainly still some issues with 5.7.4.2, but it seems more reliable than the newer versions.
 
Im running the latest BI and CPAI 2.1.8 clean install of CPAI reinstalled yolov5 6.2 and facial rec and absolutely zero issues the new version of both seems to be faster and is recognizing the faces alot quicker and getting more positive results on faces...good job all...
 
I have been wanting to get off Windows 10 and switch to Windows Server for my BI PC. This way I can also do a fresh install of CA.AI 2.1.8

I just need to figure out the best way to Backup Blue Iris...

Picking up a SSD today...
 
I may try updating this weekend, I'm still on 1.6.7.
Anyone know if CPAI 2.1.8 solves the issue of recognizing NVIDIA CUDA graphics cards? 2.1.6 had issues for some of us with NVIDIA cards where it would only run in CPU mode, not GPU (CUDA) mode with YOLOv5 6.2 . By downgrading to 2.0.8 was the temporary fix to running in GPU (CUDA) mode.
 
  • Like
Reactions: David L
Anyone know if CPAI 2.1.8 solves the issue of recognizing NVIDIA CUDA graphics cards? 2.1.6 had issues for some of us with NVIDIA cards where it would only run in CPU mode, not GPU (CUDA) mode with YOLOv5 6.2 . By downgrading to 2.0.8 was the temporary fix to running in GPU (CUDA) mode.

I have a gt1030 running in my box and it works fine with GPU running YOLOv5.6.2 on 2.0.8, 2.1.6 & now 2.1.8. I must admit it did have all sorts of issues with detection etc on my test box running the same setup until I did a clean install of everything, I've mentioned it in a thread somewhere on here.

Here are the versions

1683304402841.png

1683304453795.png
 
  • Like
Reactions: David L
So is YOLOv5.NET not still preferred?
 
For me .net process at roughly 250ms and 5.6.2 between 60 - 120ms with my GT1030
Hmmm, when I switched from 6.2 to net I got under 100ms on my 970 GPU. Course I am still running 2.0.8-Beta. When I upgrade I will have to play with them, thanks.
 
  • Like
Reactions: cyberwolf_uk
  • Like
Reactions: cyberwolf_uk
I have a gt1030 running in my box and it works fine with GPU running YOLOv5.6.2 on 2.0.8, 2.1.6 & now 2.1.8. I must admit it did have all sorts of issues with detection etc on my test box running the same setup until I did a clean install of everything, I've mentioned it in a thread somewhere on here.

I have NVIDIA GTX 1660 Super running CUDA 12.1 on 2.0.8 properly. Will try 2.1.8 this weekend. Thanks for your feedback.
 
@David L try disabling it and see what you get. Remember if you have selected it on individual cameras to disable it on each one. If they are not using the default setting
 
  • Like
Reactions: David L
Anyone know if CPAI 2.1.8 solves the issue of recognizing NVIDIA CUDA graphics cards? 2.1.6 had issues for some of us with NVIDIA cards where it would only run in CPU mode, not GPU (CUDA) mode with YOLOv5 6.2 . By downgrading to 2.0.8 was the temporary fix to running in GPU (CUDA) mode.

Make sure you run the cuDNN install script, I had to run the script again when I upgraded to 2.1.6 despite my GPU working in previous versions.

 
@David L try disabling it and see what you get. Remember if you have selected it on individual cameras to disable it on each one. If they are not using the default setting
So far it does seem a little faster:

Prior to change:
1683309905604.png

My CPU % shot up:
1683310012428.png

But in BI all looks good, will need to monitor it some:
1683310133134.png

Nevermind, look at the above after change, looks like it went Offline
 
  • Like
Reactions: cyberwolf_uk