mirror of
https://github.com/SabreTools/MPF.git
synced 2026-02-03 21:29:27 +00:00
[Problem] v3.3.0 misinterpreting RedumperLeadinRetryCount setting as drive speed #792
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 @periodic1236 on GitHub (Jan 13, 2025).
Originally assigned to: @mnadareski on GitHub.
Version
Build
What runtime version are you using?
Describe the issue
If I enable "Set Default Plextor Lead-in Retries" under Tools > Options > Programs > Redumper, the retry count value (which defaults to 4) is passed to redumper in the speed parameter, regardless of what is chosen for the Drive Speed. If I put a custom retry count, the same number shows up in the Parameters box but is attached to the
--speedflag, not the--plextor-leadin-retriesargument (which is missing). Indeed, if I start the dump, redumper is invoked with--speed=4or similar.To Reproduce
Steps to reproduce the behavior:
Audio CD, observe default "Drive Speed" for CD-ROM is set to 24 and--speed=24appears in the "Parameters" box.--speed=8in the "Parameters" box.--speed=4.--speed=4.--speed=123now.Expected behavior
For redumper, the
--speedflag should be correctly set to the chosen drive speed, and the Plextor lead-in retry count value should be passed to the--plextor-leadin-retriesflag.