Hi all, I am struggling to get my first minidv capture functioning. I have described the issue below, hoping it's simple setting I missed.
Observed behaviour:
Capture appears to run normally — DVRescue counts frames and the deck plays for the full tape duration. However, the output .dv file only contains content up to the first timecode discontinuity (a camera stop/start mid-tape). Content recorded after that break is not present in the output, despite being confirmed present on the tape by direct playback.
In a recent capture of a 60-minute tape with ~45 seconds of content before the first break, DVRescue ran for 62 minutes but output only 1,346 frames (~45 seconds).
Question:
Is this expected CLI behaviour — i.e. does capture stop writing frames at the first timecode discontinuity? If so, is there a flag to continue capturing through timecode breaks and blank sections between recordings? The use case is consumer MiniDV tapes with multiple short recordings separated by camera stop/start gaps, which is very common in home/personal tape collections.
The capture documentation mentions DVRescue will continue through blank sections if residual timecode exists — is there a way to force this behaviour regardless?
My Setup:
- DVRescue v24.07 running inside Docker (Ubuntu 22.04) on Linux (Unraid)
- Sony HVR-M15AE deck via FireWire
- Capturing MiniDV tapes (NTSC, DV SP) using CLI with -m output.dv -x output_qc.xml
Hi all, I am struggling to get my first minidv capture functioning. I have described the issue below, hoping it's simple setting I missed.
Observed behaviour:
Capture appears to run normally — DVRescue counts frames and the deck plays for the full tape duration. However, the output .dv file only contains content up to the first timecode discontinuity (a camera stop/start mid-tape). Content recorded after that break is not present in the output, despite being confirmed present on the tape by direct playback.
In a recent capture of a 60-minute tape with ~45 seconds of content before the first break, DVRescue ran for 62 minutes but output only 1,346 frames (~45 seconds).
Question:
Is this expected CLI behaviour — i.e. does capture stop writing frames at the first timecode discontinuity? If so, is there a flag to continue capturing through timecode breaks and blank sections between recordings? The use case is consumer MiniDV tapes with multiple short recordings separated by camera stop/start gaps, which is very common in home/personal tape collections.
The capture documentation mentions DVRescue will continue through blank sections if residual timecode exists — is there a way to force this behaviour regardless?
My Setup: