[Portaudio] Portaudio PulseAudio HostAPI
evan at imitone.com
Thu Dec 15 02:34:11 EST 2016
Hey, Tuukka ---
The other month, we started a little initiative for Hotplug support in
portaudio. This new featureset has a little bit of overlap with
hostApi-wise setup and teardown, and we discussed another API extension
providing those features specifically. (Click here, scroll to bottom
<https://app.assembla.com/spaces/portaudio/wiki/HotPlug>.) There's also a
branch on the current repository dealing with device list patching, though
I don't know if it's up-to-date. Either way, these APIs are probably a
better long-term solution than a global flag.
– Evan Balster
creator of imitone <http://imitone.com>
On Thu, Dec 15, 2016 at 12:53 AM, Tuukka Pasanen <pasanen.tuukka at gmail.com>
> Actually I haven't done much because I see that code is ready-to-merge if
> otherwise is said (corrected things that has risen on review). One thing
> that I have been thinking should Pulseaudio be turned on first with run
> time variable like PORTAUDIO_PULSEAUDIO=1 because there seems to be common
> fear that new untested Pulseaudio messes things up because ALSA is mature
> and working most cases.
> But if there is something that I have missed which prevents merge or
> Pulseaudio is unneeded feature that can be said now because it has been in
> works more than 3 years (and ready to merge more than half year).
> 14.12.2016, 12:26, Roland Winklmeier kirjoitti:
> 2016-08-26 12:52 GMT+02:00 Ross Bencina <rossb-lists at audiomulch.com>:
>> Hi Tuukka,
>> Yes this is very good news. I've taken a quick look at your merge request
>> and written some comments. I'm not sure that all of my comments are useful.
>> Please feel free to disagree with any of them.
>> One additional request, if you haven't done this already:could you please
>> run the examples/tests with some kind of memory checker such as valgrind or
>> llvm AddressSanitizer/LeakSanitizer. Just to check that your first-order
>> memory handling is OK.
>> Portaudio mailing list
>> Portaudio at lists.columbia.edu
> what is the current status of PulseAudio API? I remember I was testing it
> successfully and it was discussed to wait until a stable PA release has
> been made before it can potentially be merged. With the PA release being
> available, what is the status of this one?
> Cheers Roland
> Portaudio mailing listPortaudio at lists.columbia.eduhttps://lists.columbia.edu/mailman/listinfo/portaudio
> Portaudio mailing list
> Portaudio at lists.columbia.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Portaudio