Redumper/Aaru/DiscImageCreator UI in C#
This is a community project, so if you have some time and knowledge to give, we'll be glad to add you as a contributor to this project. If you have any suggestions, issues, bugs, or crashes, please look at the Issues page first to see if it has been reported before and try out the latest AppVeyor WIP build below to see if it has already been addressed. If it hasn't, please open an issue that's as descriptive as you can be. Help me make this a better program for everyone :)
For the most recent stable build, download the latest release here: Releases Page
For the latest WIP build here: Rolling Release
MPF is the main, UI-centric application of the MPF suite. This program allows users to use Redumper, Aaru, or DiscImageCreator in a more user-friendly way. Each backend dumping program is supported as fully as possible to ensure that all information is captured on output. There are many customization options and quality of life settings that can be access through the Options menu.
The main UI has some known limitations that are documented in code and in some prior support tickets:
MPF.CLI is a commandline-only program that allows users to use Redumper, Aaru, or DiscImageCreator in a more user-friendly way. Each backend dumping program is supported as fully as possible to ensure that all information is captured on output. There are many customization options and quality of life settings that can be access through the config.json
file.
The main CLI has some known limitations that are documented in code and in some prior support tickets:
MPF.Check is a commandline-only program that allows users to generate submission information from their personal rips. This program supports the outputs from Redumper, Aaru, DiscImageCreator, Cleanrip, and UmdImageCreator. Running this program without any parameters will display the help text, including all supported parameters.
MPF.UI, MPF.CLI, and MPF.Check have the same system requirements for running, with the exception that MPF.UI is Windows-only.
Ensure that your operating system and runtimes are as up-to-date as possible, since some features may rely on those updates.
To build for .NET 9.0, ensure that the .NET 9.0 SDK (or later) is installed and included in your PATH
. Then, run the following commands from command prompt, Powershell, Terminal, or shell:
MPF.UI (Windows only):
dotnet build MPF/MPF.csproj --framework net9.0-windows --runtime [win-x86|win-x64]
MPF.CLI (Windows, OSX, Linux):
dotnet build MPF.CLI/MPF.CLI.csproj --framework net9.0 --runtime [win-x86|win-x64|win-arm64|linux-x64|linux-arm64|osx-x64|osx-arm64]
MPF.Check (Windows, OSX, Linux):
dotnet build MPF.Check/MPF.Check.csproj --framework net9.0 --runtime [win-x86|win-x64|win-arm64|linux-x64|linux-arm64|osx-x64|osx-arm64]
Choose one of win-x86
, win-x64
, win-arm64
, linux-x64
, linux-arm64
, osx-x64
, or osx-arm64
depending on the machine you are targeting.
Windows users may run publish-win.ps1
and Linux users may run publish-nix.sh
to perform a full release build. Both scripts will build and package all variants of MPF.UI, MPF.CLI, and MPF.Check with commandline switches to control what is included.
publish-win.ps1
requires 7-zip commandline and Git for Windows to be installed and in PATH
publish-nix.sh
requires zip
and git
to be installed and in PATH
For all additional information, including information about the individual components included in the project and what dumping programs are supported, please see the wiki for more details.
A list of all changes in each stable release and current WIP builds can now be found here.
MPF uses some external libraries to assist with additional information gathering after the dumping process.
Here are the talented people who have contributed to the project so far in ways that GitHub doesn't like to track:
For all others who have contributed in some way, please see here.
These are the tireless individuals who have dedicated countless hours to help test the many features of MPF and have worked with the development team closely:
Thanks to these communities for their use, testing, and feedback. I can't even hope to be able to thank everyone individually.