v2.2.24

Fixes a situation in pyzm where OpenCV 4.5.4 would error out with Yolo #44

v2.2.23

• sync and allow aliases

v2.2.22

• Fixes an issue where past_det_max_diff_area was not being picked up from ml_config

v2.2.21

• Adds example of convert_snapshot_to_fid
• Links with updated pyzm to support yes or bool for convert_snapshot_to_fid

v2.2.20

• Fixes a situation where polygons were not compared correctly when only_triggered_zm_zones were used

v2.2.19

• Fixes a situation where only_triggered_zm_zones did not function properly across multiple runs. See this

v2.2.18

• Added support for basic authentication
• Added support for plate recognizer parameters - see here

v2.2.17

• For some weird reason, pyzm had old code, not sure why. Forced an upgrade to 0.3.46. This was causing errors in match_past_detection
• Added ability to limit # of hook processes that are spawned in zmeventnotification.ini via max_parallel_hooks

v2.2.16

• Fixes a bug where adding DB users from CLI in interactive mode did not work
• Fixes a bug where zones were imported into mlapi if global import zones was no and unspecified in monitor specific areas
• Allows mlapi to be used without ZM authentication (only use if ZM has auth turned off) via auth_enabled flag in config.

v2.2.14

• match_past_detections, past_det_max_diff_area and max_detection_size (and associated label prefixes)
  need to be in the general section of ml_sequence. In the previous release they were stuffed inside each
  model sequence which lead to problems (imagine an event where snapshot and alarm had different objects and you
  were checking both. In pass 1, snapshot would match but alarm would not, so you'd see objects in alarm. In pass 2,
  alarm would match, but not snapshot and it would keep going on like this, effectively making match_past_detections
  useless. To avoid this, I am checking for match_past_detections after all matching is done)

• You can now choose to ignore certain labels when you match past detections using ignore_past_detection_labels

• stream_sequence now has a few new fields fields:

  • delay_between_frames. If specified, will wait for those many seconds before processing each frame.
  • delay_between_snapshots. If specified, will wait for those many seconds when processing snapshot frames.
    This allows you to do something like this: frame_set ['snapshot','snapshot','snapshot','alarm'] with a
    delay_between_snapshots:2, which means it will keep analyzing snapshot 3 times, but with 2 seconds in between, which
    lets you grab multiple snapshot frames as it changes during an event. This is really only useful for this specific case.