It is written in the readme at GitHub - bp2008/ui3: A powerful, modern HTML5 web interface for Blue Iris.
Thank you! That was very helpful.It is written in the readme at GitHub - bp2008/ui3: A powerful, modern HTML5 web interface for Blue Iris.
No, it is not.Is it possible to bind two Blue Iris Pc's into one UI3 instance?
I'm on BI 5.5.6.21. I keep getting the Orange Circle of Death on UI3 when I switch to viewing a single camera. It doesn't matter what resolution I try. I'm using the HTML5 viewer with both the latest versions of Chrome and Edge. It says the stream is becoming delayed and it's a compatability issue.
If I view a group of cameras, it's just fine.
The client is an i5 10th gen. The server is a Xeon 2680 V2 and is only running at 50% load. Gig wired network betwixed them, so resources are not the issue.
How do I dig into what's going on?
Watch the frame rate on the camera you are viewing? If it fluctuates drastically, there is an issue with that camera causing the orange circle. If frame rate is steady there is another camera on your system having issues. When I get an orange circle I immediately check the frame rate of each camera individually to see which camera is the culprit. If all cameras have stable frame rates. Then I know the device I’m viewing ui3 on has poor internet connectivity.I'm on BI 5.5.6.21. I keep getting the Orange Circle of Death on UI3 when I switch to viewing a single camera. It doesn't matter what resolution I try. I'm using the HTML5 viewer with both the latest versions of Chrome and Edge. It says the stream is becoming delayed and it's a compatability issue.
If I view a group of cameras, it's just fine.
The client is an i5 10th gen. The server is a Xeon 2680 V2 and is only running at 50% load. Gig wired network betwixed them, so resources are not the issue.
How do I dig into what's going on?
Is it possible to control the PTZ for a single camera while viewing a camera group in UI3? For instance, select the camera so that the PTZ controls are enabled, but remain in group view? I searched this thread and the UI3 settings but couldn't find it. Thanks!
Of course you did, incredible! It works perfectly.Nothing for that is built in to UI3, but I did create an override script years ago that can be coded to do it for specific cameras: Local Overrides Sample: PTZ on Group Streams · bp2008/ui3 Wiki
It might still work
Hard to say what is wrong. What if you use the Jpeg HD mode? Do you get a decent video for single cameras that way?
Is it a single processor in the server? Dual processors tend to report 50% when the load is entirely running on one maxed-out processor and can't spread out across two.
So....What's going on here? Is Chrome or UI3 being a little too aggressive at detecting frame loss, prematurely closing the connection and restarting? I've tried Firefox, Chrome, and Edge, and they all exhibit the same behavior.
@VirtualCam
Can you screenshot your Blue Iris Status window with the Cameras tab selected? Experienced eyes can find a lot of potential problems just looking at that.
It sounds like you maybe did not set up the sub streams according to best practices, and maybe something you did is causing BI to struggle with the main streams. There is a guide I wrote on setting up sub streams: Sub Stream Guide
Also based on what you say about the service shutdown time, I suggest you monitor the memory usage in Windows' task manager. See if it goes up over time. A number of things have caused Blue Iris memory leaks before, most notably Intel Hardware acceleration. Since you're running in a VM you should have hardware acceleration disabled anyway, but it is a common error for people to turn it on when it isn't actually available and there can be side-effects...
Not sure what is wrong
Those are ridiculously low frame rates. 15fps would be more typical. Video is going to be very jumpy / jerky at those fps. Also the key frame rate should be 1 key frame every X fps where x is the number of frames per second ie. 4fps is using 1 every 4. On the substreams it looks as if it's 1 key frame every 8.
Those are ridiculously low frame rates. 15fps would be more typical. Video is going to be very jumpy / jerky at those fps. Also the key frame rate should be 1 key frame every X fps where x is the number of frames per second ie. 4fps is using 1 every 4. On the substreams it looks as if it's 1 key frame every 8.