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

List:       kde-multimedia
Subject:    Re: Some ideas for the aRts-replacement
From:       Neil Stevens <neil () hakubi ! us>
Date:       2004-02-20 0:40:49
Message-ID: 200402191640.50033.neil () hakubi ! us
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday February 19, 2004 4:15 pm, Koos Vriezen wrote:
> Scott Wheeler wrote:
> > Also reasonable.  But let's define some precise terms -- "backend"
> > isn't meaningful.  Let's say:
> >
> > "sound server" -- a hardware abstraction, i.e. Jack or ESD
> >
> > "media framework" -- a library or set of libraries that may or may not
> > specifically work with a "sound server" to decode and generally handle
> > *audio and video* media.
>
> Apart from if arts or gstreamer would be choosen as a media framework,
> should all KDE apps be linked to this framework, like it's now
> with arts?

Most KDE apps don't link to aRts.  KDE apps with simple sound needs just 
use KNotifyClient.  KNotify links to aRts, but KNotify users do not.

This would not change if we replaced aRts with GStreamer.  Only apps 
needing more complex features (such as those in kdemultimedia) would link 
to GStreamer.

> I hope this discussion is converging to having a small sound server,
> used by all KDE apps (with no linking penalties, lazy initialization
> etc).

Won't work.  We need decoders, and a dumb sound server doesn't supply one.

- -- 
Neil Stevens - neil@hakubi.us

"It's snowing, it's snowing! God, I hate this weather."
    They Might Be Giants, __New York City__
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFANVeSf7mnligQOmERAq/EAJ9WcIdrwjGYD4Rf3hbko99ufV7vIQCfUcSa
/o/+sZGWPoMtLTE5nmHYm70=
=jNIt
-----END PGP SIGNATURE-----

_______________________________________________
kde-multimedia mailing list
kde-multimedia@kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia

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