[Problem] Please Omit tracks/hashes for Session 2 Lead-in in Multisession Discs - Track 00.2 / 0.2 #609

Open
opened 2026-01-29 16:19:22 +00:00 by claunia · 0 comments
Owner

Originally created by @sadikyo on GitHub (Sep 27, 2023).

Originally assigned to: @mnadareski on GitHub.

  • Stable release (2.6.5)
  • .NET Framework 4.8 running on (Windows 10)

Describe the issue
Currently, for multisession discs, some versions of redumper will pull a Track 00.2 or Track 0.2 into the dat/tracks - and this is currently being populated by MPF in the list of hashes. If Track 0.2 / 00.2 is generated, it should be omitted as we don't / can't store this info in redump, and the hashes for this lead-in aren't consistent anyway with current methods.

Additional context
If you need specific example or even logs / submissioninfo.txt from one I've dumped, please let me know and I will provide those.

Originally created by @sadikyo on GitHub (Sep 27, 2023). Originally assigned to: @mnadareski on GitHub. - [X] Stable release (2.6.5) - [X] .NET Framework 4.8 running on (Windows 10) **Describe the issue** Currently, for multisession discs, some versions of redumper will pull a Track 00.2 or Track 0.2 into the dat/tracks - and this is currently being populated by MPF in the list of hashes. If Track 0.2 / 00.2 is generated, it should be omitted as we don't / can't store this info in redump, and the hashes for this lead-in aren't consistent anyway with current methods. **Additional context** If you need specific example or even logs / submissioninfo.txt from one I've dumped, please let me know and I will provide those.
claunia added the bug label 2026-01-29 16:19:22 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#609