Web Interface (UI3) - Gotchas

Articles based on common support questions.
Post Reply
varghesesa
Posts: 49
Joined: Thu Jul 11, 2019 9:52 pm

Web Interface (UI3) - Gotchas

Post by varghesesa » Fri Oct 08, 2021 1:32 am

Introduction

Gotchas are lessons learned from past tickets.

Gotchas

Gotcha 1: Orange Clock Warning
ui3-gotcha_clock.png
ui3-gotcha_clock.png (241.75 KiB) Viewed 177 times

If you get the orange clock warning, either the fps is low for the stream or the endpoint is overloaded because the resolution (i.e. bitrate) is too high.
Run through the Windows Tuning article just to make sure Windows is not in conflict with BI.
Readjust the stream using Gear icon (bottom right).

ui3 gear icon.png
ui3 gear icon.png (89.19 KiB) Viewed 177 times

FYI, the UI3 gear settings are just presets values in the web server encoder settings
ui3-vs-settings_optimized.png
ui3-vs-settings_optimized.png (90 KiB) Viewed 177 times



Gotcha 2: Using DDNS instead of port forwarding. Accessing the UI3 interface from the LAN using the DDNS URL is very slow.

We are not networking experts so users on the forum may have a better answer.
One possibility is the firewall settings are not set correctly.
Another possibility is usually when you use a DDNS url from within the same LAN, the traffic gets proxied through the router using a function called "NAT loopback" or "hairpin NAT". It could be that their router is bad at this. One workaround is to try the BI server's LAN address instead of the DDNS url when on the same LAN.



Gotcha 3: I set the UI3 timeout to 0 (i.e. never time out), but the browser still logs me out.

In General settings, users can set the UI3 idle timeout period.

ui3 timeout setting.png
ui3 timeout setting.png (29.29 KiB) Viewed 176 times
Users state this setting is not being honored and UI3 still logs out. UI3 will let you know when a session disconnected because of a timeout.

ui3 time out message.png
ui3 time out message.png (16.36 KiB) Viewed 177 times

If instead you received the login page, that means UI3 lost the session with BI which resulted in reloading the page which typically redirects to the login page.

It could be caused by anything that causes temporary connectivity loss, such as the network going down for 1 minute or longer, or even Blue Iris crashing. Or maybe even a session length limit applied to the Blue Iris user account. Although I think the user would realize if they had set this on all their BI systems. There certainly is not a session length limit by default.

The other possibility is the endpoint viewing UI3 is disconnecting. For example, if the endpoint is a laptop, power saving settings may have put the laptop to sleep or disconnected the laptop from the network.

ui3 login.png
ui3 login.png (59.06 KiB) Viewed 177 times


Gotcha 4: Playback is slow or choppy for recordings. 1 - 5 fps

If the live view of the same camera is streaming just fine, then there is probably not an issue with CPU or network performance. The main difference between live and clip playback is the involvement of the storage device on the BI server. It may be having trouble seeking and reading an existing file if there is a lot of recording going on.

So I have some ideas:

1) Make sure playback in UI3 is set to 1x speed and not playing in reverse.
2) Try temporarily disabling recording on the BI server (set shield to red) to reduce disk load for testing purposes.
3) Make sure the recording format is BVR. I've had bad playback issues with MP4 before.
4) If hardware acceleration is used, look for the "Also BVR" checkbox in Blue Iris console > Camera Properties > Video tab. Toggle it on or off in case hardware acceleration is helping or hurting the playback somehow.


Gotcha 5: Login is slow. Live view fails to load or takes a minute to load.

I recommend checking CPU and memory usage on both server and client while remote viewing. Most computers these days are plenty good enough for UI3, but that isn't a guarantee. And also make security software exceptions (see Windows Tuning article), as such software can interfere with the web server connections. A poorly performing network could also cause such issues.

If CPU usage is high, consider unselecting "Require/decode all camera frames when streaming".
Gear icon in top right of Console.
ui3 gotcha_group stream.png
ui3 gotcha_group stream.png (22.6 KiB) Viewed 174 times
Post Reply