Version 6 Beta

[bp2008]

Is there any indicator or javascript variable to indicate if direct-to-wire is working? I have H.265 direct to disk and tried enabling direct-to-wire both in UI3 and in encoding options, but stats for nerds show much higher bitrate compared to what it should be

Edit:
My bad UI is in bits while BI is in bytes. Looks like direct-to-wire only works for the LIVE view. Interestingly the plyer delay is much higher for direct-to-wire about 11 frames vs 2-3 frames for re-encoded stream from timeline.

Further testing shows that direct-to-wire delay is variable between 2 and 16 frames, maybe it is related to iframe ? It would be nice to have option for player to wait for iframe to always stream with minimal delay.

Nothing is available yet to explicitly say if direct-to-wire is working. I test by checking the codec and bit rate in Stats for nerds. I also configure my direct to wire profile to be very low quality and bit rate otherwise so you can tell by bit rate if direct to wire is working.

The delay is often higher unavoidably with direct-to-wire. I'm not sure why but there's nothing we can do about it.

 

[jrbeddow]

As many others predicted, the list of changes for Version 6 seems rather underwhelming (IMHO). Personally,I was really hoping for a long awaited solution to getting (push/Pushover) alerts for situations where recording starts in a "non-critical" zone but eventually crosses into a zone of higher priority/concern. Before anyone mentions doing this with cloned cameras; no thanks, I have explored that but really don't want to use that cludge.

 

[tmushy]

As many others predicted, the list of changes for Version 6 seems rather underwhelming (IMHO). Personally,I was really hoping for a long awaited solution to getting (push/Pushover) alerts for situations where recording starts in a "non-critical" zone but eventually crosses into a zone of higher priority/concern. Before anyone mentions doing this with cloned cameras; no thanks, I have explored that but really don't want to use that cludge.

Thinking same thing kind of a huge let down. Make me wonder what the future looks like for blue iris.

 

[wittaj]

As many others predicted, the list of changes for Version 6 seems rather underwhelming (IMHO). Personally,I was really hoping for a long awaited solution to getting (push/Pushover) alerts for situations where recording starts in a "non-critical" zone but eventually crosses into a zone of higher priority/concern. Before anyone mentions doing this with cloned cameras; no thanks, I have explored that but really don't want to use that cludge.

I accomplish this with different IVS rules. One IVS rule to trigger the non-critical zone and another IVS rule for the critical zone that sends me a push.

 

[jrbeddow]

I accomplish this with different IVS rules. One IVS rule to trigger the non-critical zone and another IVS rule for the critical zone that sends me a push.

I appreciate the advice: I tried that as well, but with limited success, as I also use BI motion detection (with CPAI), in conjunction with allowing the in camera IVS (ONVIF) triggering. In most cases the CPAI triggers beat out the IVS ones (in terms of timing), but not always, so for these purposes the results are inconsistent.

It would seem that Ken would have to explicitly add an option to genuinely only send an "action alert" on newly added zones to existing triggers/alerts. I have tried all the current additive/exclusive options with no luck either.

 

[biggen]

I accomplish this with different IVS rules. One IVS rule to trigger the non-critical zone and another IVS rule for the critical zone that sends me a push.

Also do this with my setup. Using ivs on my ~50 cam setup across 3 BI installations is wonderful so I never have to use CPAI.

 

[jrw]

For those having issues with black screen on remote live view after upgrade the fix was the following: Settings > Web Server > Advanced > Configure > Profile: main
It was set to default before.

 

[Skinny1]

For those having issues with black screen on remote live view after upgrade the fix was the following: Settings > Web Server > Advanced > Configure > Profile: main
It was set to default before.

That worked!
Thank you,
Rick

 

[rocky500]

Thinking same thing kind of a huge let down. Make me wonder what the future looks like for blue iris.

I myself really like Blue Iris as it is, as it has been so reliable over the years for me. It just works for what I need, so it just runs in the background without another thought.

Then I have other software over the years that just go into changing too much, too many added features etc that I don't need and changed the way they work, that I have had to look for others.
2 that instantly come to mind are Evernote and ccleaner. Using Standard notes now and looking for a ccleaner replacement.

 

[Jake1979]

I'm running 5.9.9.99 11/30/25
I cannot get to the web UI:

Looks like there’s a problem with this site​

https://10.40.90.2:8088/login.htm?page=/

sent back an error.
Error code: 404 Not Found

• Check to make sure you’ve typed the website address correctly.

Edit: Browsing C:\Program Files\Blue Iris\www, I don't see login.html

I re-installed and it added the UI3 files back.

 

[biggen]

Yeah there is a bug with the new installer and getting UI3 running. You have to run the installer twice now to get UI3 working.

 

[bp2008]

Blue Iris uses a kind of weird method to install UI3. I don't know what the installation code looks like, but by observation I think what happens is this:

• BlueIris.exe has embedded a ui3 release zip file (the same zip file you'd get if you downloaded a UI3 release zip from github)
• On the first run of a new Blue Iris version, it "installs" the embedded UI3 version by: (1) Writing the ui3 zip file to the Blue Iris program files directory, then (2) extracting the zip file into www/, then (3) deleting the zip file.

I haven't run the new Blue Iris full installer yet but I have a hunch, based on the symptoms, I am assuming that when Blue Iris starts up, it runs the UI3 installation code before updating the web server root directory path. If I am correct, that means UI3 gets extracted into the old "www" folder instead of the new one. Then shortly afterward, the web server root directory path gets updated, so the next time Blue Iris tries to install UI3, it is installed to the correct place.

I've sent Ken an email with my theory.