"New and all retriggers" alert crashes Blue Iris after second AI confirmation
Posted: Sun Aug 04, 2024 5:35 am
Win10, BI5.9.4.11, Codeproject AI 2.6.5, YOLOv5.NET (onboard Intel GPU) or Coral TPU with YOLO5 or YOLO8. I've deleted and reinstalled the camera, CP.AI and the Coral hardware. Ensured I have the latest Intel INF drivers and video drivers.
If you configure an alert for "New and all retriggers", upon the second AI-confirmed retrigger within the period of the first trigger, the stream for that camera will freeze in the Windows UI, the web UI3 and destabilize the operating system. BI stops sending data to CP.AI for that camera for about 2 minutes until it resets itself and the same repeats.
That camera will then display a Signal Loss, and the camera properties general tab will say "Frame Bottleneck" or "Check FPS and keyrates"
Cameras are 25fps / 1 keyframe per second for both main and substream.
Everything works perfectly if the alert is configured for "New triggers only"
Can anyone repeat this? Is it a bug or maybe something I've done wrong?
If you configure an alert for "New and all retriggers", upon the second AI-confirmed retrigger within the period of the first trigger, the stream for that camera will freeze in the Windows UI, the web UI3 and destabilize the operating system. BI stops sending data to CP.AI for that camera for about 2 minutes until it resets itself and the same repeats.
That camera will then display a Signal Loss, and the camera properties general tab will say "Frame Bottleneck" or "Check FPS and keyrates"
Cameras are 25fps / 1 keyframe per second for both main and substream.
Everything works perfectly if the alert is configured for "New triggers only"
Can anyone repeat this? Is it a bug or maybe something I've done wrong?