Blue Iris UI3

Hm, almost seems like an oversight by the BI team. Is it something we could request?
Anyway, thanks for the reply. It's really awesome having a programmer that the end users have direct contact with. Rare indeed.
 
Lately, I've noticed that if I have UI3 open in Chrome and open another window full screen on the same monitor, UI3 video/audio will stop playing in the background and alerts don't trigger, etc. When switching back to UI3, I can see it reloading. However, opening youtube in chrome and placing another window full screen doesn't interrupt the youtube video. Is this a behavior of UI3?
 
Hm, almost seems like an oversight by the BI team. Is it something we could request?

You could certainly try.

Lately, I've noticed that if I have UI3 open in Chrome and open another window full screen on the same monitor, UI3 video/audio will stop playing in the background and alerts don't trigger, etc. When switching back to UI3, I can see it reloading. However, opening youtube in chrome and placing another window full screen doesn't interrupt the youtube video. Is this a behavior of UI3?

UI3 does cease video streaming when the browser tab's state changes to inactive/hidden. I've only seen that happen when minimizing the browser window, or when a different tab is active in the same browser window that UI3 is in. Not when another window is made full-screen. Anyway, the video, audio, and event cues are all part of the same stream, so they all stop when the video stream stops.
 
UI3 does cease video streaming when the browser tab's state changes to inactive/hidden. I've only seen that happen when minimizing the browser window, or when a different tab is active in the same browser window that UI3 is in. Not when another window is made full-screen. Anyway, the video, audio, and event cues are all part of the same stream, so they all stop when the video stream stops.

Seems like overriding documentIsHidden() does allow it to keep playing in the background. So guess its just getting marked as inactive/hidden. I can just override the function as a workaround.
 
  • Like
Reactions: bp2008
Seems like overriding documentIsHidden() does allow it to keep playing in the background. So guess its just getting marked as inactive/hidden. I can just override the function as a workaround.

Hmm. Just in case you were not aware: UI3 Help

A long time ago I decided I didn't want to add a setting to control this behavior, but I think I made that decision back when H.264 decoding was only done in JavaScript, making it very CPU intensive. And event-triggered sounds weren't a thing, either. Now that things have changed, I think it is probably time to add that setting!
 
@bp2008 Is there a way to set Specific Cams (not all) to have a motion trigger sound? I have all my cams record on motion but I only want the exterior cams to alerts me via audio.

thx for making a great UI
 
This is fixed now, thank you

I noticed that too! Unfortunately it looks like it takes more CPU time now for BI to produce group streams. I tested the previous and new BI versions, and while the new one is certainly capable of higher frame rates, if I limit it to frame rates the old one achieved, CPU usage is still noticeably higher, like 5-10% higher even.

@bp2008 Is there a way to set Specific Cams (not all) to have a motion trigger sound? I have all my cams record on motion but I only want the exterior cams to alerts me via audio.

thx for making a great UI

The only way to control this would be to view a camera group that only has your exterior cams.
 
@bp2008 sorry for not being clear. I know how to create groups. Here's the goal: Keep the screen on (UI3) full time, and get an Audio Alert, in UI3 / browser, when the camera/group detects motion.
 
I've actually noticed that I get audio alerts for cameras outside of the current group that is selected when using the Camera Triggered audio.
 
Same here - here's the rest of the error I see
 

Attachments

  • Screenshot 2019-10-24 at 21.59.30.png
    Screenshot 2019-10-24 at 21.59.30.png
    96.3 KB · Views: 17
Thanks for the warning. I suppose it is good to wait right now.

I hope it is fixed soon.