mirror of
https://github.com/SabreTools/MPF.git
synced 2026-02-03 21:29:27 +00:00
[Request] - Separate profiles for Dreamcast Low Density and High Density dumps (or combine together). #451
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 @ehw on GitHub (Sep 12, 2022).
Originally assigned to: @Deterous on GitHub.
Is your feature request related to a problem? Please describe.
Dreamcast GD-ROMs and GD-Rs contain two separate regions that must be dumped - a low density (LD) and a high density (HD) region. DiscImageCreator can currently dump both regions with in two separate modes. The low density tracks are dumped like a traditional CD-ROM/CD-R, while the high density are dumped with the "GD" mode. Currently, MPF has a "Sega Dreamcast" profile that can dump only the high density tracks with the "GD" mode in DiscImageCreator. However, there is no formal profile for the low density.
Another issue is the fact that currently there has to be two profiles for each density. More likely than not, users will most likely need two separate drives to dump Dreamcast discs - A Plextor for the low density, and a TSST (or other non-DIC supported drive) for the high density. It would be convenient if there was a profile in MPF that could handle both, but this would be very difficult to implement for a few reasons.
Describe the solution you'd like
The simplest solution that can be implemented right now is to create two profiles for the Dreamcast - one explicitly marked for low density and another for high density. Both that run the appropriate commands to make it work.
Describe alternatives you've considered
To make one singular profile for Dreamcast, a lot more work has to be put in that will definitely break in the future. This would also be very involved for the user as there are a lot of ways the procedure can go.
I would hold off on implementing any of this straight away as its possible that sarami might want to change certain things with DIC in the near future. But I'm filling out a feature request just for record keeping.