Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for bitwise ROM dumps to the UI application #56

Closed
sergm opened this issue Apr 10, 2021 · 0 comments
Closed

Add support for bitwise ROM dumps to the UI application #56

sergm opened this issue Apr 10, 2021 · 0 comments

Comments

@sergm
Copy link
Member

sergm commented Apr 10, 2021

Since (#44), mt32emu supports bitwise ROM dumps (a.k.a. partial ROM images), those can now be identified, loaded and merged for use by the synth engine.

However, the ROM selection dialog does not provide a possibility to select more than 1 ROM file of each type (control / PCM), so that only the full ROM images are effectively supported.

Additionally, only two configured ROM filenames are used internally and stored in the application settings. Instead, the max of 4 filenames must be supported.

@sergm sergm added this to the mt32emu_qt_1_9 milestone Apr 10, 2021
@sergm sergm self-assigned this Apr 10, 2021
sergm added a commit that referenced this issue Apr 25, 2021
- QSynth now cares about a pair of ROM files of each type, and the second
  filename is now stored in settings.
- Reworked ROMSelectionDialog to permit selection of multiple ROM files
  of each type and to support known machine configurations to simplify
  selection of ROMs when many are present in a single directory.
- Some improvements in Master and QSynth initialisation stuff.
@sergm sergm added the Feature label May 2, 2021
@sergm sergm closed this as completed May 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant