DiscImageCreator (Page 7 of 141)

The PX-116A2 is a rebadged PIONEER-121 according to "the internet".

We even listed the known working ones...

It would be cool if this tool could act as CDtoIMG-D8 replacement with C2 reporting (which works properly, of course) + offset correction (manually entered or automatically detected) + subcode dump (D8 + C2 isn't supported, whereas D8 + C2 + Sub96 is supported), without unscrambling/splitting/other kind of postprocessing this D8 dump.

F1ReB4LL: the scramble.bin file I think is the EOR decryption key for scrambled sectors. IIRC it's nothing more than that to scramble a sector, there is no weird math like some people think.

WIP
http://www.mediafire.com/download/de7fhhiaq4z8vla/
c2: re-read until 80 times (80 is magic number at present.)
this coding is very slow, so impractical..

Oh good, I will test the C2.

I got a very strange bug when dumping 7th Guest disc 1. When unscrambled there were ~50000 errors because the headers were decoded wrong. Other tools dump the disc fine.

No, I didn't use the new version of DIC to dump that, I used the last one. So not with C2. Also it was the older dump I made of the OEM version.

Very strange that it happened at all and didn't give any error. There was subcode desync in the log however, maybe that was the reason.

I will do it again and see if that same bug occurs again. If it does, I will compress it all and upload it somewhere for you to look at.

A friend of mine with Plextor PX-W5224A, has problem with his drive reporting tons of C2 error. It has same firmware as mine and same hardware revision. Dumps are OK though... very strange! EAC does not report C2 error when ripping audio.

Just a warning for sarami, when dumping Main + C2 + Sub you have to correct the offset of main channel and the offset of the C2 pointers.

For example, if the autodetected offset correction for the main channel is +48 samples / + 192 bytes, you have to apply 192 bits (192 bytes / 8) offset correction to the C2 pointers provided by the drive.

@F1ReB4LL: what's about the method used by the dBpoweramp CD Ripper? And perhaps is useful as inspiration for sarami. It's the commercial program (I bought a licence a year ago) I use to rip my music CDs into my music library.

Roughly it does this:

-Read one given track once. If no C2 error reported, encode to the final file. If C2 errors are detected, will make rereads taking into account the C2 pointers.

-It will try to get 10 identical reads and not marked as bad by the C2 pointers, until it can get those identical 10 reads not marked as bad or reach the maximum number of rereads allowed (you can configure any extreme numbers of rereads, like 2000/5000/10000 rereads, the developer suggests 750 if you own a drive with decent C2 error reporting). If cannot obtain 10 identical rereads not marked as bad, but could obtain a certain reread not marked as bad, it will use this one.

-Of course, the program needs to know the ammount of audio that the drive caches (can autodetect that) to defeat properly the cache when performing the rereads. Or if you own a real Plextor drive, you can enable the FUA mode to defeat fastly the cache without rereading useless data.

For example, ripping this music track detected 10 bad sectors (according to C2 pointers), and reread these ones until it could obtain 10 identical rereads not marked as bad. c2 dropped n means the number of rereads discarded because at least there is one corrupted byte.

Track 4:  Ripped LBA 71463 to 94145 (5:02) in 9:07. Filename: C:\Extraído\Prodigy, The\Music for the Jilted Generation\04.wav
  Secure (Warning)  [Pass 1, Ultra 1 to 1, Re-Rip 10 Frames]
  CRC32: A7A75304
    Re-rip Frame: 72283 (00:00:10,920) matched 10 / 12  (c2 dropped 156)
    Re-rip Frame: 74723 (00:00:43,453) matched 10 / 12  (c2 dropped 4)
    Re-rip Frame: 81020 (00:02:07,413) matched 10 / 12  (c2 dropped 473)
    Re-rip Frame: 81021 (00:02:07,426) matched 10 / 12  (c2 dropped 763)
    Re-rip Frame: 81480 (00:02:13,546) matched 10 / 12  (c2 dropped 5460)
    Re-rip Frame: 81876 (00:02:18,826) matched 10 / 11  (c2 dropped 1)
    Re-rip Frame: 82211 (00:02:23,293) matched 10 / 11
    Re-rip Frame: 83303 (00:02:37,853) matched 10 / 11  (c2 dropped 2)
    Re-rip Frame: 84605 (00:02:55,213) matched 10 / 12  (c2 dropped 123)
    Re-rip Frame: 90379 (00:04:12,200) matched 10 / 12  (c2 dropped 75)

>pablogm123
Thanks info.
>F1ReB4LL
Thanks advice.

WIP2
http://www.mediafire.com/download/u0olo2c51f2qv13/
-Support C2 error Flag on D8 command.
-if C2 error bit off & 2 different results, reread.

Looks good here, but you've done it not the way I've said. You're trying to fix each sector right after the error was found. And I still think it's better to read all the sectors "as is", make a list of incorrect ones and reread them after all the sectors were read. That should give better results, since when you read 1 sector many times, it may return cached results and when you reread all bad sectors in a batch after you have dumped the whole disc, you can be sure no caching is involved As I've said already, Subdump works exactly this way and it's usually good in fixing read errors.

Other than that, it definetely works now.

If you add hashing, I would prefer that they can be outputted in clrmame format for using in the newdisc menu.

I think that F1REB4LL's suggestion of error correction be used so we can be sure that the cache is defeated on re-read.

:EDIT:

Got testing results back from other person with different HW revision 5224a.

DIC w/C2 is now functioning properly with his drive. =]

So what is the recommened version now? WIP2? Or isn't it tested enough yet?