Need Help - Consistent Different Dumps - DIC vs ReDumper

[Urk]

Hi,

When I started submitting discs, I mostly used Redumper. Then, I saw that DIC was better, in particular with mixed Data-Audio discs, so...
I'm in the process of redumping all my discs with DIC & Redumper to ensure all my dumps are correct.

I need help to figure out a weird situation with 3 discs.

The two firsts are covermount games that have not been submitted yet. (iM1A2 Abrams & Take No Prisoners).
(Single track/Not mixed discs)

I dumped each game 4 times :
- 2 times with Redumper (1x & 4x)
- 2 times with DiscImageCreator (1x & 4x)

And... I get consistent different dumps.

Redumper consistent dumps differs from DiscImageCreator consistent ones.

The thrid game is Heroes of Might & Magic II (That have been submitted : https://redump.info/disc/118659/)
(Mixed disc)

I just redumped this game six times.
- 3 times with Redumper (1x, 4x & 8x)
- 3 times with DiscImageCreator (1x, 4x & 8x)

And again, I get consistent differents dumps between Redumper & DiscImageCreator.

All the discs are in a good shape, no scratches, no moisture.

The question is : Which dumps should I trust to be the good ones : DIC dumps or Redumper dumps ?

Your help would be appreciated

Regards,

[Deterous]

In what way did you think that DIC is better?
If you can then dumping with both can help ensure the dump is good, but Redumper is recommended for the majority of discs.

As for why the dumps are different, the logs give hints as to non-zero errors, invalid sync sectors.
There are some scenarios that Redumper and DIC deal with unexpected sectors differently.
I would have to look at the logs closer to be sure.

Also, please update your MPF to the latest version (3.3.0) which contains the recommended version of Redumper and has fixed a lot of bugs.

[sarami]

And again, I get consistent differents dumps between Redumper & DiscImageCreator.

Pregap length of track 30 and 32 is different.

All the discs are in a good shape, no scratches, no moisture.

Last subQ all tracks and second subQ from the last of all tracks is weird. It seems a mastering issue.

[Urk]

In what way did you think that DIC is better?

Oh, I think I read that in some forums. I thought that it was the reason why Redumper was later accepted than DIC for dumps.
I assume that I'm wrong

Also, please update your MPF to the latest version (3.3.0) which contains the recommended version of Redumper and has fixed a lot of bugs.

Done ! I'm on 3.3.0 now !

I redumped these 3 discs with the new MPF version, but get the same results.

[Urk]

Pregap length of track 30 and 32 is different.

Last subQ all tracks and second subQ from the last of all tracks is weird. It seems a mastering issue.

Doesn't ReDump & DIC should read the same pregap lengh & SubQ infos as they read discs at block level ?

I'm not expert enough to decide which dumps are to be considered corrects ^^

[sarami]

I'm not expert enough to decide which dumps are to be considered corrects ^^

As far as the logs are concerned, DIC is correct.

[Deterous]

I thought that it was the reason why Redumper was later accepted than DIC for dumps.

Redumper is new, that is why it is only recently accepted.

Both tools are dumping the exact same data from the discs, the difference is in how they are doing post-processing.
For the Might & Magic disc, they just split at different locations. DIC has identical pregap lengths for all tracks, Redumper has different pregap for Track 30 and 32. For this disc, it is due to the subcode desync messages, likely needs to be fixed (Redumper currently incorrect splits). I have fixed redump.org hashes to include the DIC splits (Tracks 29-32 have changed).

For the other two discs, they have some invalid sectors (one of which is EDC/ECC error). DIC and Redumper treat these errors differently, hence the different hashes. It is likely that redumper's method here is preferred. These are all the test cases that Redumper uses when determining what to do with invalid/unexpected sectors: https://github.com/superg/redumper/tree … unscramble

[sarami]

To:Deterous

01_invalid_sync.0.pass
10_invalid_mode_zeroed_intermediate.0.pass
11_invalid_mode_non_zeroed_intermediate.0.pass
12_invalid_mode_non_zeroed_intermediate_last_byte.0.pass

Can you explain from the CD specifications why this sector is unscrambled?

03_mode0_zeroed_data.0.pass
04_mode0_non_zeroed_data.0.pass
05_mode0_non_zeroed_data_last_byte.0.pass

User area of the mode 0 sector is all zero. It's CD specifications. But I confirmed that other software also treats as no error sector. I'll fix this case.

16_msf_mismatch_invalid_sync.42.fail
:
:
45_no_msf_invalid_mode_no_intermediate_max.null.fail

What is the "msf_mismatch" and what is the "no_msf"? It seems msf of test data is normal (00:02:00).

[Deterous]

I will see if superg can respond to your questions, better than I could.

[Urk]

Deterous, I think you forgot to update the Error Count on the page https://redump.info/disc/118659/

Error Count : 2