aRts vs JACK

Neil Stevens neil at
Fri Feb 21 21:27:29 GMT 2003

Hash: SHA1

On Friday February 21, 2003 01:16, Matthias Kretz wrote:
> On Friday 21 February 2003 22:15, Neil Stevens wrote:
> > On Friday February 21, 2003 01:01, Matthias Kretz wrote:
> > > I was in the best belief, that all CSL is trying to achieve is, that
> > > you're programming your audio output with CSL and automagically your
> > > program is able to use any soundserver/output CSL supports. Please
> > > correct me if I'm wrong... (I'm pretty sure I'm not ;-) )
> >
> > Well, but arts is the only existing system that gives us decoders, so
> > CSL would just add another layer.
> I'd need to look a the CSL code, but I guess it could be possible to use
> aRts' features when CSL outputs through artsd.
> If not, well, playing sound streams is always supported - for sure - and
> having a media framework for decoding in process won't hurt either...

Yes it will.  Right now, if a decoder crashes, the app has to just restart 
arts.  If we move deocding in process, a crashed decoder crashes the app.  
KNotify, konqueror (previews), noatun, kaboodle, and most of kdeedu and 
kdegames, and more would become less stable if one unreliable playobject 

> > So I don't see any value in KDE adopting CSL.
> Well if forcing KDE users to have to use aRts and not be able to choose
> is a good thing to do... then you're probably right.

Yes, KDE has to force its users to use certain libraries and services.  We 
force X, we force Qt, we force unix, we force C++.  Forcing one more thing 
doens't hurt.  We don't force you to run aRts after all.. we only force 
you to use it if you want audio.

- -- 
Neil Stevens - neil at
"Distinctions by race are so evil, so arbitrary and insidious that a
state bound to defend the equal protection of the laws must not allow
them in any public sphere." -- Thurgood Marshall
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-multimedia mailing list