651

(3,497 replies, posted in General discussion)

[ERROR] Number of sector(s) where bad MSF: 2
        Sector: 14098, 14099,
[ERROR] Number of sector(s) where user data doesn't match the expected ECC/EDC: 1
        Sector: 14097,
[ERROR] Number of sector(s) where sync(0x00 - 0x0c) is zero: 1
        Sector: 901,

In fact, the damaged sectors are 14097, 14098, 14099 and 14100. Why does it say 901 instead of 14100? DIC is probably using a wrong algorithm to show the sector numbers.

652

(17 replies, posted in General discussion)

iR0b0t wrote:

10. Total CRC-32

I cannot do a database dump of it, Total CRC-32 is not stored within the database, its generated on the fly each time you review a disc page.

Every time when you open the page or every time when you edit the page? If the latter, it should be saved somewhere?

The current REM LEAD-OUT "standard" is used to define the address in the bin _image_ (not track), where the last track of the session ends. And, since we don't use the single bin images, we need 2 new commands to show the CD emulator/burner/whatever_other_tool to insert the needed amount of lead-out and lead-in sectors to fill the gap between tracks.

Jackal wrote:

Looking there and also at other example cuesheets, IsoBuster seems to use only REM LEAD-OUT and REM RUN-OUT.

Yeah. It basically shows where the last session of the first track ends with the REM LEAD-OUT command. And the next track entry shows where the first track of the next session begins. The actual lead-out sectors of the first session/lead-in sectors of the second session/pregap are 'just there' undescribed.

But if we want these to be split to tracks, we need to describe how many lead-out sectors to generate and how many lead-in sectors to generate.

But if it reads all the sectors, why does it need the SS ranges? smile

DiscImageCreator.exe xboxswap F: dump 8 290540 445728 603308 759356 912208 1298824 1449692 1610286 1979736 2289920 2448012 2601336 2836428 2990638 3298528 3456316 /nss 2
AppVersion
        x86, AnsiBuild, 20190413 103735
/nss val is omitted. set [100]
Unknown option: [2]
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

DiscImageCreator.exe xboxswap F: dump 8 /nss 2 290540 445728 603308 759356 912208 1298824 1449692 1610286 1979736 2289920 2448012 2601336 2836428 2990638 3298528 3456316
AppVersion
        x86, AnsiBuild, 20190413 103735
[/nss] is invalid argument. Please input integer.
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

Still doesn't work.

Doesn't work?

DiscImageCreator.exe xboxswap F: dump 8 /nss 2
AppVersion
        x86, AnsiBuild, 20190407 215226
Invalid argument
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

DiscImageCreator.exe xboxswap F: dump 8 /nss 2
AppVersion
        x86, AnsiBuild, 20190413 103735
Invalid argument
Usage
        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
...

I think you've probably missed the IFPI codes? One of them is usually on the ringcode and written with smaller text, another one is usually pressed on the mould (sometimes only 4 symbols without the "IFPI" acronym).

Welcome, obtain your password here.

(check the spam folder in case there will be no message in your inbox)

Please make sure you read and understand the dumping process and the way you have to submit the dumping logs before posting your dump info.
Dumping Guides

Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord

659

(1 replies, posted in Guests & account requests)

Welcome, obtain your password here.

(check the spam folder in case there will be no message in your inbox)

Please make sure you read and understand the dumping process and the way you have to submit the dumping logs before posting your dump info.
Dumping Guides

Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord

redpants3 wrote:

Was also wondering where the PS3 database is because I don't see any PS3 titles in redump.org.

Dump something first smile

Welcome, obtain your password here.

(check the spam folder in case there will be no message in your inbox)

Please make sure you read and understand the dumping process and the way you have to submit the dumping logs before posting your dump info.
Dumping Guides

Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord

Jackal wrote:

I'd say go with the IsoBuster standard. If it has REM LEAD-IN [MSF] and REM LEAD-OUT [MSF] then fine. Adding custom stuff isn't going to help us in any way.

Erm. IsoBuster allows to map the sessions with their lead-ins/lead-outs only inside a single bin+cue image, it doesn't support split tracks. We need to do the custom stuff in any case. And my idea stated above is to show the amount of inserted generated sectors. Like the PREGAP 00:02:00 and POSTGAP 00:05:00 commands => REM LEAD-OUT 00:03:00 and REM LEAD-IN 00:02:00 (or something similar to not to conflict with native IsoBuster commands).

Readd him properly (linked to the nick).

IIRC, after the REM SESSION 02 there goes REM LEAD-IN [MSF]. Because after the last sector of the 1st section there are a number of Lead-out sectors and after them there are Lead-in sectors of the 2nd session. You need to generate both to have the correct LBAs for the 2nd session tracks.

What would you like to contribute?

How are you going to get the correct LBAs if you exclude the lead-out/lead-in sectors?

No, dreamcast is a special case, it's not a multisessional disc, it's a disc with 3 independent areas and 3 independent TOCs (SD area, logo area, HD area). They don't need to be connected because the SD area's leadout always ends exactly at 24600, the ring area always starts at 24941 and ends at 38690 and the HD area always starts at 49850. These values cannot be changed, so you don't need the multisessional TOC with the sessions addresses in it. And you don't need to define the sessions, mirror zones and other stuff in cue, because these values should be precoded in the emulator.

And for the multisessional discs you always have the 'main' TOC where all the sessions are listed, so you need to fill the lead-out and lead-in gaps somehow to not to ruin the addressing.

668

(3 replies, posted in Guests & account requests)

Welcome, obtain your password here.

(check the spam folder in case there will be no message in your inbox)

Please make sure you read and understand the dumping process and the way you have to submit the dumping logs before posting your dump info.
Dumping-Guides

Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord

669

(2 replies, posted in Guests & account requests)

Welcome, obtain your password here.

(check the spam folder in case there will be no message in your inbox)

Please make sure you read and understand the dumping process and the way you have to submit the dumping logs before posting your dump info.
Dumping-Guides

Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord

Welcome, obtain your password here.

(check the spam folder in case there will be no message in your inbox)

Please make sure you read and understand the dumping process and the way you have to submit the dumping logs before posting your dump info.
Dumping-Guides

Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord

sarami wrote:

I think 'REM LEAD-IN' and 'REM LEAD-OUT' don't need in multi-session's cue of multi-track (redump'org) format.
1. Because multi-session's cue of multi-track format doesn't have lead-in area and lead-out area.

We need our own variants of these to show the amount of Lead-In and Lead-Out sectors to generate (similar to PREGAP and POSTGAP commands) - http://forum.redump.org/post/67312/#p67312

Lizard wrote:

Thank you! I'll try to do my best smile

Try to start checking your own entries, whether all your submissions were properly added with all the ringcodes smile

673

(3,497 replies, posted in General discussion)

Hashing doesn't take much time. At least CRC32 is needed, but even all 3 checksums don't take more than a couple of seconds unless we're talking about 50GB blurays.

674

(3 replies, posted in Guests & account requests)

Some examples, maybe?

675

(3 replies, posted in Guests & account requests)

Including all the Japanese demo ones? Interesting.
--


Welcome, obtain your password here.

(check the spam folder in case there will be no message in your inbox)

Please make sure you read and understand the dumping process and the way you have to submit the dumping logs before posting your dump info.
Dumping-Guides

Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord