@bp2008 Love the new auto-maximize feature, thank you for building it!
Thanks, and you're welcome!
What determines how long a cam is maximized? Does it remain maximized while the cam is in a triggered state (break time), or is it a separate timer?
It remains maximized for as long as the maximize condition is active. In UI Settings > Video Player you can configure whether you want the maximize condition to be "Motion" or "Trigger".
"Motion" means the cam will only be maximized while
Blue Iris is actively detecting motion, so it resets fairly quickly.
"Trigger" means the cam will stay maximized until your break time expires. "Trigger" mode is also required if you don't use Blue Iris's built-in motion detection.
How does UI3 handle the "auto-maximize" when multiple cameras are triggered in a row? It seems like a new trigger will not override a previous "auto-maximize" until UI3 has returned to grid view?
The way it works is UI3 asks Blue Iris for the camera status every 1 second while this feature is enabled. When each data update is received, UI3 goes through the visible cameras left to right, top to bottom, checking if the maximize condition has been met on any of them. When it finds one, it maximizes that camera and waits for the condition to go away before looking at other cameras.
It would be nice if it could be smarter, but without any control over the serverside, I can't do much.
Just spitballing here, but when in "Motion" mode, maybe I could have UI3 do a "soft-release" of the camera when motion stops being sensed by the maximized camera, where it will switch to another camera that is sensing motion if there is one, otherwise the maximized camera could stay open a few seconds longer. This way UI3 could still respond fairly quickly to objects moving between cameras, but not be quite as quick to un-maximize during periods of intermittent motion sensing.