Damn, you are right. As soon as I clicked on a camera I knew had motion it crashed with the errors. Bummer. Guess I am back to the app.Are you sure. I thought mine was fine too but I noticed when I clicked on a camera the image was static i.e. it wasn't playing the video it was just showing a picture (time never advanced).
I'm on 5.7.3.0
Go to the timeline and try to scroll around in the past. That is what allowed me to see it was messed up.I have 16.4.1 and UI3 is working as expected.
So apparently he added his PC's LAN IP address to the allowed whitelist on an older PC that was recently upgraded to new hardware. BI must cache the MAC addresses of the IP's in the whitelist. So the IP no longer matched the MAC of the new PC. He deleted it, and it started working again. Thanks for the help.Thanks Brian. I've forwarded the link to your post. I'll follow up with you either way here.
Those 2 IP's should not be the same; #1 should be the cam, #2 should be the BI server and also #2 needs a colon and the BI port after BI's IP.The HTTP commands are not working but the cgi commands are working. Strange.
This works:
But this does not:
You could try the Find/inspect option on the IP cam configuration panel in Blue Iris. It might fix a bad port number or something, who knows.The PTZ controls are not working within Blue Iris local console for this camera.
I've tried all the Dahua PTZ options as well as ONVIF (OXML)
Any other ideas before I reset camera to factory default?
Hmmm. Do you think this could also be the root cause of this problem?I know very little about the issue on iOS since I don't own any modern Apple devices. My assumption is they (Apple) changed their Media Source Extensions (MSE) implementation such that it no longer accepts mp4 fragments that do not begin with a keyframe. Such a change would go largely unnoticed because the overwhelming majority of MSE usage is for VOD where all the video is already prepackaged in chunks that always begin with a keyframe. Low latency live streaming (such as what Blue Iris's web server does in ALL video streaming cases, even playing recordings) cannot function with such a requirement. The efficiency, the video delay, and the responsiveness would suffer enormously.
Hmmm. I just installed UI3-234 and restarted BI server, and when I choose Automatic on my iPhone (iOS 16.4), I still get the Blinking Red Screen of Death. About the UI reports version 234.I have released UI3-233 which revises the "Automatic" H.264 player selection logic. iOS 16.4 or newer (until iOS 17) will no longer automatically choose the HTML5 player. Hopefully they fix the issue by the time iOS 17 comes out, otherwise i'll have to revise the logic again and more people's systems will be broken again later this year.