Auto-Maximize in UI3 - How to cycle between multiple simultaneous alerts?

[Corvus85]

I've been playing around with auto-maximize on UI3 and can't get it to work the way I want it to.

I have alerts set up for CP.ai to detect my dog in the backyard as well as vehicles which enter my driveway.

Let's say my dog is moving in my backyard, generating an alert (this is desired behaviour), but at the same time, a salesman comes to my door, or someone pulls up in my driveway.

With auto-maximize set to on, it will select the camera which first detects an alert (in this case, my dog running to the side gate to bark at the intruder), but then it NEVER SWITCHES TO THE DRIVEWAY/FRONT DOOR CAM. It just remains focused on my dog.
Ideally, I'd like it to auto-maximise on EACH NEW ALERT and switch cameras appropriately.

Please tell me that after all these years, there's a way to make it do this.

 

[bp2008]

Not possible without modifications to UI3 which I am not very interested in.

I can explain why it works the way it works today. My thought process in designing this feature was something like this. I could make UI3 be eager to swap to newly triggered/alerted/etc cameras, or I could make it stick to one until it becomes idle again, then switch to another. There are pros and cons to both approaches. The benefit of swapping more frequently is, obviously, you get a better overall idea of what is going on. The downside is there are more frequent camera switches, which breaks your focus and causes a brief interruption where there is no video playing at all. And UI3 would be far more likely swap away from the important action, to something irrelevant. Arguably, this is better than perhaps never showing you the important action in the first place. But what it boiled down to for me is, with UI3 actually having NO IDEA which cameras or alerts are a higher priority, it seems there is an equal chance that switching cameras is wanted or unwanted. So I can't make a good decision based on that. Howeverautomated camera switching is certainly more disruptive than not switching, and I should minimize switching, so that is what I did. This decision was reinforced when sub streams were added to BI, which makes camera switching even more disruptive than before.

However Blue Iris has also in recent years introduced the ability for a remote client to video a subset of cameras in a group all at once -- a capability which UI3 does not yet use in any way. This is an obvious case where that would be beneficial. UI3 could display simultaneously all the cameras that are seeing motion/trigger/alert. However it would also be more disruptive than ever because in a busy, ever-changing environment, camera switches could be happening very frequently, causing lots of stuttering and camera rearrangement. I do not think this would be a pleasant experience, so I have not tried it yet.