From kde-core-devel Wed Feb 18 20:58:52 2004 From: Matthias Kretz Date: Wed, 18 Feb 2004 20:58:52 +0000 To: kde-core-devel Subject: Re: Disabling aRts in knotify Message-Id: <200402182158.56923.kretz () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=107713782823004 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--Boundary-02=_QI9MATrjSSWoKGc" --Boundary-02=_QI9MATrjSSWoKGc Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 18 February 2004 21:48, Alexander Neundorf wrote: > On Wednesday 18 February 2004 21:25, Scott Wheeler wrote: > ... > > > Again, none of the multimedia apps in KDE deal with raw audio. I know > > that solution sounds attractive and all that, but it's just not a simple > > problem and there's no silver bullet for fixing it. From a software > > developers > > Yes, they all use the sound stuff which depends on arts. > Turning encoded audio into raw samples is independent from the api of the > backend (OSS/ALSA/MAS/arts....). Looks like your definition for a backend is only the sound output... > The decoding step should also handle=20 > things like resampling to the sample rate of the backend, to the number of > channels of the backend, etc. And after this is done, the decoded raw data > should be playable by any backend (otherwise I'd consider the api of the > backend broken). But what you're getting at here is to create a media framework. We have=20 frameworks available with gstreamer, aRts, NMM and MAS. Creating our own=20 would not be the way to go (IMHO). I'd rather see KDE able to use any of th= e=20 frameworks. Because different people have different needs and KDE should be= =20 able to cope with that. =2D-=20 C'ya Matthias ________________________________________________________ Matthias Kretz (Germany) <>< http://Vir.homeip.net/ MatthiasKretz@gmx.net, kretz@kde.org, Matthias.Kretz@urz.uni-heidelberg.de --Boundary-02=_QI9MATrjSSWoKGc Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAM9IQyg4WnCj6OIoRAn1/AJ0eEf1xo8cfhopmjwRoDt64Hq716gCfZsER M8H1vDXg8Cm0/V30+hNfR6w= =8FJm -----END PGP SIGNATURE----- --Boundary-02=_QI9MATrjSSWoKGc--