There is an issue that I keep seeing every time I try upgrading to a BI release higher than 5.7.8.3.
On these newer releases (and I’ve tried most of them, including 5.8.9.3) after an AI confirmed alert is logged the alerting camera will often appear to freeze in the BI Console for a period of 99-100 seconds.
In the BI console, the symptoms I see are the Yellow warning triangle appears above the window and the image freezes (both the camera’s date time overlay and the BI date time overlay stop updating). If I make note of the timestamp during the freeze and the timestamp at the point when the image resumes updating, there are always either 99 or 100 seconds between the two timestamps.
If I then play back the alert, I find that the recording actually does include the entire time period that the live view froze. The timestamp from the camera ticks up the entire time, but the BI timestamp freezes for the same 99-100 second period in the recording as I had observed in the live view.
I raised the issue with BI Support about 3 weeks ago, but although Ken has asked me to try the releases since then they have all shown the behavior.
Is anyone else seeing this or similar behavior?
On these newer releases (and I’ve tried most of them, including 5.8.9.3) after an AI confirmed alert is logged the alerting camera will often appear to freeze in the BI Console for a period of 99-100 seconds.
In the BI console, the symptoms I see are the Yellow warning triangle appears above the window and the image freezes (both the camera’s date time overlay and the BI date time overlay stop updating). If I make note of the timestamp during the freeze and the timestamp at the point when the image resumes updating, there are always either 99 or 100 seconds between the two timestamps.
If I then play back the alert, I find that the recording actually does include the entire time period that the live view froze. The timestamp from the camera ticks up the entire time, but the BI timestamp freezes for the same 99-100 second period in the recording as I had observed in the live view.
I raised the issue with BI Support about 3 weeks ago, but although Ken has asked me to try the releases since then they have all shown the behavior.
Is anyone else seeing this or similar behavior?