aRts vs JACK
zyzstar at uid0.sk
Fri Feb 21 21:30:16 GMT 2003
On Fri, Feb 21, 2003 at 10:01:35PM +0100, Matthias Kretz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Friday 21 February 2003 22:01, Jozef Kosoru wrote:
> > 1) JACK is low-latency sound server with callback-driven API - CSL
> > probably not.
> CSL is a wrapper library not a sound server... I don't know what your
Use google for JACK, ASIO and ReWire documentation and you will understand
what I'm talking about.
> > 2) It adds one more layer to every aRts-aware application.
> > see:
> > application
> > +->CSL
> > +->aRts
> > +->JACK
> > +->sound card
> Hmm, this would be a misuse, but I guess a possible use.
Possible use for the user who needs aRts and JACK in the same time.
> > One must understand that any serious audio application will never use this
> > scheme. This is just another overdesigned idea. Do we really need COBRA
> > based CSL for playing xmms and kaboodie?
> CORBA based CSL? Did I miss something?
> 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, I misuderstand the 3th slide (it was about the aRts, not CSL).
IMHO CSL could be the great thing if it allows me to write CLS layer for
JACK (to run necessary KDE application) and forget about aRts forever.
jozef kosoru [zyzstar] <zyzstar at uid0.sk>
More information about the kde-multimedia