Audio IO Presets
Using multiple different audio routing configurations in current mixxx requires selecting all audio settings from scratch every time the configurations are changed. This blueprint proposes implementation of UI and backend changes to show and store multiple named "sets" of audio connection configuration, allowing to switch between modes quickly.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Work Items
Work items:
Define a way to store audio settings multiple times to database, referenced by name: TODO
Detect connected audio devices reliably and recognise which mappings can be applied and which should be disabled because devices are not connected: TODO
Give priority to the mappings, sorting the selection in the preference user chooses: TODO
During mixxx startup, choose the highest priority audio IO preset available (for which all devices are connected): TODO
Changes to the Sound Hardware dialog to allow listing, editing, renaming, ordering, deleting and storing audio IO preset profiles: TODO
instead of only active current settings as we do now (requires the backend changes described above): TODO
Mark as unselectable and disable editing and activation of presets for which the hardware is not available, allowing still reordering and deleting of such presets at any time. (requires audio device connection status detection described above): TODO
Provide a list of audio io presets to choose from in menu or available to skins, ordered by preset preference: TODO
