On Wednesday February 04 2015 09:40:27 Paul Davis wrote: > I probably shouldn't guess this, but I'd imagine that the overwhelming > majority of all Linux-y applications that have ever interacted with > PulseAudio have done so using the ALSA API, not the PA API.
> All those > Phonon-using apps on KDE? They are not using the PA API, but GStreamer > which in turn uses the ALSA API, and just gets redirected through > PulseAudio (or JACK or ....). Or they are using ALSA directly. Or they are using the VLC backend ... whatever VLC uses afterwards. > Getting PulseAudio working on OS X won't address or help in the use of > those applications. Either I missed or misunderstood something, or you forgot to take something into account: ALSA doesn't exist on OS X. So all those applications that rely on the ALSA API should be helped by something on OS X that puts the ALSA API in front of CoreAudio. > Do you have a specific list of apps that you know actually use the > PulseAudio API, rather than (as (used to be) recommended) the ALSA API via > some layer of "middleware" or directly? No, I don't. I hope I didn't give the impression, but it was never my intention to claim that I was looking to cater to applications that do use the PA API. Really, for all I knew PA was an alternative to ALSA on Linux, one that also happens to support OS X to some extent, while ALSA clearly does not. (At least it couldn't without a name change :)). > That doesn't have much to do with PulseAudio :) No, but it does have something to do with providing an API and runtime interface on OS X like what's available on Linux. Phonon with an appropriate backend would also do the trick, but only for Qt-based applications AFAIK. R. _______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
