Breakthrough/DVR-Scan v1.4

DVR-Scan v1.4

on GitHub

Release Notes

In addition to several bugfixes, this release of DVR-Scan adds the ability to draw a bounding box around the area in the frame where motion was detected. There are also several improves when using -fs/--frame-skip and/or -df/--downscale-factor by ensuring all other option are relative to the original video framerate/resolution.

Changelog

• [feature] Add new --bb/--bounding-box option to draw rectangle around the area in the video where motion was detected
  • An amount to temporally smooth the box in time can also be specified after -bb (e.g. -bb 0.5s), where the default is 0.1s
• [bugfix] Processing errors should now return a non-zero exit code
• [bugfix] Allow a maximum window size to be set when using -roi (#59):
  • The -roi flag now accepts a maximum window size for the ROI selection window (e.g. -roi 1920 1080)
  • If the screeninfo package is installed, or you are using a Windows build, videos will automatically be resized to the maximum screen size
• [bugfix] Fix frozen timestamp at beginning of video (#68)
• [bugfix] Fix output videos not including all of the duration specified by -tb/--time-before in certain cases (#68
• [bugfix] Fix event start times not reflecting -l/--min-event-length and -tb/--time-before (#68
• [bugfix] Scanning no longer stops suddenly after a frame fails to decode (#62)
  • If more than 1 corrupt frame is found, a warning will be displayed with the number of frame decode failures
  • If more than 5 frames in a row fail to be decoded, processing will stop and display an error
• [bugfix] When no events have been found, an empty file is no longer created if -o/--output is specified
• [enhancement] -k/--kernel-size is now relative to the original video resolution, and will be reduced to adjust for -df/--downscale-factor if set (#46)
• [bugfix] Output videos now have the correct playback speed when using -fs/--frame-skip by reducing the framerate (#70)
• [bugfix] The -l/--min-event-length, -tb/--time-before-event, and -tp/--time-post-event parameters are now adjusted to compensate for -fs/--frame-skip if set (#70)
• [bugfix] An erroneus event (false positive) is no longer generated at the beginning of a video when -l/--min-event-length is equal to 1 frame

Known Issues

• Variable framerate videos (VFR) are not fully supported, and will yield incorrect timestamps (#20)
• When using -fs/--frame-skip, event start times do not include all of -tb/--time-before-event (#68, #70)
• When using -bb/--bounding-box, the amount of time covered by -l/--min-event-length will be missing bounding box overlays (#31)
• Using -st/--start-time will yield incorrect results