Report name of corrupt file and continue about dvr-scan HOT 4 CLOSED

One problem with this is that it may cause a motion event to be detected if the lighting changes significantly. I suppose this is probably acceptable for most use cases though if only a few are corrupt, and can add a warning that the result might not be accurate if a video was skipped.

I'll work on adding a new option for this in the next release.

from dvr-scan.

Sorry I may have misunderstood your use case here. Can you clarify what you mean by stop and start over? The program should abort as soon as this occurs, rather than in the middle of a run. Thanks!

from dvr-scan.

@9812ga98sd @Breakthrough
It sounds like you're looking to differentiate between files processed by "dvr-scan" and those that aren't. You could generate a report or log containing the list of processed filenames for the user's reference. This way, the user can review the report later to see which files were processed by the software.

from dvr-scan.

This can be disabled at the source level when videos are loaded in the joiner, but in DVR-Scan v1.6 it should report the full path of the corrupt video name and the reason it could not be opened. This check should happen before any processing starts, so you will not need to manually start/stop anything.

The program was intended to concatenate inputs as a contiguous stream, and relies on that for accurate timekeeping. This is why scanning does not continue when a video cannot be opened. If this is undesirable, you can also use a loop in a script to run DVR-Scan on each video individually, rather than running it once on all videos.

from dvr-scan.