Blue Iris

I have an old setup that ran fine at my prior house, and dusted it off at a new house and started buying cameras. So far I have two (previously 7 x 4k).

I record 24x7 at 4fps, and keep about 30 days worth. The server at this point is loafing, about 5-10% CPU, 10-20% GPU, 50% memory, just nothing to see there. It is the same hardware as at the prior house EXCEPT that I found a GTX 970 (previously only the on-chip Intel). I have turned that on and off inside BI without impact to my issue.

The issue is that while BI's native client displays fine, smoothly (well, as smooth as 4fps can be), the UI3 client is now awful - it hangs, orange clock, warnings about disconnects, viewer stalls, long pauses. This happens whether I use edge or firefox or chrome, and happens whether I use my desktop (wired 1gbs connection), android phone, or run the UI directly on the server running BI. It happens whether or not there is a display from BI's client on the server (though if there is, that display continues to run smoothly).

Here are my web settings (below). I am running 5.9.1.6 on W10x64. That is newer than I ran before as I updated when I got into the new home, but it was a small jump, I was probably running something from 3-6 months earlier. Other than routine windows updates nothing has changed in the OS, and even the network is unchanged, same switch, same server, same desktop.

When this happens there is nothing in the status log in BI. Nothing at all (or at least if I click the graph-jagged-rising, is there another place to look?).
There is nothing in the system or event logs of the system running BI.

It does NOT happen when both cameras are displayed together, when it is showing the low resolution display. It is only when I select a single camera (and presumably it changes to the main stream). I have tried reducing the streaming quality (now 2160) without impact (i switched to 1440p and it hung without about 5-8 seconds of switching streams).

I'm stuck what to check (and what else is useful to tell you).

Any suggestions?

Linwood

Maybe try pushing a few more frames toward UI3 for the encoding involved to create its main streams?

Certainly can't explain why it used to work fine but now it doesn't. Seems to be a lot of that going around lately.

What are you viewing UI3 on? I fired mine up last night on a ONN GoogleTV streamer using the browser in Downloader and it was as smooth as it normally is, which doesn't knock my socks off by any means in the first place, but worked within its intended design.

For pure convenience I use tinyCam Pro (at home). If you're only pushing 7fps anyway you may find it a much more acceptable solution for your purposes. Stream your cameras directly to it or use its web server hanging off an AndroidTV box for remote access. Could use any number of methods for secure connections. Resolution and aspect ratio are retained well, but at the expense of frame rate if streaming much above 10~12fps. In your case, it may be the ticket..., or at least an alternative to UI3.

Doesn't answer your question, though. Sorry I can't help more there.

Pogo wrote: ↑Fri May 31, 2024 8:39 pm Maybe try pushing a few more frames toward UI3 for the encoding involved to create its main streams?

Certainly can't explain why it used to work fine but now it doesn't. Seems to be a lot of that going around lately.

What are you viewing UI3 on?

So this is bizarre. I increased one camera to 15fps, and it works fine. The other at 4fps still hangs when it is selected, so it definitely appears that low fps is the culprit. Which is certainly new behavior, I ran 4fps on 7 cameras for years and used UI3 all the time. Whether it's a change in UI3 or something in my setup changed...

I run UI3 on Chrome usually on windows 10 on my desktop. I've tried this problem through on Edge and Firefox, and also tried it running the browser directly on the BI server, and also tried it on my Pixel 7 android. All behave identically.

I guess I need some experimentation to see what the low cutoff limit is.

Anyone know if some new feature might require higher frame rates?

So it seemed I needed about 8-10 (there was a choppiness as it got low).

However, I went into the encoder settings and mine were set to defaults. I worked on them a bit just setting what I thought might work and... it works fine. Now I get 4fps smoothly.



I have no idea if I reset this to default accidentally at some point recently, my guess is yes. I'm also not sure why defaults don't work, so I don't know what I did that fixed it. But the above works, and I'm happy for now.

Cool beans. It only seemed logical that the ultra-low frame rate wasn't quite enough to provide the necessary input for any reasonable level of encoding.

You're welcome.