Redumper - Revision history

>Deterous at 08:38, 6 April 2026

2026-04-06T08:38:54Z

← Older revision		Revision as of 08:38, 6 April 2026
Line 172:		Line 172:
	CD lead-in consists of RAW TOC and 2 seconds (150 sectors) of pre-gap. Good PLEXTOR drives can read last second of pre-gap the usual way and TOC with first second of pre-gap by utilizing PLEXTOR negative LBA range reading. PLEXTOR is the only drive that is currently known to provide such a functionality.		CD lead-in consists of RAW TOC and 2 seconds (150 sectors) of pre-gap. Good PLEXTOR drives can read last second of pre-gap the usual way and TOC with first second of pre-gap by utilizing PLEXTOR negative LBA range reading. PLEXTOR is the only drive that is currently known to provide such a functionality.
	On the other hand, some good known LG/ASUS/LITE-ON drives are able to read a little bit less than 2 seconds of pre-gap (~135 out of 150 sectors) the usual way. However, what LG/ASUS/LITE-ON drives can't do, is to read RAW TOC and a small portion (~15 first sectors) of pre-gap.		On the other hand, some good known LG/ASUS/LITE-ON drives are able to read a little bit less than 2 seconds of pre-gap (~135 out of 150 sectors) the usual way. However, what LG/ASUS/LITE-ON drives can't do, is to read RAW TOC and a small portion (~15 first sectors) of pre-gap.
	When it comes to lead-out, good PLEXTOR can read ~100 lead-out sectors the usual way, good known LG/ASUS/LITE-ON drives are unable to read lead-out the usual way, but some amount of lead-out sectors can be extracted directly from the drive cache using vendor commands. The other promising development is ~~Rib's modified ASUS~~ firmware that fully unlocks lead-out reading (and he discovered ASUS cache read command in the first place)~~. Compatibility with the modified firmware is enabled as of redumper build 221~~.		When it comes to lead-out, good PLEXTOR can read ~100 lead-out sectors the usual way, good known LG/ASUS/LITE-ON drives are unable to read lead-out the usual way, but some amount of lead-out sectors can be extracted directly from the drive cache using vendor commands. The other promising development is [[OmniDrive]] firmware that fully unlocks lead-out reading (and he discovered ASUS cache read command in the first place).

	===PLEXTOR Lead-In Notes===		===PLEXTOR Lead-In Notes===

>Deterous at 09:18, 24 January 2025

2025-01-24T09:18:55Z

