1,079
edits
Difference between revisions of "OpenTasks"
Jump to navigation
Jump to search
→MIDI device configuration
m (→Add 16bit graphics support to SCUMM engine: link to freddicove demo) |
|||
| Line 187: | Line 187: | ||
=== MIDI device configuration === | === MIDI device configuration === | ||
Right now, the MIDI drivers are treated by ScummVM in a rather single minded fashion: Either a driver is linked in and hence "available", or not. It's not possible to configure anything about them (like ports to be used etc.), nor does it ever take into account that a single driver might correspond to multiple devices (after all, you can plug several sequenecers into your MIDI port; or you could have configured several different sound font settings in your MIDI emulator). | ''Technical Contact'': [[User:Fingolfin|Max Horn]] | ||
* | |||
* | '''Background:''' | ||
Right now, the MIDI drivers are treated by ScummVM in a rather single minded fashion: Either a driver is linked in and hence "available", or not. It's not possible to configure anything about them (like ports to be used etc.), nor does it ever take into account that a single driver might correspond to multiple devices (after all, you can plug several sequenecers into your MIDI port; or you could have configured several different sound font settings in your MIDI emulator). | |||
'''The Task:''' | |||
* Add an API for querying the OSystem backend for a list of available MIDI devices (not drivers) | |||
* Information about the selected device must be serializable, so that it can be stored in the config file | |||
* Selection of devices via command line should be possible | |||
* It must deal with devices being added/removed (at least between runs of ScummVM, ideally also while ScummVM is running) | |||
* Devices should be configurable via the GUI; this needs to be done in a flexible (different devices/drivers offer different settings) and portable fashion. | |||
=== XMIDI parser === | === XMIDI parser === | ||