Search results

You can also use zones in BI and mask the area where your overlays are located.

Maybe it has something to do with your shiny new gaming machine (i7-14700F - 32GB DDR5 Memory) while mine is an old piece of junk (i7-4790 - 16GB Memory). :)

Updating to 5.8.9.7 causes "clips: disk can't keep up" errors. Had to roll back to 5.8.9.6.

Just as a test to see if speeds up your MQTT times. If it does then then you know AI is the issue and you can work on decreasing your processing times.

Have you tried adding your MQTT trigger to "Immediate {pre-altert) actions..." to see if that helps?

It works well with two Windows 10 installations.

I just wanted to say thanks again for the IPC-HFW5241E-Z12E-S2. I received the camera 3 days after I purchased it and it was in excellent condition, I set it up a few days ago and it works perfectly.

But did you check to see if you’re still missing plates? I don’t think the pre-trigger record time is the issue here.

You might want to try rolling back to 5.8.7.11 and see if that helps.

So I was using the following settings for my LPR camera: I sent this to Ken and this was his response: Yes with these settings, all custom models will be run. If you want only specific models, you need to specify the model name. If you use a non existent mode name, none of them will be...

Nope, it’s using all the custom models.

That's exactly what it is doing and it's obviously a bug. I would suggest emailing support.

5.8.7.8 Fixed the issue with the start/stop option.

I guess I’ve never noticed because I don’t use this option. I have the service setup in windows to start automatically.

Mine is greyed out as well.

I updated to 5.8.7.7 and AI is working. but the use custom models option field is still grayed out.

I am on the latest version and I posted this issue on the CodeProject.AI Insiders forum.

YOLOv5 .NET I shutdown yolov5.net and installed YOLOv5 6.2 and am seeing the same errors.

Bump, I now know that this not an isolated issue on my system. Any ideas on how to resolve this @MikeLud1 ?

You can take a screenshot of the trigger image and use that in CPAI Explorer or setup BI to capture the trigger image to a specific directory.

It only uses the module that you have enabled.

Using YOLOv5Net and the ipcam-dark model your squirrel #1 cropped image is identified as a cat.

@MikeLud1, I'm seeing a lot of these timeout error messages in the log files of the latest version of CPAI (2.5.1). They appear to be tied to the ALPR module (2.9.0), but don't seem to be causing any issues. Can I just ignore them or is this something that needs to be addressed...

Any image containing something that you are trying to detect will work. This test only confirms the AI is working.

YOLOv5.NET 1.9.2 was just released to resolve the timeout issue.

If you’re still on 2.5.1 there’s an update to the yolov5.NET module (1.9.1) that should resolve this issue.

He responded to my initial e-mail within 10 minutes.

So I've been working with Ken to resolve this and he found something in his codepath where if you see "Alert image not created" in your log file, the camera may stick as triggered. He released version 5.8.4.5 that addresses this issue. To determine if this was affecting your system you can...

Rolling back to 5.8.2.5 seems to resolve the issue. I've sent an email to Ken explaining the problem.