[xine-devel] Re: xine

[Guenter B. <bar...@st...>]

Hi Maxime,

On Mon, 18 Dec 2000, Maxime Austruy wrote:

> I'm a french student interested in contributing to xine, 

great! :-)

> and since I don't want to work on something that is already taken care
> of, would you mind telling me the point you would like me to work on??

we're just setting up our bugtracking system so perhaps you could have a
look at it (xine sourceforge project page -> bugs). I don't think it's
that complete but it should give you a first impression of what the
current issues are that we're working on.

I don't know about your abilities so it's hard for me to decide what you
could work on. If you see something that you think is interesting (in the
bugtracking system or anywhere else in xine or on our mailing lists) just
drop me a line and I can tell you if somebody else is working on that
already.

> Since I own a H+, have you ever thought of supporting (like OMS) such
> hardware?

We've had requests regarding such features but nobody was offerings help
until now :-) However I must say that this is not a top-priority for now
and I'm not sure if it's that easy to integrate hardware decoder support
in xine. xine is designed to be a fast software-only decoder and that's
our main focus. The hardware decoder cards all have very different
features (h+ can't do audio decoding in hardware AFAIK) and I don't want
xine to become a huge dynamic linking project like OMS and without that I
think it's hard to support a variety of hardware decoders within a single
application.

BUT: that doesn't mean we can't do anything in that direction. Heiko and I
have already talked about this and we came to the conclusion that
developing a player application for the h+ (or other mpeg2 decoder
cards) based on the xine sources (but in a seperate source tree) would be
possible and IMHO could really make sense. 

So if you want to develope anything to that end I really suggest you set
up your own source tree for that (of course I'd help you with that if you
want me to). In that tree you'd be free to change everything and hack the
h+ support in without having to fear the "mainstream" xine breaks. As soon
as you've got the h+ working we can compare the two source trees and see
where there differences are and if it is possible/usefull to merge them
into one tree or if it's better to maintain the two players seperately.

Now, these are just my ideas and thoughts, comments are welcome! :-)

Regards,

   Guenter


-- 
   xine - a free video player

   http://xine.sourceforge.net

NEW: xine mailing list:
http://lists.sourceforge.net/mailman/listinfo/xine-user