Probably 5.7.5.0 or 5.7.5.1.Which version would this be? I just upgraded to 5.7.4.2 and have started getting the error.
Probably 5.7.5.0 or 5.7.5.1.Which version would this be? I just upgraded to 5.7.4.2 and have started getting the error.
More noodling about this. What does a renderer do if it has mp4 fragments that don't start with a keyframe? How does it render anything?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.
Hard to tell. It seems to work intermittently, sometimes after a bunch of clicks sometimes not.@biggen @jaydeel @Serodgers @DSteiNeuro
Could it be a software bug? Like, is it ignoring the first N clicks of the fullscreen button?
I don't know. I tried it both in Safari and Chome on my iPad and I couldn't get the full screen to recognize me hitting the button in either browser@biggen @jaydeel @Serodgers @DSteiNeuro
Could it be a software bug? Like, is it ignoring the first N clicks of the fullscreen button?
Not that I can discern.@biggen @jaydeel @Serodgers @DSteiNeuro
Could it be a software bug? Like, is it ignoring the first N clicks of the fullscreen button?
Turn off "Auto Maximize".Not sure when this started happening, but UI3 is automatically switching cameras on me. Mostly switchover from one camera to another that has motion detected but also from one camera to all camera view. There's nothing in UI3 settings that seems related to this behavior and I don't remember changing anything in the BI console that would cause this. Is there a way to prevent this from happening?
It is supposed to get the keyframe from a previous mp4 fragment and keep using that keyframe until a new keyframe arrives.More noodling about this. What does a renderer do if it has mp4 fragments that don't start with a keyframe? How does it render anything?
All browsers on iOS internally use the same browser engine. Apple won't allow it any other way.I don't know. I tried it both in Safari and Chome on my iPad and I couldn't get the full screen to recognize me hitting the button in either browser
Look for this button in the playback controls area.Not sure when this started happening, but UI3 is automatically switching cameras on me. Mostly switchover from one camera to another that has motion detected but also from one camera to all camera view. There's nothing in UI3 settings that seems related to this behavior and I don't remember changing anything in the BI console that would cause this. Is there a way to prevent this from happening?
Ah, if I'm understanding this correctly, you try to keep a keyframe around all the time, even if it's stale, because any keyframe is better than no keyframe, and for footage from a fixed position, like most security cameras, even a stale keyframe is likely to be pretty useful.It is supposed to get the keyframe from a previous mp4 fragment and keep using that keyframe until a new keyframe arrives.
The problem is, most of Video On Demand streaming online uses MP4 fragments that are a few seconds long and always begin with a keyframe. So that is apparently all that Apple bothered to test with.
UI3 creates an MP4 fragment from every single video frame so that frames can be submitted to the video player without building up a buffer of multiple frames. So most of the MP4 fragments don't contain a keyframe. The first MP4 fragment always does, and for all the other browsers, that is good enough.
Eh, kind of.Ah, if I'm understanding this correctly, you try to keep a keyframe around all the time, even if it's stale, because any keyframe is better than no keyframe, and for footage from a fixed position, like most security cameras, even a stale keyframe is likely to be pretty useful.
Is that more or less correct?
@bp2008 ignore this post, it is working now, server needed to be restarted.@bp2008 when I try to access Blue Iris System Log I am getting the below error. I am on the latest UI3 & BI
View attachment 161896
Which model? You may need to change your PTZ Control page from ONVIF to something else depending on which camera you are using.Good evening,
I’m having an issue in UI3. The PTZ and triggers are grayed out and “not available for current camera”. I can use these functions in local DMSS and on the Blue Iris app. I really want UI3 to be my one and only tool for viewing. Here’s some screenshots of what I’ve got in the camera, BI and UI3. Thank you for any suggestions!