MAS in KDE

[Tim Jansen]

On Wednesday 05 March 2003 18:24, Mike Hearn wrote:
> OK, so the reason that we can't just standardise on Jack and make
> everybody mostly happy is that it's not network transparent?

At least that's one of the reasons why it is not a obvious choice. Others 
include:
- KDE already uses Arts and switching is difficult for many reasons
- Some people think that MAS's close relationship to X.org makes it a good 
choice


> About the
> last point, does being able to decode and encode network audio/video
> imply having the media framework *inside* the sound server a la aRts, or
> would writing say an ogg filter for the network transparency jack plugin
> be enough?

Ideally you would want the sound server to support every format that you want 
to hear, including those that are embedded in videos. So unless you want to 
implement every codec twice or support only some formats for thin-clients or 
distributed applications or want to re-encode the sound (which is especially 
bad for thin-clients, since many users share a single server), the sound 
server should share the same codecs.


> If the idea is you can stream audio before it's decompressed, then maybe
> a codec on the networking side is good enough, after all if you're using
> a network performance isn't critical anyway, and not everything played
> via the media framework would be compressed anyway. 

For playback, yes. But what about applications that edit/convert/process 
sound? 


> > Unless someone comes up with a server that has all those features, KDE
> > has two choices:
> So basically the blocking issue is the lack of a sound server that is
> good enough for everybody?

Different question: assuming that there would be a sound server that would be 
at least as good as the competition in every aspect, would will still have to 
argue?

bye...