On Tue, 2011-02-22 at 13:27 -0600, pl bossart wrote: > >> Still, I am not clear about the negociation. the client would need to > >> use pa_stream_new_extended with multiple formats, and then get the > >> actual format with get_format_info. If my understanding is correct, > >> then maybe you would need a list of formats instead of just one? > > > > Oh, indeed! That was the intention, but I guess I missed putting that in > > the wiki. Fixed now. > > ok. Looks good. > 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. -- Arun
