[RFC] Passthrough support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



'Twas brillig, and Arun Raghavan at 18/02/11 09:41 did gyre and gimble:
> Hello!
> 
> On Tue, 2011-02-15 at 22:02 +0530, Arun Raghavan wrote:
>> Hey folks,
>> I've put up a draft proposed API changes to get passthrough support to
>> the point where things Just Work? for at least the common cases, based
>> on previous discussion on-/off-list:
>>
>> http://pulseaudio.org/wiki/PassthroughSupport
>>
>> Please review/comment. Once we have some consensus, I'll send in patches
>> to actually get this done.
> 
> I've updated this page with the changes discussed so far (and translated
> them into the actual API changes that we need). Please take a look and
> let me know if this looks acceptable.

I've maybe missed the discussion, but is it worth having both:
 pa_stream_new_extended
and
 pa_stream_new_with_proplist_extended

Doesn't the former just call the latter with a NULL proplist anyway?

While I appreciate the symmetry with the existing API, I'd say avoid the
cruft and just call it pa_stream_new_extended() which implies both the
format and the proplist. WDYT?

Col



-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]




[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux