Phonon xine backend future

[Harald Sitter]

On Tue, Feb 22, 2011 at 3:13 PM, Ian Monroe <ian at monroe.nu> wrote:
> How do you plan to have this implemented? How do we make this cross-platform?

I imagine it would be like the volume stuff etc. PulseSupport would
just intercept the call to the appropriate API interfaces and thus
override the backend's EQ. That is pretty much a nobrainer, just a
couple of ifdefs around the PulseSupport interception code.

> I know what we want from the end-user perspective: that the same
> client code with PA would work without PA if the multimedia backend
> has support for  the eg equalizer.

Which would be the case. PA would just override an implementation in
the framework/library.

Example:
* app queries for effects
* (new and improved) API returns a list of enum values of effects
* PulseSupport checks if list contains EQ, if not -> adds it
* app wants to use EQ
* PulseSupport intercepts call within libphonon and processes it in
place of the backend
* app manipulates EQ settings
* PulseSupport intercepts call within libphonon and once more
processes it in place of the backend
...

This scales very well, PA just sits between API consumer and the
backend when Phonon is built with PA support.

regards,
Harald