Just to confirm and for my own understanding: these new(ish) caps on the number of items in the Alertlist and Cliplist only apply to what BI passes along to UI3, correct? in other words, when working from the BI console, these new numbers don't truly restrict the actual number of Alerts or Clips accessible, right? I have access within the BI console to considerably higher numbers than that, currently using BI 5.7.8.2, and don't want to see a loss of access to those Alerts if I migrate to a newer version (currently 5.7.9.5).It appears the new limits for cliplist and alertlist responses in 5.7.9.3 are:
cliplist
:4096 items
alertlist
:2048 items
(+/- a few because of some alert list weirdness)
That is correct. The old limit (for many years) used to be 1200 for clips and about 1000 for alerts. If you want to see further back in UI3, you need to use the date filter (calendar date selector) and then UI3 will make as many requests as it needs to load all of the selected date range. Or just use the Timeline tab if that suits you.Just to confirm and for my own understanding: these new(ish) caps on the number of items in the Alertlist and Cliplist only apply to what BI passes along to UI3, correct? in other words, when working from the BI console, these new numbers don't truly restrict the actual number of Alerts or Clips accessible, right? I have access within the BI console to considerably higher numbers than that, currently using BI 5.7.8.2, and don't want to see a loss of access to those Alerts if I migrate to a newer version (currently 5.7.9.5).
TIA for confirming.
Yes. I agree it is very frustrating. Blue Iris tries to produce the timeline video stream at a steady 30 FPS. In order to achieve that without lots of pausing and stuttering, the video clips get loaded asynchronously. That is to say, the timeline playhead continues to move ahead steadily while clips load in the background.Timeline tab playback usually skips the first few seconds of every clip (which contains the actual important parts, making it useless). Non-Timeline playback is normal. Any ideas why?
Stats for nerds
. This will tell you the resolution being streamed, native resolution, and viewport size, which should provide clues about what is going on.Thanks for the input. I have tried a number of these things previously and I have done a few more based on your recommendations. Here are the results.@gwithers I can't think of anything that would cause the behavior you describe. I have the Annke version of the same camera using main and sub streams and I don't have the same problems.
I have some recommendations:
1. In UI3, right click the video and openStats for nerds
. This will tell you the resolution being streamed, native resolution, and viewport size, which should provide clues about what is going on.
2. Try different streaming profiles in UI3. 8K, 4K, 4MP, 2MP, etc and note any effects on stream resolution in Stats for nerds, and on the aspect ratio. If you choose a profile that is not larger than the sub stream resolution (e.g. 480p) then Blue Iris will deliver video from the sub stream.
3. Try UI3 on a very different device (to rule out driver issues).
4. Try a different H.264 player in UI3 (main menu > UI Settings > Video Player > H.264 Player).
Yes, some systems may have trouble playing this camera's native resolution via some players. The easiest solution on those systems is to use a 4K or smaller stream in UI3 as this will limit the width to 3840 pixels.4.) No changes between selecting the HTML5 or WebCodec player (or Javascript) although some of the stream profiles and player codec don't like each other and won't play the new camera stream.
That is correct. If I play video from the "All Clips" in UI3, all is well, but it is broken when played through the alert (via the 1920 x 1080 resolution designation) . Yeah, the new camera didn't help either. I don't know why it is always thinking it should be 1920 x 1080. I am stumped.So you get the bad behavior when you're using "Alerts" in UI3, but good behavior when using "All clips" in UI3? It sounds like Blue Iris wrote the wrong resolution to its database for the alerts for some reason. But if you created a new camera in Blue Iris and it still happens, then I don't know what else to do. What version of Blue Iris are you running?
Yes, some systems may have trouble playing this camera's native resolution via some players. The easiest solution on those systems is to use a 4K or smaller stream in UI3 as this will limit the width to 3840 pixels.
Good troubleshooting. I'd be curious to know what the root cause is if you ever figure it out.This feels like something got messed up during the testing phase for this new camera and the problem I introduced has stuck in the configuration somewhere.
Hello!This issue becomes apparent when I access the UI3 interface from an external network via an external URL. In this scenario, the PTZ controls for my cameras become disabled, despite using the same administrator user credentials.
My reason for reaching out to this community is to inquire whether this behavior is intentional, perhaps as a design choice, or if there might be a configuration option that I can examine to rectify this issue. Any insights, suggestions, or solutions that fellow members could provide would be greatly appreciated.