Recent content by Gyula614

No. Like a table tennis ball. On camera it's clearly visible.

Other risk from robbery and direct violent acts is poisoning pets inside private area. It should be detected by an "intelligent" camera network controller SW. As it requires the analysis of successive video frames and trajectory detection of moving objects it is questionable if possible with BI...

However now both YoloV5 and YoloV8 give much more false positive detections, in CP AI 2.6.2 than it was in 2.0.8. So will revert to 2.0.8 tomorrow. Later version should be better I thought but it seems that it has kind of reached its limits by many reasons.

Just did an experimental test with CP AI Benchmark tab. Got an image from the web: Rescaled that to various sizes: 4k, 2k, 1280, 720, 640, 320, 160 wide images and provided them to the AI benchmark. Then checked the resulting detection %, FPS and CPU load. Detection % of the person on the...

Thanks, will try D1 or 640*480 whichever is available on the camera. full resolution at high fps/bit rate must be used for identification. 3 streams are ideal I think because phone apps can use a low bit-rate low resolution secondary and AI can use a high bit rate fixed res. third.

Ok. Will check it out. Usually, as I remember it was at about equal in detection with similar resoltion (around 640x480). But some high resolution cameras have distant scenes. For them I kept the higher res. And after that as Dahuas can do 1080p on third stream I just preferred to have 720p or...

The substreams are set to 720p or 1080p whichever is possible on the camera. May it have some rescaling to expected AI input resolution, that causes the CPU load? So, maybe rescaling of sub's frames can raise the CPU. What resolution do you use on substreams? I guess there's an optimal...

That's promising. Just did a stop and restart to the CP AI on its webpage then the CPU goes down to 35% and then back to 100 on restart. The RAM usage also fell some GBs. Had a sreenshot but haven't saved. Now tried again but it always autostarts. I can't stop it. Anyway it seems to be related...

Saved screenshots on disable and enable. Also got YoloV5 working. It has some internal bugs in CP AI, also attached. Is it something to do with camera resolution? This flats the CPU now.

It's dedicated to this task. Nothing else uses this PC. Tried to disable the cameras earlier today. CPU went down to 0 %. Then gradually up to 30. It was a nice linear slope. Will try the FPS. Lower FPS for subs gives better image.. Will try on some of them to see if it helps. Now it's 3:18 AM...

Yes. That would be nice. There are motion zone masks to reduce false detections on some cameras. But it would de-compress the stream anyway to hand frames over to AI. So it's de-compressing frames on motion trigger. That's a considerable work to do. And it may do resize to AI input, but I'm not...

Camera status is great. Thanks for the idea. I was missing something like that for a long time. Attached the screenshots. It's running only for about an hour. 85 % is a good average. Now it's at version 5.8.6.7. Daytime it's somewhat more. All cameras are direct to disk (Although some privacy...

I haven't left mine running for so long. Just about 5 minutes. As CPU didn't fall from 100 decided to revert the version and really everything after 5.8.6.7 ate a bit more CPU as the version number increased and went flat from about late-March versions. To the memory usage I saw similar when AI...

Yes, the AI runs on substreams. No mainstream usage is allowed for any cameras. Eventually I tweaked the substream (third if available) quality to reasonable level 2 Mbit/s for 2 MP res., @ 15 fps, etc.) and AI really didn't give better results with with mainstreams. Haven't checked the wiki...

My PC (i7 8700, 24 GB RAM, GTX 1660, 170 Mbit/sec total IP data rate from 28 cameras, CodeProjectAI 2.6.2) was around 85% CPU usage with maximal 1/sec trigger rate per camera. With the latest BI update versions since 5.8.6.7, as the version number increments it gradually flats to 100 % CPU. Is...