as Scott Wheeler isn't a subscriber to this list he was not
allowed to send it to the list directly. Instead, I'll
forward it for him:
> > Apparently aRts could be removed from KDE4 CVS HEAD RSN.
I haven't seen the rest of this discussion, but it seems out
of place to me.
Pretty much any discussion on the future of KDE multimedia
should happen on
the KDE multimedia list (firstname.lastname@example.org). Discussions
-- for better or worse -- are likely to be fruitless.
> > I have no say in the matter but I would
> > My general question, to those who know far more than me,
Well, it's a step back from that in a sense. We're kind of
punting on this
one for KDE 4. Matthias Kretz has been working on a generic
"typical" user applications (think players and maybe some
that will load plugins which implement the API. GStreamer
will certainly be
one of those and may be the default, but also as was noted
GStreamer isn't a
soundserver or collection of drivers. It's a framework for
multimedia pipelines that handle demuxing, decoding,
processing and then dump
them somewhere -- there are "sinks" for various audio and
video systems. The
same goes for NMM, which is another likely candidate for a
> I guess JACK will *not* be an option for the KDE team
Actually it won't be an option because it's a soundserver.
We're not looking
for a soundserver, we're looking for a multimedia framework.
How the sound
gets to the soundcard/soundserver is up to that framework.
> For this reasons, it seems to be more probable that
Just to repeat again -- KDE most likely won't be choosing a
the very most we may have some recommended defaults. I said
it above, but
it's worth repeating -- Jack is a soundserver; the problems
that Jack solves
aren't really all that relevant to KDE's multimedia decisions
orthogonal to them.
Three words: you have no clue