Difference between revisions of "Music drivers redesign"

Jump to navigation Jump to search
m
cleanup
m (cleanup)
Line 16: Line 16:
**GS (MTD_GS)
**GS (MTD_GS)
**...?
**...?
*Digitalised/CD-Audio (MTD_DIGI?)
*Digitized/CD-Audio (MTD_DIGI?)
*...?
*...?


Line 53: Line 53:
*General configuration:
*General configuration:
**The user can configure the default options of the drivers/devices (This ALSA device is an MT-32 and use this volume, the FluidSynth driver should use this soundfont file, ...)
**The user can configure the default options of the drivers/devices (This ALSA device is an MT-32 and use this volume, the FluidSynth driver should use this soundfont file, ...)
**The user can priorize the music types globaly (i.e. I prefer GM, then AdLib, then PC Speaker, and nothing else) and the default driver/device for each type
**The user can prioritize the music types globally (i.e. I prefer GM, then AdLib, then PC Speaker, and nothing else) and the default driver/device for each type
*For each game:
*For each game:
**The MetaEngine offers an API for querying which music types are supported by a given target, in order of preference and the user can choose one of those (default will use the previously configured priorities)
**The MetaEngine offers an API for querying which music types are supported by a given target, in order of preference and the user can choose one of those (default will use the previously configured priorities)
Line 67: Line 67:
** sword2
** sword2


*Engines using MIDI and without any special adlib support (so they use the AdLib driver at most as a cheap MIDI "emulator"):
*Engines using MIDI and without any special AdLib support (so they use the AdLib driver at most as a cheap MIDI "emulator"):
** agi
** agi
** agos
** agos
2,051

edits

Navigation menu