Blue Iris UI3
- Thread starter bp2008
- Start date
Well the errors are deep in the video decoder somewhere. "Array buffer allocation failed" suggests maybe your client device (running Chrome) doesn't have enough memory.
The only thing I can suggest here is to not use quality 100%. Try putting it back to Quality 50%, as was the default. The encoder could be doing something funky when it is told to do extremely high quality, but do it within a tiny 256 Kbps stream.
In my experience Quality 100% results in video streams larger than 10 Mbps. Sometimes larger than 20 Mbps. And the decoder doesn't always cope with that.
The only thing I can suggest here is to not use quality 100%. Try putting it back to Quality 50%, as was the default. The encoder could be doing something funky when it is told to do extremely high quality, but do it within a tiny 256 Kbps stream.
In my experience Quality 100% results in video streams larger than 10 Mbps. Sometimes larger than 20 Mbps. And the decoder doesn't always cope with that.
James DiBernardo
Young grasshopper
Hi there. I enjoy betas, so i decided to add my input for those who would like to use IIS
For those using IIS, what i did was make a new App (called it CCTV) and pointed the physical path to: E:\Program Files\Blue Iris 4\www\ui3beta so this way it's easier to type in the URL.
In my case i'm using: http://home.1930networks.com/CCTV/
for the IIS setup though you should use HTTP Redirect using the full path in my case http://home.1930networks.com:xxxx/uibeta/ui3.htm -- XXXX denotes the port you have setup.
and tick the boxes for:
[X] Redirect all requests to exact destination (instead of relative to destination)
[X] Only redirect requests to content in this directory (not subdirectories)
Next, set the default document to ui3.htm - move this to the top if it's not already.
after doing that i was able to bring up the ui3 login page and main camera page without error.
=-=-=-=-=-=-=-=
The one bug id like to report though is that when i attempted to make amasking page i get the following error:
Basically, it's so that i can mask the true path to the ui3.htm page to just http://home.1930networks.com/cctv/
I'm not knowledgeable enough to determine where in the code this is occuring. My guess it's somewhere in one of the 3 js files.
For those using IIS, what i did was make a new App (called it CCTV) and pointed the physical path to: E:\Program Files\Blue Iris 4\www\ui3beta so this way it's easier to type in the URL.
In my case i'm using: http://home.1930networks.com/CCTV/
for the IIS setup though you should use HTTP Redirect using the full path in my case http://home.1930networks.com:xxxx/uibeta/ui3.htm -- XXXX denotes the port you have setup.
and tick the boxes for:
[X] Redirect all requests to exact destination (instead of relative to destination)
[X] Only redirect requests to content in this directory (not subdirectories)
Next, set the default document to ui3.htm - move this to the top if it's not already.
after doing that i was able to bring up the ui3 login page and main camera page without error.
=-=-=-=-=-=-=-=
The one bug id like to report though is that when i attempted to make amasking page i get the following error:
Basically, it's so that i can mask the true path to the ui3.htm page to just http://home.1930networks.com/cctv/
I'm not knowledgeable enough to determine where in the code this is occuring. My guess it's somewhere in one of the 3 js files.
piconut
BIT Beta Team
OK, I just discovered another interesting feature. Maybe I'm just slow and the last one to be observant enough but the date above the clip list was flashing green which I think meant that there were new clips to download? Or maybe that I need to refresh the clip list? It's cool, but what does it indicate?
piconut
BIT Beta Team
OK, I think I figured it out. The flashing green date means that I'm looking at a paused video and it is alerting me that I'm not actually seeing live video. I think.
Getting the exact same thing. Using latest Chrome on macbook. I'm NOT going to do a fresh install if it means I have to set everything up again.
No, actually that starts flashing to notify you that new clips have been added to the top of the list. This only happens if you were scrolled down in the list when the clips were added. If you are at the top of the list when clips are added, then the new items just appear in-view with no notification.
I'm not certain what is wrong with your configuration since I don't know how you tried to configure your reverse proxy. UI3 needs to be able to POST to Blue Iris's /json page which BI's web server hosts at the root ... e.g.
Code:
http://localhost/jsonIf you are hosting your reverse proxy in a subdirectory (/cctv/) then here is what will be happening. UI3's first /json request is to check the session status. First, it tries requesting via a relative path, so it ends up sending the request to:
Code:
http://domain/cctv/jsonAt which point your IIS reverse proxy is probably forwarding this to
Code:
http://blueiris/ui3beta/json... That should actually return a 404, not 503, which is why I'm not sure how you set up your proxy server. Or maybe your Blue Iris hasn't been updated in a long time ... older versions did not return 404 from /json requests in a subdirectory.
Anyway if UI3 gets back a 404 after trying the relative path, then it assumes ui3.htm is hosted in a subdirectory and will try an absolute path:
Code:
http://domain/jsonThis would be fine if you didn't have a reverse-proxy in the way, but since you do, that is obviously not what you want to have happen.
Essentially, the problem is that ui3 is being hosted in a subdirectory (this was intentional on my part, since I wanted there to be fewer file version conflicts when this UI goes live) and your reverse proxy server is also hosted in a subdirectory. This configuration can't be accommodated automatically. So there are three potential solutions.
Pick one.
1) The quickest fix would be to move all the files in /ui3beta/ out into the root of /www/. This way, UI3's initial "json" request will go to the root of the web server and this should just start working.
2) Don't host your reverse proxy out of a virtual subdirectory.
3) Configure your reverse proxy server to send json requests to the correct endpoint.
eangulus
Getting the hang of it
- May 19, 2015
- 104
- 6
Just have a suggestion/feature request.
For PTX Cameras with Presets, can we have the option to show the names instead of the numbers? I know it shows the name on hover, but it would be much quicker if I could see the names without having to hover each number till I find the preset I want.
For PTX Cameras with Presets, can we have the option to show the names instead of the numbers? I know it shows the name on hover, but it would be much quicker if I could see the names without having to hover each number till I find the preset I want.
Thanks for the suggestion. I'm not going to do it, though. With the current layout, there isn't enough space for that to work well. Besides that, any text in the preset buttons is only meant to be a placeholder until you have thumbnails captured (try setting each of your presets again, either by long-pressing or by right-clicking and choosing the "Set" option!).
eangulus
Getting the hang of it
- May 19, 2015
- 104
- 6
Didn't know that Just tried it on lasted beta25 and up to date BI 4.6.9.2, and got an error "ele.getAttribute is not a function" Line 258 Char 69
Also just tried the right click as well, I have no set option on right click. I opened PTZ to full screen and right clicked.
Also on another issue, I see that the camera is running at 1024x720 for Stream Resolution but Native is 1920x1080. Can the stream resolution be changed and if so where can I find it?
Last edited:
Beta b26 is available in the first post:
* Fixed a bug where some users experienced their streaming quality preference being changed to "Jpeg Best Quality" after a browser crash.
* Fixed a bug where new preset thumbnails could not appear in tooltips until the next page load.
* Fixed a bug where some users experienced their streaming quality preference being changed to "Jpeg Best Quality" after a browser crash.
* Fixed a bug where new preset thumbnails could not appear in tooltips until the next page load.
eangulus
Getting the hang of it
- May 19, 2015
- 104
- 6