Search options (Page 39 of 66)

Pregap/Lead-In sectors are read randomly, you can read the -5000...-1100 area a couple of times and get different sectors each time. I think, DIC needs a special mode to read that area a couple of times and reconstruct the whole lead-in sector-by-sector.

READ_TOC(0x43) doesn't output the data area, though, only subs

Dumping lead-out is interesting. Why "6750 sectors"? Lead-out sectors go upto the very end of the disc. If the main data area is small (a few megabytes), the lead-out would be 300 000+ sectors.

https://github.com/libretro/libretro-da … Saturn.dat -- versions look useless and distracting here. As well as publishers.

PS2 (as well as Sega systems) versions aren't tied to revisions, so you can't easily predict the missing ones. Like, http://redump.org/disc/39485/ is v1.04, but if to name it according to the version/revision, it should be v1.0/Rev 0 due to its ringcode that ends with "1". http://redump.org/disc/22458/ -- v2.01, ends with "1", so the earlier ones, like v2.00, don't exist _for this serial_ (which differs from the original release, which is http://redump.org/disc/15921/ which is v1.01, ringcodes end with 4 and 5, so it's worth to look for 1 or 2 with the possible v1.00 inside). TimeSplitters v2.00's ringcode ends with "4" and you can't say for sure, whether "1", "2" and "3" would differ or not until you find and dump all the missing rings.

Still, nothing bad in calling it (v1.01) to motivate people to look/check for (v1.00). Again, as far as I understand, No-Intro names their roms according to the version/revision, if known, even if the existence of the earlier ones is only suggested, not proven.

Why do you need to know the version? What does it tell you?

You either need to buy a specific drive that supports 0xD8 reading command or you can try to use the swapping - http://forum.redump.org/post/60603/#p60603

I've just checked its Windows build and I couldn't get any CDDA sound of it, so I'm not sure if it's truly supports Redump-style gdis. Also it crashes every time you try to close it and doesn't seem to support the controllers. Maybe the Android build is better, but clearly not the Windows one.

The process and tracks will be the same, just the db should generate cues instead of broken gdis.

I don't think everything will need to be redumped, non-zero data doesn't go upto the very end of the last track, so the offset can be fixed quite safely, we just need to define some standard.

I still insist on switching to 2xcues+bins

Нет, я про более ранние косяки с аудиотреками и их прегапами из-за которых по всем последующим дампам возникали вопросы. По точности верификейшнов в том числе. Вопросов не будет в случае дампов с плекстора, но условно удовлетворительные результаты можно попробовать получить и на обычном приводе (речь, ессно, про диски с аудиотреками). В идеале хотелось бы и передампы тех, что уже в базе.

http://redump.org/disc/8335/ -- this one was released in Asia and then rereleased in Japan, What do you think, shoudn't it be (Asia, Japan)?
I don't think No-Intro ever faced such issues, so it's pointless to look for examples in their dats.

The logs in the first post are from the March DIC version, which isn't the most recent one (there were CD-i Ready-related fixes a week ago, you should get a different track 1 checksum with the May version).