Changes between Initial Version and Version 1 of Ticket #8476, comment 12


Ignore:
Timestamp:
Jun 3, 2012, 1:13:59 PM (12 years ago)
Author:
ttcoder

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #8476, comment 12

    initial v1  
    22
    33- a) we clearly want to keep the driver talking to media_server as normal, and access multi-audio through the media_server only.
    4 - b) turns out the userland code to access multiple streams probably won't be hard: the e.g. tunetracker code (released under a MIT/BSD license for other apps to use) which implements targetting a specific audio card (other than the "main" one) might be used for accessing a specific audio jack (other than the "line out" one). (<''The multiaudio addon will expose an input for each stream exposed by the driver. The user can select this input in the Media preflet for the mixer output.''>)
     4- b) turns out the userland code to access multiple streams probably won't be hard: the e.g. tunetracker "File Audition" code (released under a MIT/BSD license for other apps to use) which implements targetting a specific audio card (other than the "main" one) might be used for accessing a specific audio jack (other than the "line out" one). (<''The multiaudio addon will expose an input for each stream exposed by the driver. The user can select this input in the Media preflet for the mixer output.''>)
    55- c) the key to solving this ticket, thus, is to implement code driver-side; so that the HDA driver 1) allows for more than just one output stereo stream, 2) can route that output playback stream to an output "widget" in HDA parlance and then 3) route that output widget to an output connector (a jack other than the main output jack).
    66