[pulseaudio-discuss] [RFC] Passthrough support
bossart.nospam at gmail.com
Tue Feb 22 12:26:04 PST 2011
>> One last comment on proplists. If we don't define a set of mandatory
>> elements, then it's going to be really hard to use this
>> pa_stream_new_extended() routine. How will the client figure out what
>> exactly it needs to send for each format?
> I was thinking that his would basically develop as convention, though
> the few basic properties (rate, channels) could be documented along with
> the pa_encoding_t structure. We can document additional properties (for
> example bitrate, if some sink ever needs it) as being optional but
> recommended if available.
To make things clearer I would add the sampling rate as a mandatory
property in the RFC. the number of channels may be unknown before you
actually decode, and for an IEC format the number of channels seen by
PA is 2...
More information about the pulseaudio-discuss