[pulseaudio-discuss] RFC: Routing and Priority lists
Tanu Kaskinen
tanu.kaskinen at digia.com
Wed Nov 23 12:42:19 PST 2011
On Tue, 2011-11-22 at 23:14 +0200, Janos Kovacs wrote:
> Hi,
>
> so far we were talking of the simpler routing scenarios. So let's shift to
> the next gear and discuss the more challenging setup's.
>
> In some cases we might have multiple zones, e.g a desktop PC
> were in one room and a stereo amplifier would be in another
> connected via S/PDIF. Say you want to do the usual stuff and
> see youtube videos in one room, while playing out music to the
> other room.
>
> Let's forget for a moment about that there is no profile with dual sink
> and focus on the possible routing issues.
>
> How would our media role based routing work? Both streams
> media role would be 'music' so it could not be used to select the
> sink.
>
> One option would be to add a property to the streams what would
> tell the 'zone'. The lack of property would default to a certain zone.
> That would be a natural thing from the application perspective but
> would break the currently proposed routing infrastructure.
Does the proposed system limit the input for decisions to only one
property? If so, then I'd say the proposal needs fixing.
> The other option would be to follow the bad example of profiles
> and have media roles like 'music' , 'music-in-zone2' etc. This
> thing would work with the proposed routing infrastructure but ...
...but violates the rule that only roles from the predefined set may be
used, if interoperability is desired.
--
Tanu
More information about the pulseaudio-discuss
mailing list