Blue Iris UI3

. . . and now UI234 gives me this error when attempting to load UI3 in Chrome/macOS:

1682111043062.png

Rolling back to an earlier version now . . . .
 
. . . and now UI234 gives me this error when attempting to load UI3 in Chrome/macOS:

View attachment 160666

Rolling back to an earlier version now . . . .

Rolling back UI3 won't help with that. This is a Blue Iris bug because Ken refuses to use a proper JSON encoder. You probably have a quotation mark in a name field you added or changed recently.
 
  • Like
Reactions: aesterling
Rolling back UI3 won't help with that. This is a Blue Iris bug because Ken refuses to use a proper JSON encoder. You probably have a quotation mark in a name field you added or changed recently.
I’m having the same issue when trying to load the webgui from my iPhone and I do not have any or had any quotation mark anywhere.
Both iPhone and blue iris is running the latest version
 
Rolling back UI3 won't help with that. This is a Blue Iris bug because Ken refuses to use a proper JSON encoder. You probably have a quotation mark in a name field you added or changed recently.
I hadn't changed anything in the config lately, but allowing BI to update itself fixed the problem. ‍
 
Last edited:
Okay now im getting a new error when viewing alerts from my iPhone. It says something about running out of memory…
My server has 16gb ram and gpu 2gb, triggered the error while looking at the server and no issues or high usage on hw memory..
 

Attachments

  • IMG_2670.png
    IMG_2670.png
    3.4 MB · Views: 24
Ok, back with more details on the issue of error in screen shot... "Unable to contact Blue Iris server." when trying to view system log.

I can confirm that it happens on my Android devices using Chrome, and on a laptop running Linux Mint with Firefox.

Went into the direct BI interface on my BI computer, opened log file, cleared, and then I could view log on all devices.

every single other selection in the UI3 menu will display on all devices, it's only when the log file gets large that it won't display.

Just an interesting anomaly, I don't really expect a solution, just something I noticed in case you're interested in trouble shooting...

View attachment 149659

Did you ever get this resolved? I'm getting this error as well on UI3 but also when attempting to view on mobile. I attempted to clear the log file completely. It worked for the first 1 or two entries, then failed again. The file was only 2kb and 25 rows.
 
Okay now im getting a new error when viewing alerts from my iPhone. It says something about running out of memory…
My server has 16gb ram and gpu 2gb, triggered the error while looking at the server and no issues or high usage on hw memory..

Those error messages are from UI3, not from Blue Iris. It would be your iphone running out of memory. I doubt it is actually out of memory, but rather probably just reaching a browser-imposed limit. If the resolution of the stream is very high, try a lower resolution as that should directly influence memory usage in the most significant way availabile.
 
Those error messages are from UI3, not from Blue Iris. It would be your iphone running out of memory. I doubt it is actually out of memory, but rather probably just reaching a browser-imposed limit. If the resolution of the stream is very high, try a lower resolution as that should directly influence memory usage in the most significant way availabile.
Looks like the issue was a software (ether blur iris or UI3) bug as I’m no longer seeing the errors on version 5.7.5.2..
 
I am getting a peculiar situation that keeps popping up recently with UI3. I have deleted and regenerated the database a couple times but and I keep getting a situation where the Alert list shows all the alerts for a single camera with the same time stamp and an error that states that the "automatic alert list update got too many items, Refreshing clip list now", this error repeats. If you go back to a group view, no alert list error is produced. I'm running UI3 236 and BI 5.7.5.3 and this phenomenon just started in the last few days on a new install of BI. Again, this persists even after database regeneration, deletion, etc. and the group view shows the alerts properly time stamped. I get the error in Chrome and Edge on Windows on multiple different computers. Any thoughts on places to look for the cause of this? I searched but couldn't find anything on this.

Update: Turns out the problem was with some of the alert images I brought over to the new installation. Removing them seems to have cleared up the issue. Of course all the older alerts are gone now but I am not exactly sure what was the issue per se but the DB wasn't regenerating alerts properly and getting the time stamps correct was a problem. I've migrated to new installations of BI in the past and this process worked without any issues. This time, not so much. Problem solved more or less and seems to be related to BI and generating the DB from the transferred alerts images. Like it was getting the time stamp for the day and time the alerts was copied to the new location and not the creation date.
 
