Quote:
More important is that these do not transfer bad and corrupt frames, maybe they give you a dropped frame counter or just a dialogue saying that frames were dropped
|
If a frame is not delivered by the reading circuit of the player becase an error in the tape, it will not be captured by any software. The dropped frames are there because they do not arrive in time (based on the framerate information), and are skipped byt the software; it can be a temporary problem solved by a further capture or a permanent problem because a tape drops and again, if the player does not deliver the frame, no software can capture it.
Quote:
A script that takes multiple transfers of the same tape containing errors and combines them to create one file with the best information available for each problematic frame
|
To be honest, I do not trust any automatic engine to rebuild the frames across multiple captures. In the analog capture, when you try to do a median of multiple captures and one of the frame is damaged the result is a bad, and manual intervention is necessary to exclude/duplicate/repair/merge a bad frame.
If a concealment is present because tape drops, I just recapture many times the concerned segment and decide after a visual inspection how to deal with it.
My DV archive flow is the following:
- use "ScenalyzerLive" or "WinDV" to transfer data to DV type-1 files
- run "AVPS DV Analyzer" on the transfered file for video error concealment detection to validate that there are no transfer errors
- transfer again the segments with concealment, trying to get as many correct blocks/frames as possible and choose/splice the frames together if necessary
- run ICEECC on the DV files and create 10% parity files to recover future data corruption
But in any case DVrescue looks promizing, and I will give it a try, thanks for sharing the project.