-An option (for the -rall and -rgd modes) so that the C2 pointers are used only for purely informative purporses, without absolutely re-reads, like the old PerfectRip does. I mean the program will read and dump into a .c2/.c2e file the raw C2 pointers provided by the drive, but won't re-read anything marked as bad by the C2 pointers. This way I will know if a rip is good (no further action required) or bad: to resurface and clean the CD until getting 0 C2 errors, to try another drive, to try another read speeds or simply replace the CD if nothing works to get a flawless dump without re-reads. Of course, the log file should report if the dump was flawless or not flawless.
-The suggestion posted above applied to the -ra mode as well. And I would like that you could implement offset correction for the -ra mode: it would apply, as default option, the standard one defined by the AccurateRip database plus the possibilty of override it via the add parameter implemented in the -rall mode.
The same one for main channel / 8, because there are 2352 bytes for main channel and 294 bytes (one bit per byte of main channel) for C2 pointers. And this way will proceed PF if you enter 0 as c2 read offset correction bit(s).
On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator:link To write properly occidental characters contained in japanese titles:screenshot Spaces must be the fullwidth variant:link / screenshot
C2 switch for GD-ROM ripping does work now, but unfortunately the dumped .sub is invalid (contains non-sense data). Without C2 switch the .sub is valid and the extra frame is no longer present. Anyway, the actual dump (with/without C2 error reporting) matches the expected.
The same one for main channel / 8, because there are 2352 bytes for main channel and 294 bytes (one bit per byte of main channel) for C2 pointers. And this way will proceed PF if you enter 0 as c2 read offset correction bit(s).
In case of Plextor drive, how many is the values of c2 read offset correction bit(s)?
The read offset you are applying in bytes for that dump in bits.
To dump a CDDA disc, standard offset correction for a +30 Plextor drive:
+30 samples / +120 bytes --> 120 bits.
To dump a Saturn game, +18 write offset and +30 Plextor drive:
+48 samples / 192 bytes --> 192 bits.
To dump the Tenbu Mini Audio CD, add 13 and +30 Plextor drive:
+43 samples / 172 bytes --> 172 bits.
On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator:link To write properly occidental characters contained in japanese titles:screenshot Spaces must be the fullwidth variant:link / screenshot
Last edited by pablogm123 on Thu Nov 21, 2013 12:18 pm, edited 1 time in total.
On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator:link To write properly occidental characters contained in japanese titles:screenshot Spaces must be the fullwidth variant:link / screenshot
it seems that DiscImageCreator doesn't detect PregapMode (ccd value) and always sets it to '0', even though many discs have a different value there.. PSX discs need PregapMode 2.. can you fix it so that the correct PregapMode is obtained from the disc?
it seems that DiscImageCreator doesn't detect PregapMode (ccd value) and always sets it to '0', even though many discs have a different value there..
I have recognized it and want to fix it. But I don't know about "PregapMode" and "PregapSubC", "DataTracksScrambled" in detail. Therefore, I always sets it to '0'.
Last edited by sarami on Fri Nov 22, 2013 9:07 am, edited 1 time in total.
