mirror of
https://github.com/SabreTools/MPF.git
synced 2026-02-04 05:35:52 +00:00
[Problem] MPF does not default to .aaruf extension when using Aaru #596
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 @CookiePLMonster on GitHub (Aug 23, 2023).
Originally assigned to: @mnadareski on GitHub.
Version
What version are you using?
Build
What runtime version are you using?
Describe the issue
Aaru requires that the output file extension is
.aarufand not.bin.Supplying a path with a wrong extension will make Aaru refuse to dump the disc. I vaguely recall that MPF used to supply a correct extension when selecting Aaru, but this is not the case anymore.To Reproduce
Steps to reproduce the behavior:
.binfile..aaruffile and start dumping again.Expected behavior
MPF defaults to a correct
.aarufextension when using Aaru as the dumping program.@mnadareski commented on GitHub (Aug 27, 2023):
Please expand on point 2. Do you mean "change to Aaru using the drop-box in the main UI" or "change to Aaru using the Options menu"? This is a critical difference.
@mnadareski commented on GitHub (Aug 27, 2023):
If it is the former, try
d92a1d566dto see if it fixes your issues.@CookiePLMonster commented on GitHub (Aug 28, 2023):
Yes, it is the former, apologies for not clarifying.
However, on the latest WIP build (
d92a1d566d) the issue still persists. Changing to Aaru using the dropdown in the main UI does not change the extension from.binto.aaruf. Ideally, the extension (and only the extension) should change regardless of whether the output path has been left at default, or modified by the user beforehand.@mnadareski commented on GitHub (Aug 28, 2023):
Try out
0912b78568to see if it fixes your issues.@CookiePLMonster commented on GitHub (Aug 28, 2023):
Almost - the order of operations is wrong, because now changing the dumping program influences not the current extension, but the future one - as if it first checked the dumping program, then the dropdown option change took effect.
Try it with the following:
.bin..bin..aaruf.@mnadareski commented on GitHub (Aug 28, 2023):
You mean "past" not "future". Try out
98a30e6558@CookiePLMonster commented on GitHub (Aug 28, 2023):
I meant "future" as in "the current selected UI option is going to influence the next (future) output path", which indeed is equivalent to "the past UI option influenced the current output path".
Regardless, it works fine now. Thanks!