wildcards produce different detection than file by file run about dvr-scan HOT 4 OPEN

Whenever you pass multiple files to DVR-Scan, it treats them as a single contiguous video. This allows you to combine multiple videos from a single camera angle, while still handling the case where an event occurs across the boundary of a file.

To achieve what you want, instead for now you'll need to run DVR-Scan once on each disjoint clip. You can automate this by writing a for loop in bash, e.g.:

for f in /mnt/foo/*.mp4
do
  dvr-scan -i $f --threshold 200
done

This has also come up in the past in #135, so this is a frequent enough ask that I think it should be added to DVR-Scan. I'll repurpose this bug report to track adding this as a feature. In the next release, we can add a -n/--no-concatenate flag for use cases similar to this. That should avoid requiring the workaround specified above. The documentation should also be updated to make this behavior more clear.

Although this is working as intended currently, I can see how it can be confusing due to the lack of documentation around how this works. Until that's resolved, I'll keep this tagged as known issue as well. Thanks for filing this!

Edit: Also I want to thank you so much for providing all required information, and a sample - that made triaging/"debugging" this a lot easier. Cheers!

from dvr-scan.

Thank you Brandon,

That did the trick. It was a bit slow on my Linux laptop (old core i5 1.6Ghz) @ 45fps, so I tried with a batch command on Win11 on AMD Ryzen 7530U and that got me 90fps - all of that over a WIFI connection to the storage unit. I then tried to run it on my desktop on a Corei5 9th gen on a local USB 3 connection and I still got 90 fps. Does that sound about right? or can it go faster on a faster CPU?

Also, I don't believe it has anything do do with DVR-scan, but when I got back to my computer, the HDMI display would not come out of power saving mode. There was the occasional SDD drive activity LED flashing but it wasn't consistent with the amount of i/o involved in the process. The bottom line is that I am not sure whether the process had completed or not. Is there any log that I can access to check on that? do I need to use a switch to trigger the creation of a log?

I thought I'd mention it in case you have faced that issue or heard of that issue before.

from dvr-scan.

Never mind about the black screen issue, somehow the driver for my monitor was updated to the "correct" one during a recent Win11 update. I changed it back to the "bad" one and that problem is now solved (my monitor is theoretically only supported up to Win8, but it still works perfectly, so I am using the newer model's driver which supports up to Win10 and voila...).

from dvr-scan.

I've added a workaround for this in the user guide in v1.6, but will defer adding the flag to v1.7.

from dvr-scan.