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

List:       kde-core-devel
Subject:    Re: Disabling aRts in knotify
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2004-02-18 20:22:48
Message-ID: 200402182122.48273.neundorf () kde ! org
[Download RAW message or body]

On Wednesday 18 February 2004 20:51, Matthias Kretz wrote:
> On Wednesday 18 February 2004 20:25, Alexander Neundorf wrote:
...
> > Basically these plugins would simply forward sampled raw audio data to
> > the backend. Almost no cpu usage, much few chances to crash, etc.
>
> This wouldn't even be enough since you need to do the reading, decoding and
> resampling (if needed) to be able to play .wav and .ogg files. For knotify
> and probably for some simple games that'd be ok then. But a media player or
> a game relying on the right timing of the sound might have a lot more
> complex needs. (just to let you know it's not a piece of cake to get this
> right)

But this shouldn't be on the same level.
Above the level covering the low-level interface (play these samples, set up 
channels and frequency, ... ) there should be another layer: "play this file" 
including decoding, resampling etc. This layer would then immediately be 
independent from the actual backend (OSS/ALSA/MAS/arts/gstreamer).
These functions shouldn't be mixed within one layer  ("layer" not meaning 
daemons streaming data from one to another via IPC).

Maybe this is one of the reasons that arts didn't become a real success: it 
tries to do so many things at once (network transparency, mixing audio audio 
streams, decoding, effect plugins, snythesizer, ...)

K.I.S.S. !

Bye
Alex
-- 
Work: alexander.neundorf@jenoptik.com - http://www.jenoptik-los.de
Home: neundorf@kde.org                - http://www.kde.org
      alex@neundorf.net               - http://www.neundorf.net
[prev in list] [next in list] [prev in thread] [next in thread]