Last edited:
I am getting a peculiar situation that keeps popping up recently with UI3. I have deleted and regenerated the database a couple times but and I keep getting a situation where the Alert list shows all the alerts for a single camera with the same time stamp and an error that states that the "automatic alert list update got too many items, Refreshing clip list now", this error repeats. If you go back to a group view, those same alerts show in the list with the proper time stamp and no alert list error is produced. I'm running UI3 236 and BI 5.7.5.3 and this phenomenon just started in the last few days on a new install of BI. Again, this persists even after database regeneration, deletion, etc. and the group view shows the alerts properly time stamped. I get the error in Chrome and Edge on Windows on multiple different computers. Any thoughts on places to look for the cause of this? I searched but couldn't find anything on this.

That is pretty bizarre. I tried on my main system here and no weirdness was observed with the alert list with a single camera selected. You should email Blue Iris support since the bug is almost certainly on their end.
 
Anyone else experiencing this with IOS 16.4? Fails on both my iphone's with the same error. From a reddit post:

Updated my phone to 16.4, no longer was able to view UI3 in either chrome or safari. BI installed version was 5.7.1.2. My wife’s phone, still on 16.3, continued to work properly.
Updated BI to 5.7.2.4, still no working video in 16.4. Wife’s phone on 16.3 still works.
If you’re using iOS, maybe wait to update.

====
Hi
I am having a similar issue, everything is working, except I am not able to connect with the iPadOS or iOS 16.5 blue Iris application.
I didn't change anything and it stop working.
Did you fixed your issue?
Thank You
Mario
 
====
Hi
I am having a similar issue, everything is working, except I am not able to connect with the iPadOS or iOS 16.5 blue Iris application.
I didn't change anything and it stop working.
Did you fixed your issue?
Thank You
Mario

For the "Key frame is required" error, just update Blue Iris to latest again. UI3 was updated to apply the current workaround automatically.

It may break again when iOS 17 comes out, and if so I will update UI3 again.
 
  • Like
Reactions: hikky_b
Full screen icon

The full screen icon (little square in the right lower corner of ui3) is sometimes hard to hit on my touch screens (iPad, Echo Show).
It there a way to make it larger?

I could do it in ui3.htm or ui3-local-overrides.js

Thanks!
 
  • Like
Reactions: bp2008
There are a few built-in UI settings that might help. This one controls UI scale in general:

1682710439353.png

While this one just adds more clickable space around all the playback controls:

1682710493566.png

To target just that one button, you could write something like this into ui3-local-overrides.css

CSS:
#clipFullscreenButton
{
    width: 35px;
    height: 35px;
}
 
  • Like
Reactions: hikky_b
I know very little about the issue on iOS since I don't own any modern Apple devices. My assumption is they (Apple) changed their Media Source Extensions (MSE) implementation such that it no longer accepts mp4 fragments that do not begin with a keyframe. Such a change would go largely unnoticed because the overwhelming majority of MSE usage is for VOD where all the video is already prepackaged in chunks that always begin with a keyframe. Low latency live streaming (such as what Blue Iris's web server does in ALL video streaming cases, even playing recordings) cannot function with such a requirement. The efficiency, the video delay, and the responsiveness would suffer enormously.

I've been noodling over this for awhile now. Can you think of a reason why this would have broken the UI3 client on an iOS device but not on a macOS device?
 
I've been noodling over this for awhile now. Can you think of a reason why this would have broken the UI3 client on an iOS device but not on a macOS device?

I'm sure they use plenty of shared code to be sure, but not everything is shared of course. On macOS for example it is still allowed for web browsers to include their own rendering engine.

I do not think it was a conscious decision on Apple's part to break this. The change may have been deliberate but they likely did not realize anyone used HTML5 video the way UI3 does, therefore they wouldn't have realized they were breaking anything.
 
  • Like
Reactions: TheWaterbug
I know very little about the issue on iOS since I don't own any modern Apple devices.

If, hypothetically, one were to start a GoFundMe to buy bp2008 a modern iOS device, who would contribute?
 
If, hypothetically, one were to start a GoFundMe to buy bp2008 a modern iOS device, who would contribute?

Lmao. You realize you are basically asking for funding to send me to hell. No thank you. If the error message is at all accurate, then I couldn't fix this issue anyway. The best I could do is develop a minimal reproduction environment to send in to apple as a bug report, which they would ignore, and I would have wasted a lot of time and effort.