This is a feature request for the logging to help dealing with disc read errors and whether they actually matter that much or not. My specific use case is doing full copies of discs. This is for large NAS (80TB) and playback via a device (DuneHD) which can play the disc from folder / ISO over network. Having said that, I have also done rips of specific episodes to mkv, which of course can be constructed with multiple files on disc (e.g. extended cuts, etc.). I’ve ripped about 20TB of stuff so far, fighting my way through Game of Thrones 4K box set (known for defects).
- When a read error occurs, the log file provides very basic info, e.g. “read error filling 0: 11 22773760 22781370 22777280 24”
- it would be very helpful if the error log could flag the specific file (e.g. 00123.m2ts) that will be filled with 0 so I can then go look at it in the output folders. [EDIT - I just figured out the # of the .m2ts file is at the end of the read error line]
- I can sort of guess at what that read error is (looks like a block with start and end address, then position of the error, not sure after that). Would be nice to have a legend for that somewhere.
I’ve spent a bunch of time doing multiple rips of full discs and doing diffs (e.g. WinMerge) between the multiple different output folders looking for any files that mismatch, which is a strong indicator that those files are actually the ones that had errors because the errors will probably be slightly different on each run. Many times, the file with errors are the little 20 second long (15MB) m2ts files with the copyright warning in many different languages. I may not have a perfect copy of the disc, but those files do not really matter. What I want to know - upon error - is what files the errors are in. [EDIT See above] Then I can determine what I need to do about it.
Also, if there is any more info about the error that can be provided, that would be helpful. I’m not sure this is completely possible or not, but it would be great to know what layer and the radius from the center of the disc so that I can hunt for the offending dirt, scratch, or defect. I’m assuming that based on the disc “type” (e.g., BD100) and the sector, that information should be fairly straight forward to calculate.
Is there good spot for little UI/UX or other reports for little (some very minor) usability comments / suggestions?
Thanks!
[EDIT - adding items]
It would be incredibly useful to have a log spit out for each disc separately, that way I can compare the logs to see where the errors were on multiple runs.
BUG? I left a rip going for hours that I already knew would have issues. I wanted the smallest amount of 0 fill possible, so I set the “skip sectors after a reading error” to 0. Looks like that ended up never moving forward to the next sector, so it sat for hours and hours try to read the same error sector. I assumed that “0” would mean the number of sectors after the error to skip and assumed the error condition would just cause it to move to the next sector. Maybe I am not understanding this?
