12
12
project version mediator
13
13
-----------------------------------------------------------------------
15
ffmpeg build 4715 Mike Melanson
15
ffmpeg 50.1.0 Mike Melanson
17
17
gsm610 1.0.10 Mike Melanson
21
21
libdvdnav 0.1.10 Michael Roitzsch
22
libfaad 2.0 Miguel Freitas
22
libfaad cvs-2005-01-30 [GPL] Miguel Freitas
23
23
libmad 0.15.1b Miguel Freitas
25
25
libmusepack svn 13/01/05 James Stembridge
32
32
-----------------------------------------------------------------------
34
[GPL] this is the latest GPL compatible version of FAAD2. later cvs
35
snapshots have added an advertisement clause so we cannot update until
36
the situation gets fixed.
35
39
[*] common question: lastest version of libmpeg2 is 0.3.1, why don't
38
the answer is not so simple.
40
quoting libmpeg2.sf.net: "The old API [0.2.x] was not flexible enough for
41
most users, as a result various projects (xine, mplayer etc...) ended up
42
rewriting their own versions of decode.c."
44
this is indeed true: in order to support a lot of dvd features, menus with
45
still frames, closed caption decoding and better buffer management for
46
xine it was needed to patch our libmpeg2 copy. of course we should always
47
try not to "fork" external projects, but in the libmpeg2/xine case it is
48
easy to see (from CVS logs) how long did it took to reach the stability
51
so, while targeting a stable libxine release, there is no hurry in
52
updating libmpeg2 and this is not the trivial task as it might sound.
54
note that we have also backported some fixes/improvements from libmpeg2
55
cvs (eg. motion vector clipping for broken streams). if you need any
56
specific change or fix feel free to send us a patch or discuss the issue
42
the answer is not so simple.
44
quoting libmpeg2.sf.net: "The old API [0.2.x] was not flexible enough for
45
most users, as a result various projects (xine, mplayer etc...) ended up
46
rewriting their own versions of decode.c."
48
this is indeed true: in order to support a lot of dvd features, menus with
49
still frames, closed caption decoding and better buffer management for
50
xine it was needed to patch our libmpeg2 copy. of course we should always
51
try not to "fork" external projects, but in the libmpeg2/xine case it is
52
easy to see (from CVS logs) how long did it took to reach the stability
55
so, while targeting a stable libxine release, there is no hurry in
56
updating libmpeg2 and this is not the trivial task as it might sound.
58
note that we have also backported some fixes/improvements from libmpeg2
59
cvs (eg. motion vector clipping for broken streams). if you need any
60
specific change or fix feel free to send us a patch or discuss the issue
63
update plan for libmpeg2: we should leave our patched libmpeg2 for
64
hardware accelerated decoding (xvmc) only and use "libmpeg2new" (containing
65
updated libmpeg2) for software decoding.
60
68
[o] These libraries are not well maintained and subsetted from the