However, it doesn't look like Redumper prints which sectors these affect anywhere? Ideally, it would be cool if Redumper ran a final EDC/ECC check on the data tracks (like EDCCCHK) and printed out a list of sectors that contain P, Q, and EDC errors, particularly in its own log file. The reason for this is because there will be discs that might have no C2 errors, but baked in EDC/ECC errors. Error discovery should have the highest priority, so logs should be generated in their own file for error discovery to make things easier. This way, if I dumped a disc and I saw that my edc/ecc error log file is 0kb, then I know there are no errors to worry about for the data tracks. But if I dumped a disc and I have something in my log file, it needs to be investigated to figure out why.
Currently, Redumper does print a count of the amount of sectors that fail ECC and EDC checks when splitting.
data errors [beatmaniaprotosaz (Track 0).bin]: ECC: 3922 EDC: 3952 CD-XA SubHeader mismatch: 671 redump: 4630However, it doesn't look like Redumper prints which sectors these affect anywhere? Ideally, it would be cool if Redumper ran a final EDC/ECC check on the data tracks (like EDCCCHK) and printed out a list of sectors that contain P, Q, and EDC errors, particularly in its own log file. The reason for this is because there will be discs that might have no C2 errors, but baked in EDC/ECC errors. Error discovery should have the highest priority, so logs should be generated in their own file for error discovery to make things easier. This way, if I dumped a disc and I saw that my edc/ecc error log file is 0kb, then I know there are no errors to worry about for the data tracks. But if I dumped a disc and I have something in my log file, it needs to be investigated to figure out why.