For example, I have a frame with person:85% and another frame with two people, person:84% and person:84%. It used to be that BI would try to get the maximum number of recognized objects in one frame and choose that as the frame to use for Alert images and memos. Nowadays, it seems to choose person:8...

Sorted indeed in the latest

I’d only like the counter to increment for alerts that were AI-confirmed. Is there a way to do this?

Anyone else notice that the Alerts list is loading extremely slowly now? Happened after updating to 5.7.8.3 from an earlier version (5.7.7.18), but continuing in at least 5.7.9.1.

The Clips list is still fast to load, only the Alerts are slow. Like takes nearly 7 seconds for it to load every time.

Thanks guys. A lot of the discussion was on simply triggers, but I was more interested in Alerts in my case. After talking to Ken, I was pointed towards the "Wait" action set which at first sight seems to take into consideration what I mentioned. It has an option to integrate newly detecte...

Say you have a camera facing the driveway in the street. You want to record motion that happens both on the street and the driveway, but you only want alerts for motion in the driveway. Makes sense, right? A zone for each. Objects on, objects off, doesn't matter. But Blue Iris doesn't seem to suppor...

Yep, doesn't work. But %001 works. It uses the memo, which is set to the detected object anyway.

I run BI in a Windows VM on top of Debian running KVM. It’s great once you set up Intel GVT-g for hardware acceleration. I do get virtual GPU crashes every couple of days, since apparently Intel employs like two very slow people to maintain their buggy virtual GPU code, but the headache is worth it....

On a fresh install of 5.2.6.0, when I went to run Blue Iris as a service in the settings and entered my Windows logon username and password, it kept giving me the error "Could not login, check password (1326)". I am 500% sure I was entering it correctly. A few hours later, I changed my pas...

My GPU usage has doubled since 5.2.5.7. Slow enough to be unusable. And reverting to 5.2.5.6 or even 5.2.5.1 didn’t fix it. Must be a permanent configuration... RIP.