5.0.7 - December 15, 2019

fenderman

Staff member
Joined
Mar 9, 2014
Messages
36,897
Reaction score
21,250
5.0.7 - December 15, 2019
The web server will now send an “image not found” JPEG in reply to an /alerts/ request for
a non-existent database record. Previously there was either no response or a file not found
error returned and these both confused the iOS app.
The use of HTTP keep-alive semantics is now optional on the Advanced page from Settings/
Web server.

The Plate Recognizer AI integration now pulls a status on the Trigger/AI page. This serves
to both validate the token entry as well as to provide usage statistics for the current period.
Camera source triggers (via ONVIF) were previously handled as “external” triggers but are
now labeled more appropriately as ONVIF triggers. A new check box on the Alerts tab in
camera settings determines whether alerts will fire for ONVIF triggers. The trigger state in
Blue Iris now is also maintained until a trigger reset event is received from the camera
(previously this was ignored and the trigger ended after the break time only).

One headache from the use of Intel hardware decoding has been the ambiguity between
1088 and 1080 line resolution. The Intel decoder will take a 1080 line source and force an
output of 1088 lines. This is because 1080 is not a multiple of 16, yet 1088 is, and that’s
required by the decoder. This has caused confusion as a new resolution forces a new zone
map in the motion detector. Beginning with this version, the output size is cropped at 1080
lines. This will eliminate “garbage” lines from appearing at the bottom of the decoded
frames. However, this may result in the need to redesign your zone maps, sorry for that
inconvenience.
 
Top