Audio CD Moderation Guide - Revision history

Sadikyo: Protected "Audio CD Moderation Guide" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2026-06-22T01:23:10Z

Protected "Audio CD Moderation Guide" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 01:23, 22 June 2026
(No difference)

>Mictlantecuhtle at 10:20, 26 January 2026

2026-01-26T10:20:28Z

← Older revision		Revision as of 10:20, 26 January 2026
Line 119:		Line 119:
	Session 1: 0-3487 -> (14887-11400)		Session 1: 0-3487 -> (14887-11400)
	Session 2: 14888-227278		Session 2: 14888-227278

			==Cuesheet Parsing Issues==
			A number of cuesheet elements for Audio CDs are unable to be correctly parsed by the site. To enable discs with these issues to be added, the elements should be removed from the cuesheet section and a note added to comments as follows e.g.:

			Following cuesheet elements unable to be parsed correctly:
			Row 1: CATALOG 0?
			Row 3: SONGWRITER "?"

	==Editions / Datfile versions==		==Editions / Datfile versions==

>Mictlantecuhtle at 10:20, 26 January 2026

2026-01-26T10:20:28Z

← Older revision	Revision as of 10:20, 26 January 2026
(No difference)

>Sadikyo: /* General Audio CD notes */

2025-10-02T13:53:19Z

General Audio CD notes

← Older revision		Revision as of 13:53, 2 October 2025
Line 11:		Line 11:
	Serial field is for serials present on the label of the disc, all other serials should be put in comments.		Serial field is for serials present on the label of the disc, all other serials should be put in comments.

	Track times taken from VGMDB may be incorrect, ~~recommend taking~~ times from ~~foobar2000 or other tools, or leaving times blank entirely~~.		Track times taken from VGMDB may be incorrect, please leave times blank unless taken from the item.

	Ideally, the contents should be listed exactly as on the item, for accuracy. This isn't always done of course. If you've confirmed it was done, please add the following line to the comments verbatim:		Ideally, the contents should be listed exactly as on the item, for accuracy. This isn't always done of course. If you've confirmed it was done, please add the following line to the comments verbatim:

>Sadikyo: /* General Audio CD notes */

2025-10-02T13:53:19Z

General Audio CD notes

← Older revision	Revision as of 13:53, 2 October 2025
(No difference)

>Mictlantecuhtle: /* Universal Hash match across multi-disc sets */

2025-02-05T12:35:48Z

Universal Hash match across multi-disc sets

← Older revision		Revision as of 12:35, 5 February 2025
Line 69:		Line 69:

	# Add the newly matching entry to the database following all of the usual processes and checks, but mark it as yellow (possibly bad dump). This ensures the entry remains visible in the database but without hashes being added to the DAT		# Add the newly matching entry to the database following all of the usual processes and checks, but mark it as yellow (possibly bad dump). This ensures the entry remains visible in the database but without hashes being added to the DAT
	# Add the following text in the comments of the newly matching entry: ''"This disc is a ~~reprint of and~~ Universal Hash match for [existing entry], but has been intentionally added as a separate (yellow) entry to ensure the completeness of this multi-disc set in the database."''		# Add the following text in the comments of the newly matching entry: ''"This disc is a Universal Hash match for [existing entry], but has been intentionally added as a separate (yellow) entry to ensure the completeness of this multi-disc set in the database."''
			## Additional commentary can be added where it is known e.g. that the new entry is a reprint of the older
	# Mark the existing entry as green (verified) and add the following note: ''"This disc is a Universal Hash match for [new entry], which has been intentionally added as a separate (yellow) entry to ensure the completeness of the multi-disc set/both multi-disc sets [delete as appropriate]."''		# Mark the existing entry as green (verified) and add the following note: ''"This disc is a Universal Hash match for [new entry], which has been intentionally added as a separate (yellow) entry to ensure the completeness of the multi-disc set/both multi-disc sets [delete as appropriate]."''

	==== Matching Universal Hash / different cuesheet ====		==== Matching Universal Hash / different cuesheet ====

>Mictlantecuhtle: /* Universal Hash match across multi-disc sets */

2025-02-05T12:35:48Z

Universal Hash match across multi-disc sets

← Older revision	Revision as of 12:35, 5 February 2025
(No difference)

>Mictlantecuhtle: /* Scenarios where matching Universal Hash should not currently be merged */

2025-01-27T14:19:42Z

Scenarios where matching Universal Hash should not currently be merged

← Older revision		Revision as of 14:19, 27 January 2025
Line 71:		Line 71:
	# Add the following text in the comments of the newly matching entry: ''"This disc is a reprint of and Universal Hash match for [existing entry], but has been intentionally added as a separate (yellow) entry to ensure the completeness of this multi-disc set in the database."''		# Add the following text in the comments of the newly matching entry: ''"This disc is a reprint of and Universal Hash match for [existing entry], but has been intentionally added as a separate (yellow) entry to ensure the completeness of this multi-disc set in the database."''
	# Mark the existing entry as green (verified) and add the following note: ''"This disc is a Universal Hash match for [new entry], which has been intentionally added as a separate (yellow) entry to ensure the completeness of the multi-disc set/both multi-disc sets [delete as appropriate]."''		# Mark the existing entry as green (verified) and add the following note: ''"This disc is a Universal Hash match for [new entry], which has been intentionally added as a separate (yellow) entry to ensure the completeness of the multi-disc set/both multi-disc sets [delete as appropriate]."''
			==== Matching Universal Hash / different cuesheet ====

			Occasionally, it is possible to encounter discs which have matching universal hashes but differing track hashes purely due to cuesheet differences (see https://redump.info/disc/105344/ and https://redump.info/disc/112883/ for an example).

			In this case, the entries should be kept separate and an appropriate datfile version applied (generally Alt), along with a note in comments in both entries stating "Universal Hash match with [matching entry] but differing track hashes due to cuesheet differences"

	== Other warnings and issues ==		== Other warnings and issues ==

>Mictlantecuhtle: /* Scenarios where matching Universal Hash should not currently be merged */

2025-01-27T14:19:42Z

Scenarios where matching Universal Hash should not currently be merged

← Older revision	Revision as of 14:19, 27 January 2025
(No difference)

>Mictlantecuhtle: /* Matching Universal Hash / different cuesheet */

2025-01-27T14:19:22Z

Matching Universal Hash / different cuesheet

← Older revision		Revision as of 14:19, 27 January 2025
Line 44:		Line 44:

	In scenario 3 above, note that the previous DIC track hashes should be replaced with the hashes of the redumper dump which correctly identified an offset. If scenario 2 applies, refer to the guidance above regarding Universal Hash and discs with different non-zero data starts.		In scenario 3 above, note that the previous DIC track hashes should be replaced with the hashes of the redumper dump which correctly identified an offset. If scenario 2 applies, refer to the guidance above regarding Universal Hash and discs with different non-zero data starts.

	~~=== Matching Universal Hash / different cuesheet ===~~

	Occasionally, it is possible to encounter discs which have matching universal hashes but differing track hashes purely due to cuesheet differences (see https://redump.info/disc/105344/ and https://redump.info/disc/112883/ for an example).

	In this case, the entries should be kept separate and an appropriate datfile version applied (generally Alt), along with a note in comments in both entries stating "Universal Hash match with [matching entry] but differing track hashes due to cuesheet differences"

	== Merging entries which have the same Universal Hash ==		== Merging entries which have the same Universal Hash ==