Blue Iris UI3

@bp2008 Does UI3 have the ability to "Crop playback to selection" like in BI, so the alert playback scrub bar represents only the alert duration rather than the full clip length? I'd like more accuracy when scrubbing an alert and my 1-hour clips make the alert scrub area pretty small within a 1-hour clip. Thanks!
 
aesterling said:
@bp2008 Does UI3 have the ability to "Crop playback to selection" like in BI, so the alert playback scrub bar represents only the alert duration rather than the full clip length? I'd like more accuracy when scrubbing an alert and my 1-hour clips make the alert scrub area pretty small within a 1-hour clip. Thanks!
Click to expand...

Nope, although believe me I have thought about it, I have not implemented that because frankly people had not been asking for it and it is not super easy to do properly.

S4nDr0 said:
UI3 does not seem to work since latest update (6.0.3.1) it worked fine before that. Anyone else having issues? I just get ERR_EMPTY_RESPONSE.
Click to expand...

You are getting hit by the new "security" features Ken added in 6.0.3.0. Really it is not very fair to call them security features, it is more like bot/crawler mitigation features.

Which web browser are you using? It could be sending a User-Agent header that Blue Iris did not anticipate.

If there is anything in the "Host/s" field in your Blue Iris Settings > Webserver tab, that may also be limiting which requests Blue Iris is able to respond to. I think it should be empty by default. (the change log mentions this but erroneously says it is in Settings/AI).
 
aesterling said:
@bp2008 Does UI3 have the ability to "Crop playback to selection" like in BI, so the alert playback scrub bar represents only the alert duration rather than the full clip length? I'd like more accuracy when scrubbing an alert and my 1-hour clips make the alert scrub area pretty small within a 1-hour clip. Thanks!
Click to expand...

There is also a seeking mechanism I have seen on a (few) video players in the past where the further you drag your mouse pointer (or finger) from the seek bar while dragging, the slower the seeking gets. Like if you click the seek handle and drag up a few inches before moving left or right, the seek bar will effectively zoom in so you can move left or right more precisely. I kind of want to implement that in UI3 but the sheer complexity of implementing that smoothly and intuitively kind of scares me off. It'd be simpler to just "Crop playback to selection" like Blue Iris is doing.
 
  • Like
Reactions: aesterling
bp2008 said:
You are getting hit by the new "security" features Ken added in 6.0.3.0. Really it is not very fair to call them security features, it is more like bot/crawler mitigation features.

Which web browser are you using? It could be sending a User-Agent header that Blue Iris did not anticipate.

If there is anything in the "Host/s" field in your Blue Iris Settings > Webserver tab, that may also be limiting which requests Blue Iris is able to respond to. I think it should be empty by default. (the change log mentions this but erroneously says it is in Settings/AI).
Click to expand...
I don't think that I am using anything that isn't used by other people. I access it via latest version Chrome, using Tailscale. I do not access it by IP but by custom hostname I set in tailscale, it is also configured to use a self-signed SSL however it doesn't seem to be the cause, as the issue was present even when I switched it to port 80/http. Only thing out of the ordinary setup in this case seems to be Tailscale / custom hostname/domain in Tailscale, however I presume this is possibly used by many people?

bli.jpg

P.S. OK, I didn't see that changelog previously. It is possibly that indeed, as it is a new field and I had not populated it, as I did not expect it. I will upgrade again tomorrow and check settings -> AI to set my custom hostname that I use to connect.
 
bp2008 said:
Nope, although believe me I have thought about it, I have not implemented that because frankly people had not been asking for it and it is not super easy to do properly.



You are getting hit by the new "security" features Ken added in 6.0.3.0. Really it is not very fair to call them security features, it is more like bot/crawler mitigation features.

Which web browser are you using? It could be sending a User-Agent header that Blue Iris did not anticipate.

If there is anything in the "Host/s" field in your Blue Iris Settings > Webserver tab, that may also be limiting which requests Blue Iris is able to respond to. I think it should be empty by default. (the change log mentions this but erroneously says it is in Settings/AI).
Click to expand...
Brian, does the word "served" here seem right to you or does "severed" make more sense?


served-or-severed.jpg
 
  • Like
Reactions: aesterling and biggen
@bp2008 I am on UI3 version 316, Blue Iris version: 6.0.2.8. Minor UI bug: in Clips tab, for wildlife alert, the wildlife icon is displayed, but in Timeline tab, same event, the person icon is displayed - i.e. bug. See 2 screenshots for example. This bug has been around for awhile.clips.pngtimeline.png
 
TonyR said:
Brian, does the word "served" here seem right to you or does "severed" make more sense?
Click to expand...
"served" is definitely right. The web server is serving the login page from the / path too now. I don't understand how this is a benefit to cybersecurity though.
 
actran said:
@bp2008 I am on UI3 version 316, Blue Iris version: 6.0.2.8. Minor UI bug: in Clips tab, for wildlife alert, the wildlife icon is displayed, but in Timeline tab, same event, the person icon is displayed - i.e. bug. See 2 screenshots for example. This bug has been around for awhile.View attachment 238818View attachment 238820
Click to expand...

UI3 code looks correct for this. I think Blue Iris is fumbling the wildlife flag in timeline data. I can't even assign the wildlife flag to an alert using the JSON API; it corrupts the alert and makes that alert stop working in UI3. I'll submit a bug report.
 
  • Love
Reactions: actran
bp2008 said:
"served" is definitely right. The web server is serving the login page from the / path too now. I don't understand how this is a benefit to cybersecurity though.
Click to expand...
Still doesn't make sense to me somehow since it says ".....unauthenticated server requests will no longer be redirected to login.htm....."

But then again, I've still got a trace of "chemo brain" from last year. :cool:
 
You must log in or register to reply here.
Top Bottom