[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Multiple sounds with phonon
From:       Andreas Scherf <ascherfy () googlemail ! com>
Date:       2010-06-21 18:36:12
Message-ID: 201006212036.13072.ascherfy () googlemail ! com
[Download RAW message or body]

Sure, and not to mention the KDE settings. But as a kde game maintainer there 
are some problems with phonon. I use the game profile and the response time is 
very slow. So it would be nice if we could find a way to fix this. 

Andreas


Am Montag, 21. Juni 2010 schrieb Aaron J. Seigo:
> On June 16, 2010, Nikos Chantziaras wrote:
> > Long answer made short: use SDL, fmod or some other similar audio
> > library.
> 
> let me suggest something "radical" here: follow in the footsteps of Amarok,
> who also rely on Phonon, and do some work on Phonon itself.
> 
> ok, so it's not very radical; in fact, i'd nearly call it common sense.
> while Phonon is certainly never going to fill 100% of use cases, it should
> be able to cover these kinds of use cases.
> 
> falling back on other solutions just because Phonon doesn't do $FOO when
> Phonon is our own API that we can hack on and improve borders on the
> shortsighted. yes, it's perhaps a bit easier now (esp if you already know
> SDL or whatever, less so if you don't) but it's not easier for:
> 
> * our packagers and users (more dependencies)
> 
> * not better for other app developers that will feel they need to do the
> same work (more repetitive research and API learning)
> 
> * not better for Phonon's future
> 
> * not better for the portability and future maintainability of your
> application (having to pick and then track a future proof and API-reliable
> solution)
> 
> if there are complete roadblocks / design walls that get run into, then
> let's document those and figure out what to do. but running in different
> directions is not very "KDE".

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]