dvpackager does not write split .dv files #943
Labels
package
related to dvpackager
Comments
|
@dariuszseweryn would you mind downloading the latest version of the DVRescue GUI and see if you can package the file that way? |
|
Thank you @libbyhopfauf for the answer. When using the DVRescue GUI, Package tab, a file is created (I select I tried using the same set of ffmpeg/dvrescue/mediainfo/xmlstarlet as the GUI with the CLI but the result is the same as before, i.e. no files are created. |
|
@dariuszseweryn just to double check, did you click "apply" in the GUI? Do you get the same result if you select different segmenting rules? |
|
Yes, I did click "apply". With different settings I get a different set of segments, but every time the GUI seems to process around the same length of the input file (18 seconds). I did not actually tried to process the file with different segmenting rules as in all cases it seems to be too little segments. |
|
Please test with this snapshot: https://mediaarea.net/download/snapshots/binary/dvrescue-gui/20241027/dvrescue_GUI_24.07.20241027_Mac.dmg |
|
That's a mixed bag. I was able to get the packages with the new snapshot. I needed to provide analysis XMLs by using CLI since the GUI would do nothing when adding captures on the Analysis screen. I realised though I have filled a bad issue. I wanted to merge 4 different captures of a tape. Using CLI I've only got around a minute of footage which resembled the first scene of the capture so I thought I need to package first and then run merge on each part separately. I can fill a separate issue or try packaging first and merge individually packaged files. Unless .mkv merging is not supported as there is no possibility in the GUI to package to .dv. |
|
I believe I'm having the same? a related? issue with packager. I'm using the GUI, version Nov 2, on a Mac mini M1 running Sequoia 15.1 No matter what segmentation rules I select, the total length of files output is only 10 or 11 seconds from a file over a minute long. Here's the dv file I was working with: dv and xml I packaged once with no segmentation rules. Here's the resulting mkv + logs + a screenshot: Drive link Then packaged once again, segmented by record time breaks: Drive link Every time I see an error in the logs that says If I'm misunderstanding and this is a separate thing, feel free to open a new issue. |
@dariuszseweryn yes, merging prior to packaging is the most efficient method. Are you able to use merge with the DVRescue CLI? If you don't mind, trying merging first and then packaging, that would be really helpful for diasnosing the specific issue you are having or if that resolves it. @g-maxime @ElderOrb @dericed FWIW, I have also had mixed results using merge in the GUI with recent daily builds. For some files, it works as expected, but for others I experience the same thing as described here (GUI hangs and I eventually have to force quit the app). |
|
I have ran merging using CLI. Seeing all those missing 5 frames I start to wonder if the problem is that my footage is PAL, not NTSC. The resulting file has a little more than 5 seconds length when played back. If I can add more info — please point me what you would like me to do. CLI log in here |
|
@dariuszseweryn just to confirm, the deck you are using is in PAL mode during recording, right? @dericed PAL footage should be detected by the CLI and should merge and package correctly, yeah? |
|
@libbyhopfauf judging from the first post's table it was correctly identified as an 25 FPS video. I used the original camcorder to capture — it's user's manual states that it is PAL only, so I don't think I could switch to NTSC by chance? |
That sounds right to me! Based on this issue it sounds like there is a possibility that the video switches modes (from NTSC to PAL), like the creator started recording in NTSC for the first segment and then started recording again in PAL? Or possibly a bad DV overwrite of a tape that was originally recorded as NTSC, but was erased and recorded as PAL. I'm sorry I haven't had a chance to work with any DV tapes recorded in PAL, so I'm not sure if it's a tape error or if there's an issue with dvpackager. @dericed is there a chance that packager is always expecting NTSC? It does seem oddly consistent that the report keeps saying there are 5 frames missing. |
|
@libbyhopfauf What program could I use to throughly examine the captured file? AFAIK the tape was used only one time, never overwritten. The camera does not have NTSC option — at least in the user interface. The first post's log seem to indicate that all entries are PAL 720x576/25FPS. |
|
@dariuszseweryn it definitely sounds like those aren't a factor then. You can use the dvanalysis tab or the dvplay -x command to review changes and issues with the file. If you are able to share the file, we could also take a closer look at it. |
|
dvplay -x, an excerpt (I did not wait till the end — should I?): As for the sharing file. Is one enough (~14 GB) or should I share all of them (x4)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OSX: Big Sur and Monterey
Camera: Samsung VP-D101
Tested with CLI only.
Original file captured using
ffmpeg-dlas per this tutorial. Also trieddvrescuecapture but the result is the same.What I tried so far:
chmodthe output location to774sudo-F ffmpegI cannot find the problem, a solution. Is there possibility to debug further the problem?
Seemingly related: #726
The text was updated successfully, but these errors were encountered: