Blue Iris UI3

@bp2008
In some post a couple years ago, you said some browsers do not support full screen.
This Chronium does on the Rasberry Pi2b, but I have to manually hit the button on the lower right corner.
I am able to use the URL parameter of "maximize=1" and also "group=outside" upon startup which is great. I looked in the help file but there is no mention of auto-full screen. Looney said years ago that "fullscreen=1" should work. It does not on this Chronium.
Is this one of those browsers that do not support URL fullscreen?
What is weird... the Amazon Firestick side-loaded Chrome auto started in full screen (though there is no URL parameter for it in there). Of course, that was Chrome and not Chronium.
 
Just for info...
@MarcK had this error waaay back in Oct. 2019 and I just had it as well. Closing/restarting BI solved it for me, YMMV.

BI-UI3_error_041322.jpg
 
@bp2008
In some post a couple years ago, you said some browsers do not support full screen.
This Chronium does on the Rasberry Pi2b, but I have to manually hit the button on the lower right corner.
I am able to use the URL parameter of "maximize=1" and also "group=outside" upon startup which is great. I looked in the help file but there is no mention of auto-full screen. Looney said years ago that "fullscreen=1" should work. It does not on this Chronium.
Is this one of those browsers that do not support URL fullscreen?
What is weird... the Amazon Firestick side-loaded Chrome auto started in full screen (though there is no URL parameter for it in there). Of course, that was Chrome and not Chronium.

There is no fullscreen URL parameter because the browser won't allow a web page to enter fullscreen mode except in response to user input such as a click or key press.
 
UI3 version 206, Blue Iris version: 5.5.6.11

I've had a new issue crop up in the last couple of days. Things have been working great for the last year or so. The only thing that changed as I got a new set of Windows updates thrown at me and a forced reboot. After that, UI3 will freeze on me every couple of hours. If I click refresh, everything is fine again for a couple hours, then it freezes again.

I'm using IE as the browser.

Any idea what's going on? How do I track this down?
 
  • Like
Reactions: looney2ns
Hello, UI3 has always been great, but I've always wanted one feature, which would help a lot with high resolution cameras.

When zooming in, on a high resolution camera, it would be nice to have the option of the UI3 interface to only encode and stream the portion that's zoomed in.

As it stands now, especially if there's a lot of movement on the camera, the zoomed in view is of really low quality. If UI3 was able to somehow only encode the zoomed in portion of the bitmap, it would be much clearer.
 
  • Like
Reactions: sdkid
I'm not a code writer but I am pretty sure that would have to occur at the server end, not at the UI3/client side.
 
If it were, I think it would already be there.
 
UI3 will freeze on me every couple of hours. If I click refresh, everything is fine again for a couple hours, then it freezes again.

Does anything on the page still respond after it is frozen? Can you try opening the developer tools via the F12 key (or ctrl + i) and look at the console output to see if anything weird has happened?
 
Yes, likely both server and client, if that functionality isn't already available somehow.
If it were, I think it would already be there.

I have certainly thought about it, but trust me, it is not worth the massive collaborative effort between Blue Iris and myself that it would take to do this with an acceptable level of performance. There's simply too much complexity and very little gain.

If you choose the "2160p" streaming profile then you will typically get very high quality anyway, and if you're not satisfied by that, then you can create a new streaming profile in UI3 that encodes the stream however you like. You can get very close to lossless encoding with higher quality values and the bit rate limit disabled, at the obvious cost of terrible efficiency.
 
If you choose the "2160p" streaming profile then you will typically get very high quality anyway,
So what do you suggest? I had always used Jpeg HD, but after seeing these last few posts I have changed to 1080p2MP. Pros cons?


1649970980688.png
 
  • Wow
Reactions: TonyR
So what do you suggest? I had always used Jpeg HD, but after seeing these last few posts I have changed to 1080p2MP. Pros cons?

Heh, I can't believe you are asking this. But UI3's Jpeg options are basically just compatibility modes for systems that can't run H.264. You don't get camera audio with Jpeg streams, and the frame rate can be low, and the compression is not very efficient.

I suggest 1080p VBR or 2160p VBR if you are remote (over the internet) or on wifi. Otherwise 2160p for wired LAN connections if your viewing device can handle it. If it can't handle it, step down to 1440p, 1080p, etc until it can handle it.
 
I can't believe you are asking this
? Thanks for the reply. Maybe I had asked that already? I am getting old you know.
 
Does anything on the page still respond after it is frozen? Can you try opening the developer tools via the F12 key (or ctrl + i) and look at the console output to see if anything weird has happened?

Yipeee! There's an error message in the console log! it says http://<BI server>/<blah blah blah> Net:: OUT_OF_MEMORY

Neither the server or the client should be out of memory. The server has 14GB of RAM and only 9GB is showing as used, and the client has 8GB and Edge is the only thing running.

I'm assuming this is the server running out of memory. I don't see any errors in the BI server logs indicating any errors.
 
@VirtualCam Nope, the server running out of memory would not appear as an error on the client. Your edge browser is leaking memory from the sound of it. I'm fairly certain it isn't UI3's fault, at least not directly. You can probably work around the issue by changing the H.264 player to JavaScript (under UI Settings > Video Player). Just be aware it will use more CPU time on your client device that way.
 
@VirtualCam Nope, the server running out of memory would not appear as an error on the client. Your edge browser is leaking memory from the sound of it. I'm fairly certain it isn't UI3's fault, at least not directly. You can probably work around the issue by changing the H.264 player to JavaScript (under UI Settings > Video Player). Just be aware it will use more CPU time on your client device that way.
Switching to Chrome seems to have fixed the issue. Wonder why no one else has reported an issue?
 
Sorry, I am using Edge :) MS Browser is IE in my brain :)
So even though you were using Edge, which is Chromium-based, switching to Google Chrome solved your issue?