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

List:       kde-multimedia
Subject:    Re: artsplug near final
From:       Martin Vogt <mvogt () rhrk ! uni-kl ! de>
Date:       2000-06-21 10:10:30
[Download RAW message or body]

> > 
> > And this too ?
> > Perhaps putting mpeglib on kdesupport ?
> > (btw, is mpeglib the mp3 decoder, the mpeg video decoder, or both ? )
> 
> I can only second the CVS issue: if we don't have it there, chances are good
> that most users will never even notice that there is mp3 support...
>
The point is:

* where we should put it.

I think we cannot put it in kde-multimedia, because the artsplug
lib is linked against mpeglib and libtool does not support
linking against not installed libraies.

This is the reason why artsplug is seperate from mpeglib because
you must install mpeglib first.

* I have no CVS access

* mpeglib will never work on some old Linux systems, libc based systems
  maybe this is a point to consider.
 
 
> 
> My only concern currently is how far we'll get in the future (> KDE2.0) when
> we keep the strict seperation between aRts and standalone mpeglib code.
> Especially once we start extending aRts in the direction of more modularity
> regarding decoding and playing, video codecs, threading support, ...
>
Then split/remove/delete mpeglib. 

I think it will take some time until arts supports all this.
But then you can rip the codecs from mpeglib.
                     
Or choose other codecs. 
           
mpeglib and the "bridge" artsplug works now. If there is something
better in the future, simply remove the old things.

Another way would be to "migrate" mpeglib slowly to new arts interfaces.
(For example if arts supports video frames, use this interfaces
instead of mpeglibs)

If it supports inputStream use them in mpeglib.

and so on.

For KDE 2.0 I think to keep it how it works now.   
 
> Still, we can try this approach, and if it doesn't work, we'll try something
> else. So far, I am quite happy with the interoperability that is available
> now between mpeglib and aRts.
> 
         
It supports the kmedia2 interface, nothing more was planned for KDE 2.0

> So after everybody telling: "mpeglib should be in the CVS", would anybody
> like to put it there, maintain it there, update new versions, fix bugs, make
> sure that it integrates with the build system and such? Martin? Somebody else?
>
Hm.
Im currently unsure. mpeglib is used by two other developers
(and maybe more I now nothing about)
   
Some bugs are "unfixable", like the old libc/thread problem.
It should run on FreeBSD, but I had no success reports for a
long time.
The interlibrary dependencies...

And of course I have no CVS access.

Before we put it in, we should clear these things. 
And we should clear which codecs should be in.
Should the yaf-* part be included, should we move
ogg/vorbis into the lib, etc...

For examples vob/ac3 is very experimental,I can already
hear the user cry, that they cannot play dvd, because we
cannot include DeCss...

Mpeglib runs on alpha but (not yet) on Sun etc..
Its a rather big library and KDE 2.0 is already in freeze.

Maybe we should include it, but before that I would like to
have more people to test it, if it _really_ works for them.


regards,

Martin      
 
 
_______________________________________________
Kde-multimedia mailing list
Kde-multimedia@master.kde.org
http://master.kde.org/mailman/listinfo/kde-multimedia

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