208
edits
Difference between revisions of "OpenTasks/Audio/Audio Output Selection"
OpenTasks/Audio/Audio Output Selection (view source)
Revision as of 17:53, 4 March 2011
, 17:53, 4 March 2011Move OpenTasks onto unique pages with an Infobox and Category so we can collect them all up onto a summary page.
(Move OpenTasks onto unique pages with an Infobox and Category so we can collect them all up onto a summary page.) |
m (Move OpenTasks onto unique pages with an Infobox and Category so we can collect them all up onto a summary page.) |
||
| Line 1: | Line 1: | ||
{{Infobox_OpenTasks| | {{Infobox_OpenTasks| | ||
gsocworkload= | gsocworkload=50%| | ||
techcontact=[[User:LordHoto|Johannes Schickel]], [[User:Fingolfin|Max Horn]]| | techcontact=[[User:LordHoto|Johannes Schickel]], [[User:Fingolfin|Max Horn]]| | ||
subsystem=Audio| | subsystem=Audio| | ||
| Line 29: | Line 29: | ||
So if you plan to take this task, you will still have a lot of research to do, to find the best separation :-). Of course the technical contacts, as well as the rest of the ScummVM team, would collaborate with you on this. | So if you plan to take this task, you will still have a lot of research to do, to find the best separation :-). Of course the technical contacts, as well as the rest of the ScummVM team, would collaborate with you on this. | ||
Roughly the same layers should also be visible in the GUI configuration to allow for a much more user friendly output configuration. The user might additionally configure a concrete output driver like ALSA to use a specific setting (like in the output port for ALSA); think of this as a baby version of output devices (for true output devices, one would have to support multiple such configurations for each driver, configurable and selectable via the command line, GUI and the internal API). See the [[OpenTasks | Roughly the same layers should also be visible in the GUI configuration to allow for a much more user friendly output configuration. The user might additionally configure a concrete output driver like ALSA to use a specific setting (like in the output port for ALSA); think of this as a baby version of output devices (for true output devices, one would have to support multiple such configurations for each driver, configurable and selectable via the command line, GUI and the internal API). See the [[OpenTasks/Audio/MIDI_Device_Configuration|MIDI device configuration]] task for more thoughts about this. (Note that it would probably be best to tackle both tasks in a single Google Summer of Code project!) | ||
Of course this is not set in stone yet; if you have some other great idea how to tackle this, we are happy for your feedback :-). | Of course this is not set in stone yet; if you have some other great idea how to tackle this, we are happy for your feedback :-). | ||