On 24.04.2017 20:04, Tanu Kaskinen wrote:
> "Let PA sit ontop of that", with "that" referring to a bunch of
> headers, doesn't make sense to me. I understand your proposal so that
> the existing PA library would be one backend for the new API. So the
> new API is a layer above the existing PA
On 17.04.2017 19:40, Tanu Kaskinen wrote:
> As you're planning to create yet another cross-platform audio
> abstraction API,
No, no, I dont wanna create yet another one. I'm just trying to find
out, whether the exist PA API could become one (as it's AFAIK already
crossplatform), even for cases
On 15.04.2017 20:39, Tanu Kaskinen wrote:
> The feature set of libpulse will necessarily track the features of the
> pulseaudio daemon. Is the idea to take a subset of the libpulse API and
> make that work on non-pulseaudio platforms?
Haven't sorted out which features really require a daemon
Hi folks,
I'm just wondering whether something like PA's client API could
ever become a real crossplatform standard API.
The problem behind is there're tons of audio APIs - most of them
doing more or less the same. So application developers have a hard
time picking the right one, and dist
hi folks,
does anybody known an working pulseaudio server for Android ?
I'd like to use an (older) android phone as mobile headphone.
thx
--
Enrico Weigelt,
metux IT consulting
+49-151-27565287
___
pulseaudio-discuss mailing list
