mipops / dvrescue

Archivist-made software that supports data migration from DV tapes into digital files suitable for long-term preservation. Snapshot daily builds are at https://mediaarea.net/download/snapshots/binary/dvrescue/.
BSD 3-Clause "New" or "Revised" License
94 stars 20 forks source link

dvpackager GUI - handling failed files #686

Open libbyhopfauf opened 1 year ago

libbyhopfauf commented 1 year ago

I had a few files in a queue of 10 files (packaging from 3 files) and two of them got the little X (fail) icon in the queue, but when I opened them they played fine. At first I thought this might happen when a segment happens to end with a timecode break at the last frame. For the first two times it happened in my particular instance, the two files that failed to encode did end with a timecode break, but since then, not all files that end that way fail, but most of the ones that fail do contain a timecode break. See images below and example files here. Screen Shot 2023-03-22 at 5 54 45 PM

Screen Shot 2023-03-22 at 6 00 52 PM

libbyhopfauf commented 1 year ago

After the dvpackager process runs there's a bunch of checks to make sure everything is as expected (like that the source and output have the same frame counts). Currently we have 3 error codes:

Originally posted by @dericed in https://github.com/mipops/dvrescue/issues/617#issuecomment-1482956244

libbyhopfauf commented 1 year ago

@dericed That's super helpful to know about the error codes! I think for "missing file" we could continue using the fail icon and add a hover message that says the file is missing. For the other two errors, we could one of two things:

Let me know what you think!

dericed commented 1 year ago

For 'missing-file' I suppose the output error is thus handled from ffmpeg. It means the output file was never written, which could happen because the output directory is write-only, or the command to ffmpeg is invalid, or some other reason.

btw with the file that gave the error can you paste in the terminal output of the command line process of dvpackager, it would be worthwhile to address that error too.

libbyhopfauf commented 1 year ago

@dericed

For 'missing-file' I suppose the output error is thus handled from ffmpeg. It means the output file was never written, which could happen because the output directory is write-only, or the command to ffmpeg is invalid, or some other reason.

btw with the file that gave the error can you paste in the terminal output of the command line process of dvpackager, it would be worthwhile to address that error too.

Sure thing! I'll see if I can recreate it and send you what I get.

No problem! I'll work on some mock-ups next week for both the documentation and the icons!

  • Also maybe we should change the term from 'missing-file' to 'ffmpeg-error' since that's more accurate to what happened.

I think that makes more sense!

libbyhopfauf commented 10 months ago

How about these icons for the three issues?

Screenshot 2023-12-08 at 3 07 27 PM

Is there a way to resolve any of these? Like it would be good if we had hover tips or at least a key for them in the documentation like we do for dvanalysis that gives suggestions to resolve or at least explains how the error likely occurred. Or are these just files that dvpackager can't work with?

libbyhopfauf commented 3 months ago

@dericed what about these instead?

Screenshot 2024-06-19 at 4 00 40 PM

They would look like this in the GUI (and would have a hover tooltip):

Screenshot 2024-06-19 at 4 04 39 PM Screenshot 2024-06-19 at 4 05 43 PM Screenshot 2024-06-19 at 4 22 15 PM
dericed commented 2 months ago

@libbyhopfauf got icons?

libbyhopfauf commented 2 months ago

@dericed Sure do! See https://github.com/mipops/dvrescue/pull/894