Problem with UI3 since updating to BI 5.3.2.6 (9/7/2020)

[leemanpa]

Same problem here. Switching to Java seems to be a fix for now.
Oddly enough, it seems to be an issue with Microsoft Edge & Chrome. NOT with FireFox.
Go figure.

[Matts1984]

Have you all reported this to support ?

Looks like I won't be updating BI5 this week.

+1 Glad I actually looked at the forum before doing my routine check for an updated version

[iammrbt]

I'm willing to bet everyone with issues is using Chrome or a Chromium based browser (like the new edge). I normally do also.

I tried Firefox and it works fine no matter the profile you select. Just FYI

[lasocean]

This appears to have now been fixed in 5.3.2.7

[BruceH]

I have just applied 5.3.2.7 and this appears to have resolved this issue on both of my systems.

[aerostar]

I have just applied 5.3.2.7 and this appears to have resolved this issue on both of my systems.

Thanks for the update on the 5.3.2.7 update. Any noticeable improvements? I'm still not sure where to find the official release notes, other than the aggregate release notes, so if someone can chime in with where those might be found, or if they even exist on a per-release basis, that would be great.

[IAmATeaf]

Per major change there are notes in the BI help PDF but to get to it, you would need to download the update and then extract and read but most incremental updates don’t really have any detailed change notes, so for example these recent 5.3.1.x series of updates all have the same change notes.

[aerostar]

Thanks for the 411, IAmATeaf

[TimG]

I updated to 5.3.2.7 and found UI3 (which had been left running in a different Chrome tab) to be unresponsive. A quick refresh of that tab, and all was well. I am now running UI3 v118 (click on the blue title box on the top left hand side to see details).

[bp2008]

Hi all. I want to shed some light on what caused this issue. What happened was Blue Iris suddenly (without warning) changed the meaning of frame timestamps in H.264 video streams. This broke certain aspects of UI3, which relies on those timestamps to control playback rate and to detect video delay.

It had the biggest impact on UI3's HTML5 video player which is the default player in browsers based on Chromium.

Firefox doesn't support low latency streaming with its HTML5 player, so in that browser, UI3 uses a different less efficient H.264 player by default. That player just happened to not be significantly affected by the change to frame timestamps. Some things were still broken, but in less obvious ways.

All known issues were resolved by UI3-119.