mirror of
https://github.com/SabreTools/MPF.git
synced 2026-02-04 05:35:52 +00:00
[Request] Redumper / Audio CD - additional comment fields required #497
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mictlantecuhtle on GitHub (Feb 24, 2023).
Originally assigned to: @mnadareski on GitHub.
redumper supports a number of additional features with regards to Audio CDs. These require some additional processing of redumper logs and generation of comment fields to be added to redump entries for such items.
Universal Hash
Will be found in redumper logs under section **MODE: Split and look as follows:
Universal Hash (SHA-1): 33142665aa901c08210785c6802885768b4660d1Should be added to !submissionInfo.txt output under Comments as follows:
<b>Universal Hash (SHA-1)</b>: 33142665aa901c08210785c6802885768b4660d1Non-zero data start
Found in redumper logs under section **MODE: Split and will need to be extracted from the following:
non-zero data sample range: [ -11 .. +93464352]Should be added to !submissionInfo.txt output under Comments as follows:
<b>Ring non-zero data start</b>: -11Disc Write Offset
Found in redumper logs under section **MODE: Split and will appear one of two ways:
detecting offsetaudio silence detection... donePerfect Audio Offset (silence level: 0): -12Perfect Audio Offset applieddisc write offset: -12Or
detecting offsetaudio silence detection... donePerfect Audio Offset (silence level: 1): [-5384 .. +6991]warning: fallback offset 0 applieddisc write offset: +0Should be added to !submissionInfo.txt output as a Write offset as normal e.g.:
Write offset: -12Lead-in / lead-out - Track 0 / Track A/AA.bin
Where discs have non-zero data in the lead-in or lead-out this will result in the generation of additional Track 0 or Track A/AA.bin files. The information for these can be found in redumper logs under the "dat" heading and will appear as e.g.
<rom name="GoW III (Track 00).bin" size="2352" crc="46f91175" md5="f43c1e89009ffb2f4f0fd04f5c3a3e34" sha1="1cee51d5e1c12873cce9aca7736792bc87812113" />for lead-inor
<rom name="GoW III (Track A).bin" size="2352" crc="46f91175" md5="f43c1e89009ffb2f4f0fd04f5c3a3e34" sha1="1cee51d5e1c12873cce9aca7736792bc87812113" />They should be processed and output to !submissionInfo.txt comments as follows:
<xmp><rom name="leadin.bin" size="2352" crc="46f91175" md5="f43c1e89009ffb2f4f0fd04f5c3a3e34" sha1="1cee51d5e1c12873cce9aca7736792bc87812113" /></xmp>or
<xmp><rom name="leadout.bin" size="2352" crc="46f91175" md5="f43c1e89009ffb2f4f0fd04f5c3a3e34" sha1="1cee51d5e1c12873cce9aca7736792bc87812113" /></xmp>Example redump entries:
@mnadareski commented on GitHub (Feb 24, 2023):
Universal Hash:
0e0ff0cb80Non-zero data start:
1cbe81fba6Disc Write Offset:
420e356f34Lead-in / lead-out: Pending
@mnadareski commented on GitHub (Feb 26, 2023):
The lead-in/lead-out seems to be rare enough that this should not be necessary right now. If this becomes more pressing in the future, please open a new issue for just that.