← Older revision		Revision as of 09:18, 24 January 2025
Line 218:		Line 218:
	* current release: [https://github.com/superg/redumper/releases/latest GitHub]		* current release: [https://github.com/superg/redumper/releases/latest GitHub]
	* past releases: [https://github.com/superg/redumper/releases GitHub]		* past releases: [https://github.com/superg/redumper/releases GitHub]
	* "Best Possible" dump batch file (for completing dumps with c2 errors - use sparingly, for one-of-a-kind discs) - COMING SOON!

	[[Category:Applications]]		[[Category:Applications]]
	[[Category:Moderation Guides]]		[[Category:Moderation Guides]]

>Mictlantecuhtle at 15:05, 23 July 2024

2024-07-23T15:05:40Z

← Older revision		Revision as of 15:05, 23 July 2024
Line 221:		Line 221:

	[[Category:Applications]]		[[Category:Applications]]
			[[Category:Moderation Guides]]

>Mictlantecuhtle: /* Solution */ clarify Track 0/A requirements and naming

2024-07-23T15:04:00Z

Solution: clarify Track 0/A requirements and naming

← Older revision		Revision as of 15:04, 23 July 2024
Line 191:		Line 191:
	'''warning: lead-out contains non-zero data (session: {}, sectors: {}/{})''' (informational, guarantees that Track A/AA will be generated)		'''warning: lead-out contains non-zero data (session: {}, sectors: {}/{})''' (informational, guarantees that Track A/AA will be generated)

	If Track 0 and/or Track A/AA are generated, the hashes should be added to the comments field, example: [https://redump.info/disc/39873 Oyaji Hunter Mahjong]. Track 0 should be named as "leadin.bin" and Track A/AA should be named "leadout.bin" to keep things uniform. The original Track 0 and Track A/AA naming scheme is used by redumper just to sort files in a natural order, that is lead-in before Track 1 and lead-out after the last track. In case if multisession CD with non-zero data in lead-in/lead-out, the redumper naming scheme is Track 0.<session number> and Track A/AA.<session number> respectively yet no such disc was discovered at the time of writing (11/20/2022). The multisession uniform naming for this case is proposed to be "leadin<session number>.bin" and "leadout<session number>.bin" respectively. xmp tags have to be used in order to keep the entries tidy in comments, for the [https://redump.info/disc/39873 Oyaji Hunter Mahjong] that would be:		If Track 0 and/or Track A/AA are generated, '''for pure Audio CDs only''', the hashes should be added to the comments field, example: [https://redump.info/disc/39873 Oyaji Hunter Mahjong]. Track 0 should be named as "leadin.bin" and Track A/AA should be named "leadout.bin" to keep things uniform. Note that, at present, Track 0/A are not known to be useful for anything other than Audio CDs.

			The original Track 0 and Track A/AA naming scheme is used by redumper just to sort files in a natural order, that is lead-in before Track 1 and lead-out after the last track. In case if multisession CD with non-zero data in lead-in/lead-out, the redumper naming scheme is Track 0.<session number> and Track A/AA.<session number> respectively yet no such disc was discovered at the time of writing (11/20/2022). The multisession uniform naming for this case is proposed to be "leadin<session number>.bin" and "leadout<session number>.bin" respectively. xmp tags have to be used in order to keep the entries tidy in comments, for the [https://redump.info/disc/39873 Oyaji Hunter Mahjong] that would be:
	<xmp><rom name="leadin.bin" size="28981344" crc="34173ffb" md5="d4a1d46d6721ab93b3da1a130d3a5274" sha1="958b5a41456c90cb5c6df8d676c3d2d90a940609" /></xmp><xmp><rom name="leadout.bin" size="159936" crc="b4e470a3" md5="1f5dc334f2679331c2f6b3b26c198f01" sha1="545033f1a4ef0c9b7d98ff55e9127b6f4188121f"/></xmp>		<xmp><rom name="leadin.bin" size="28981344" crc="34173ffb" md5="d4a1d46d6721ab93b3da1a130d3a5274" sha1="958b5a41456c90cb5c6df8d676c3d2d90a940609" /></xmp><xmp><rom name="leadout.bin" size="159936" crc="b4e470a3" md5="1f5dc334f2679331c2f6b3b26c198f01" sha1="545033f1a4ef0c9b7d98ff55e9127b6f4188121f"/></xmp>

>User7 at 14:31, 9 December 2023

2023-12-09T14:31:30Z

← Older revision		Revision as of 14:31, 9 December 2023
Line 1:		Line 1:
	[https://github.com/superg/redumper '''redumper'''] is an open source optical disc dumping application for Windows and Linux (a macOS version is planned). The application is written by redump moderator superg.		[https://github.com/superg/redumper '''redumper'''] is an open source optical disc dumping application for Windows and Linux (a macOS version is planned). The application is written by redump moderator superg.

	redumper is designed to be very user friendly, a double click of the app will detect the occupied disc drive and account for unique caveat of discs.		redumper is designed to be very user friendly, a double click of the app will detect the occupied disc drive and account for unique caveat of discs. Additionally, see [[Dumping Guide (redumper CLI)]] for a guide on how to dump with redumper via command line and submit discs to redump.org.

	For a list of media types supported by redumper see [[Redumper status]].		For a list of media types supported by redumper see [[Redumper status]].

	~~See [[Dumping Guide (redumper CLI)]] for a guide on how to use redumper to dump and submit discs to redump.org.~~

	=Moderator Guidelines=		=Moderator Guidelines=

>Pelago: Linked to the guide, in case someone came to this page from a search for example

2023-12-08T18:27:33Z

Linked to the guide, in case someone came to this page from a search for example

← Older revision		Revision as of 18:27, 8 December 2023
Line 4:		Line 4:

	For a list of media types supported by redumper see [[Redumper status]].		For a list of media types supported by redumper see [[Redumper status]].

			See [[Dumping Guide (redumper CLI)]] for a guide on how to use redumper to dump and submit discs to redump.org.

	=Moderator Guidelines=		=Moderator Guidelines=

>User7 at 12:36, 31 October 2023

2023-10-31T12:36:33Z

← Older revision		Revision as of 12:36, 31 October 2023
Line 3:		Line 3:
	redumper is designed to be very user friendly, a double click of the app will detect the occupied disc drive and account for unique caveat of discs.		redumper is designed to be very user friendly, a double click of the app will detect the occupied disc drive and account for unique caveat of discs.

	redumper ~~is in an experimental stage of support for redump~~.~~org contributions.~~		For a list of media types supported by redumper see [[Redumper status]].

	~~=Media Support=~~
	* Supported: CD (CD-DA and most CD-ROM formats are fully supported)
	* Not Yet Supported: DVD, HD-DVD, Blu-Ray

	=Moderator Guidelines=		=Moderator Guidelines=

>Deterous at 00:05, 4 October 2023

2023-10-04T00:05:03Z

← Older revision		Revision as of 00:05, 4 October 2023
Line 176:		Line 176:
	CD lead-in consists of RAW TOC and 2 seconds (150 sectors) of pre-gap. Good PLEXTOR drives can read last second of pre-gap the usual way and TOC with first second of pre-gap by utilizing PLEXTOR negative LBA range reading. PLEXTOR is the only drive that is currently known to provide such a functionality.		CD lead-in consists of RAW TOC and 2 seconds (150 sectors) of pre-gap. Good PLEXTOR drives can read last second of pre-gap the usual way and TOC with first second of pre-gap by utilizing PLEXTOR negative LBA range reading. PLEXTOR is the only drive that is currently known to provide such a functionality.
	On the other hand, some good known LG/ASUS/LITE-ON drives are able to read a little bit less than 2 seconds of pre-gap (~135 out of 150 sectors) the usual way. However, what LG/ASUS/LITE-ON drives can't do, is to read RAW TOC and a small portion (~15 first sectors) of pre-gap.		On the other hand, some good known LG/ASUS/LITE-ON drives are able to read a little bit less than 2 seconds of pre-gap (~135 out of 150 sectors) the usual way. However, what LG/ASUS/LITE-ON drives can't do, is to read RAW TOC and a small portion (~15 first sectors) of pre-gap.
	When it comes to lead-out, good PLEXTOR can read ~100 lead-out sectors the usual way, good known LG/ASUS/LITE-ON drives are unable to read lead-out the usual way, but some amount of lead-out sectors can be extracted directly from the drive cache using vendor commands. The other promising development is Rib's modified ASUS firmware that fully unlocks lead-out reading (and he discovered ASUS cache read command in the first place). At the ~~time of writing, such~~ modified firmware is ~~not fully supported in~~ redumper ~~(12/19/2022) but such support will be completed soon~~.		When it comes to lead-out, good PLEXTOR can read ~100 lead-out sectors the usual way, good known LG/ASUS/LITE-ON drives are unable to read lead-out the usual way, but some amount of lead-out sectors can be extracted directly from the drive cache using vendor commands. The other promising development is Rib's modified ASUS firmware that fully unlocks lead-out reading (and he discovered ASUS cache read command in the first place). Compatibility with the modified firmware is enabled as of redumper build 221.

	===PLEXTOR Lead-In Notes===		===PLEXTOR Lead-In Notes===

>Superg: /* PLEXTOR Lead-In Notes */

2023-01-09T05:14:15Z

PLEXTOR Lead-In Notes

← Older revision		Revision as of 05:14, 9 January 2023
Line 179:		Line 179:

	===PLEXTOR Lead-In Notes===		===PLEXTOR Lead-In Notes===
	As described in the previous section, good PLEXTOR drives are able to read lead-in area using negative LBA addressing. Regardless of a starting point, such reads are "virtualized" by ~~Plextor~~ drive and will always start somewhere in the lead-in TOC area (no positional information in subchannel Q as TOC is stored there so drive isn't able to seek precisely). Consecutively reading sectors by using negative LBA range will read all TOC sectors from the starting point and pre-gap sectors will follow. However, any external pause between sequential reads (Debugger pause, sleep() call etc.) will lead to drive counter resetting and starting reading in the lead-in TOC area again.		As described in the previous section, good PLEXTOR drives are able to read lead-in area using negative LBA addressing. Regardless of a starting point, such reads are "virtualized" by the drive and will always start somewhere in the lead-in TOC area (no positional information in subchannel Q as TOC is stored there so drive isn't able to seek precisely). Consecutively reading sectors by using negative LBA range will read all TOC sectors from the starting point and pre-gap sectors will follow. However, any external pause between sequential reads (Debugger pause, sleep() call etc.) will lead to drive counter resetting and starting reading in the lead-in TOC area again.
	That said, the procedure is not flawless. Rarely, depending on some internal state, drive returns garbage and rebooting the drive usually helps. The other problem is that some particular PLEXTOR models return less data than expected and minimum required is at least 75 sectors (1 second). Getting first 75 sectors is enough as the other 75 sectors will be read later by the usual reading process thus full 2 seconds of pre-gap will be extracted.		That said, the procedure is not flawless. Rarely, depending on some internal state, drive returns garbage and rebooting the drive usually helps. The other problem is that some particular PLEXTOR models return less data than expected and minimum required is at least 75 sectors (1 second). Getting first 75 sectors is enough as the other 75 sectors will be read later by the usual reading process thus full 2 seconds of pre-gap will be extracted.

>Superg at 05:12, 9 January 2023

2023-01-09T05:12:34Z

← Older revision		Revision as of 05:12, 9 January 2023
Line 200:		Line 200:
	===Universal Hash===		===Universal Hash===
	By default, redumper outputs SHA-1 hash of the maximal non-zero span of the disc. Such hash is especially useful to match same audio discs with different write offset as the hashes for such cases would be the same, example: [https://redump.info/disc/77301 Chrono Cross: Music Selection].		By default, redumper outputs SHA-1 hash of the maximal non-zero span of the disc. Such hash is especially useful to match same audio discs with different write offset as the hashes for such cases would be the same, example: [https://redump.info/disc/77301 Chrono Cross: Music Selection].

	~~===Workflow===~~
	Each matching ringcode submission requires an additional non-zero start value entry in order to calculate disc write offset in relation to that value. It is recommended to use the earliest ringcode as a base (offset: 0) and all the following ringcodes with the relative offset to the base. Using the [https://redump.info/disc/77301 Chrono Cross: Music Selection] as an example, the workflow would be next:		Each matching ringcode submission requires an additional non-zero start value entry in order to calculate disc write offset in relation to that value. It is recommended to use the earliest ringcode as a base (offset: 0) and all the following ringcodes with the relative offset to the base. Using the [https://redump.info/disc/77301 Chrono Cross: Music Selection] as an example, the workflow would be next: