Special Processing Issues - Revision history

Mictlantecuhtle at 16:05, 5 July 2023

2023-07-05T16:05:19Z

← Older revision		Revision as of 16:05, 5 July 2023
Line 3:		Line 3:
	'''redumper - scrambled leadout marked as audio'''		'''redumper - scrambled leadout marked as audio'''

-	For some discs, lead-out following the data track is marked as audio but actually consists of fully scrambled (empty) data sectors. This results in the generation of a Track A consisting of empty data sectors.	+	:For some discs, lead-out following the data track is marked as audio but actually consists of fully scrambled (empty) data sectors. This results in the generation of a Track A consisting of empty data sectors.

-	If a data disc is dumped and submitted with a Track A, moderators should carefully check the non-zero TOC sample range and non-zero data sample range. If the data range is within the TOC range (i.e. is smaller, see below), then this situation may obtain and further advice should be sought	+	:If a data disc is dumped and submitted with a Track A, moderators should carefully check the non-zero TOC sample range and non-zero data sample range. If the data range is within the TOC range (i.e. is smaller, see below), then this situation may obtain and further advice should be sought

-	Example:	+	:Example:

-	<code>non-zero TOC sample range: [ -88200 .. +169617420]	+	:<code>non-zero TOC sample range: [ -88200 .. +169617420]

-	non-zero data sample range: [ +9410 .. +169441022]</code>	+	:non-zero data sample range: [ +9410 .. +169441022]</code>

	'''New Audio Disc Submissions (2023 02-24)'''		'''New Audio Disc Submissions (2023 02-24)'''

Mictlantecuhtle at 16:04, 5 July 2023

2023-07-05T16:04:42Z

← Older revision		Revision as of 16:04, 5 July 2023
Line 1:		Line 1:
	The purpose of this page is to track some unique items / issues, that the mods should be aware of and looking out for when processing submissions.		The purpose of this page is to track some unique items / issues, that the mods should be aware of and looking out for when processing submissions.
		+
		+	'''redumper - scrambled leadout marked as audio'''
		+
		+	For some discs, lead-out following the data track is marked as audio but actually consists of fully scrambled (empty) data sectors. This results in the generation of a Track A consisting of empty data sectors.
		+
		+	If a data disc is dumped and submitted with a Track A, moderators should carefully check the non-zero TOC sample range and non-zero data sample range. If the data range is within the TOC range (i.e. is smaller, see below), then this situation may obtain and further advice should be sought
		+
		+	Example:
		+
		+	<code>non-zero TOC sample range: [ -88200 .. +169617420]
		+
		+	non-zero data sample range: [ +9410 .. +169441022]</code>

	'''New Audio Disc Submissions (2023 02-24)'''		'''New Audio Disc Submissions (2023 02-24)'''

Sadikyo at 14:14, 24 February 2023

2023-02-24T14:14:29Z

← Older revision		Revision as of 14:14, 24 February 2023
Line 1:		Line 1:
	The purpose of this page is to track some unique items / issues, that the mods should be aware of and looking out for when processing submissions.		The purpose of this page is to track some unique items / issues, that the mods should be aware of and looking out for when processing submissions.
		+
		+	'''New Audio Disc Submissions (2023 02-24)'''
		+	:Please review the detail in the [http://wiki.redump.org/index.php?title=Audio_CD_Moderation_Guide Audio CD Moderation Guide] regarding new disc submissions, and cases where Universal Hash is the same for an existing entry, but the tracks differ. In those cases, we add as a verification via the steps outlined in the guide linked here.

	'''Error count (2023 01-13)'''		'''Error count (2023 01-13)'''

Sadikyo at 12:30, 14 January 2023

2023-01-14T12:30:28Z

← Older revision		Revision as of 12:30, 14 January 2023
Line 5:		Line 5:
	:If you are processing a verification, for example, and the error count differs from that in the current redump entry, '''please do not update it without researching further!''' It is possible that edccchk.exe needs to be run on the disc to verify errors, or further investigation is needed.		:If you are processing a verification, for example, and the error count differs from that in the current redump entry, '''please do not update it without researching further!''' It is possible that edccchk.exe needs to be run on the disc to verify errors, or further investigation is needed.

-	'''EXE Date / UTC vs. "local time" issue'''	+	'''EXE Date / UTC vs. "local time" issue (2023 01-13)'''
	:As we have discussed many times before, there are discrepancies in some redump entries (usually by a day or so), due to the difference between localtime and 'UTC' time. MPF is now adjusting the EXE Date to UTC, and so some verifications will show an EXE date that differs (usually early by a day). As a team, we need to figure out if we are going full fledged forward this direction, or not. As it stands, we have a mixture in the database and different mods are doing different things. One proposal is to not adjust them as we are adding verifications, until we figure this out.		:As we have discussed many times before, there are discrepancies in some redump entries (usually by a day or so), due to the difference between localtime and 'UTC' time. MPF is now adjusting the EXE Date to UTC, and so some verifications will show an EXE date that differs (usually early by a day). As a team, we need to figure out if we are going full fledged forward this direction, or not. As it stands, we have a mixture in the database and different mods are doing different things. One proposal is to not adjust them as we are adding verifications, until we figure this out.

Sadikyo at 12:30, 14 January 2023

2023-01-14T12:30:03Z

← Older revision		Revision as of 12:30, 14 January 2023
Line 4:		Line 4:
	:There are some issues / discrepancies with error counts. The existing tools / process, can sometimes report error counts that differ from previous redump entries as well as reliable external tools like edccchk.exe.		:There are some issues / discrepancies with error counts. The existing tools / process, can sometimes report error counts that differ from previous redump entries as well as reliable external tools like edccchk.exe.
	:If you are processing a verification, for example, and the error count differs from that in the current redump entry, '''please do not update it without researching further!''' It is possible that edccchk.exe needs to be run on the disc to verify errors, or further investigation is needed.		:If you are processing a verification, for example, and the error count differs from that in the current redump entry, '''please do not update it without researching further!''' It is possible that edccchk.exe needs to be run on the disc to verify errors, or further investigation is needed.
		+
		+	'''EXE Date / UTC vs. "local time" issue'''
		+	:As we have discussed many times before, there are discrepancies in some redump entries (usually by a day or so), due to the difference between localtime and 'UTC' time. MPF is now adjusting the EXE Date to UTC, and so some verifications will show an EXE date that differs (usually early by a day). As a team, we need to figure out if we are going full fledged forward this direction, or not. As it stands, we have a mixture in the database and different mods are doing different things. One proposal is to not adjust them as we are adding verifications, until we figure this out.

Sadikyo: Created page with "The purpose of this page is to track some unique items / issues, that the mods should be aware of and looking out for when processing submissions. '''Error count (2023 01-13)'''..."

2023-01-14T12:24:19Z

Created page with "The purpose of this page is to track some unique items / issues, that the mods should be aware of and looking out for when processing submissions. '''Error count (2023 01-13)'''..."

New page

The purpose of this page is to track some unique items / issues, that the mods should be aware of and looking out for when processing submissions.

'''Error count (2023 01-13)'''
:There are some issues / discrepancies with error counts. The existing tools / process, can sometimes report error counts that differ from previous redump entries as well as reliable external tools like edccchk.exe.
:If you are processing a verification, for example, and the error count differs from that in the current redump entry, '''please do not update it without researching further!''' It is possible that edccchk.exe needs to be run on the disc to verify errors, or further investigation is needed.