Blue Iris UI3

erkme73 said:
Man, I wish I had just a fraction of your understanding and patience to explain this to people like me :) FWIW, is it safe to assume my 320 install didn't take? I copied the contents of the zip files to the programfiles/blueiris5/www directory and overwrote what was there. But even after restarting the service, and reloading the page, I'm still showing 319 on my browser.
Click to expand...
:)

Yes if it shows 319 on the about page, then you didn't put the update in the correct place.

There's no need to restart the Blue Iris service when updating UI3. Just reload the UI3 page.

I am guessing you extracted to the wrong path. Make sure login.htm and ui3.htm go into www, and overwrite everything when prompted.
 
Ok, it took a lot longer for the stall to happen on 320, but, alas, it did. check out this video of a coyote prowling a turkey... The player delay time seems to float between 80 and 120ms, until about 25 seconds in. Then the image freezes, and the player delay takes off. It eventually starts playing (after 21 seconds of player delay)... Does this provide any more data points?
 

Attachments

  • Like
Reactions: bp2008
erkme73 said:
Ok, it took a lot longer for the stall to happen on 320, but, alas, it did. check out this video of a coyote prowling a turkey... The player delay time seems to float between 80 and 120ms, until about 25 seconds in. Then the image freezes, and the player delay takes off. It eventually starts playing (after 21 seconds of player delay)... Does this provide any more data points?
Click to expand...
Ahhh man I don't know.
In that one, the video player ACTUALLY stalled and the stall detection did not kick in. The stall detection code that shows the yellow toast message "Detected HTML5 video player stall. Reopening video stream" is not user-configurable, and it looks for very specific conditions I was getting all the time on my Android phone many years ago. Probably the reason it did not trigger there is because the video player never entered its "waiting" state which is one of the preconditions for this particular stall detection.

It kinda just looks like a less frequent symptom of whatever underlying problem is causing this mess.
 
  • Like
Reactions: erkme73
Well, whatever it is, it must be a rather recent trigger because I didn't have these issues about a month ago. I wonder if I can roll back my Brave/Chrome updates and verify... I'll explore and report.

And fwiw, 320 definitely is playing more robustly than the 319, so whatever you modified seems to help. TY!
 
  • Like
Reactions: bp2008
erkme73 said:
Well, whatever it is, it must be a rather recent trigger because I didn't have these issues about a month ago. I wonder if I can roll back my Brave/Chrome updates and verify... I'll explore and report.

And fwiw, 320 definitely is playing more robustly than the 319, so whatever you modified seems to help. TY!
Click to expand...
I rolled back to Feb 2026 on Chrome and I could not get any of the playback to stall. Granted it was 320, but still no glitching. Hopefully, as you said, some bigger fish are feeling whatever change there was and will help get it resolved. Thank again...
 
You must log in or register to reply here.
Top Bottom