Keeping the screen on is out of UI3's direct control. It is a behavior of the HTML5 video element. The JavaScript player doesn't use an HTML5 video element, so the browser doesn't try to keep the screen on. I suppose I could make a hacky screen-keepalive function by looping a small video in a hidden HTML5 player. I'll put it in my todo list but it won't be high priority.
Might be good to let them update Chrome if you have not done so in a while. As a last resort you can also try jpeg streaming since it works so differently, it might not trigger the same crash.
That is how my system responded with the framerate unequal on the substream and main stream.
What does it look like when you are asked for credentials? Can you screenshot that?
This is just the web browser informing you that you didn't use HTTPS, which is completely normal because Blue Iris does not support HTTPS natively with its web server.
I am traveling and accessing my network via zerotier. First time I have gotten credidential request as well.
You know more than I do. I haven't tried it yet
I just tried. You're right, no audio stream is given for group timeline video. I'd say this behavior is consistent with the release notes:
Hopefully timeline multi-camera audio is coming soon, but to be fair I think in a lot of systems this is less valuable since there's often a really noisy camera in the mix, or the streams are out of sync enough to make the audio a mess when you hear all the cameras at the same time.
@bp2008 Just case you did not know, for each group, when I edit group config, I can control which camera(s) will provide audio for that group. Typically, I select only 1 camera audio for each group so that I don't have multiple audio streams during group view.
Nice. I had forgotten about that.
