[MPlayer-cvslog] CVS: main/libfaad2 drm_dec.c, NONE, 1.1 drm_dec.h, NONE, 1.1 Makefile, 1.9, 1.10 README, 1.5, 1.6 analysis.h, 1.4, 1.5 bits.c, 1.5, 1.6 bits.h, 1.7, 1.8 cfft.c, 1.6, 1.7 cfft.h, 1.4, 1.5 cfft_tab.h, 1.6, 1.7 common.c, 1.6, 1.7 common.h, 1.12, 1.13 decoder.c, 1.6, 1.7 decoder.h, 1.6, 1.7 drc.c, 1.5, 1.6 drc.h, 1.4, 1.5 error.c, 1.5, 1.6 error.h, 1.5, 1.6 filtbank.c, 1.6, 1.7 filtbank.h, 1.5, 1.6 fixed.h, 1.6, 1.7 hcr.c, 1.6, 1.7 huffman.c, 1.5, 1.6 huffman.h, 1.5, 1.6 ic_predict.c, 1.4, 1.5 ic_predict.h, 1.4, 1.5 iq_table.h, 1.6, 1.7 is.c, 1.6, 1.7 is.h, 1.5, 1.6 kbd_win.h, 1.5, 1.6 local_changes.diff, 1.6, 1.7 lt_predict.c, 1.5, 1.6 lt_predict.h, 1.5, 1.6 mdct.c, 1.6, 1.7 mdct.h, 1.5, 1.6 mdct_tab.h, 1.3, 1.4 mp4.c, 1.6, 1.7 mp4.h, 1.6, 1.7 ms.c, 1.5, 1.6 ms.h, 1.5, 1.6 neaacdec.h, 1.2, 1.3 output.c, 1.11, 1.12 output.h, 1.6, 1.7 pns.c, 1.6, 1.7 pns.h, 1.6, 1.7 ps_dec.c, 1.4, 1.5 ps_dec.h, 1.3, 1.4 ps_syntax.c, 1.2, 1.3 ps_tables.h, 1.2, 1.3 pulse.c, 1.6, 1.7 pulse.h, 1.5, 1.6 rvlc.c, 1.5, 1.6 rvlc.h, 1.5, 1.6 sbr_dct.c, 1.6, 1.7 sbr_dct.h, 1.6, 1.7 sbr_dec.c, 1.7, 1.8 sbr_dec.h, 1.7, 1.8 sbr_e_nf.c, 1.6, 1.7 sbr_e_nf.h, 1.6, 1.7 sbr_fbt.c, 1.6, 1.7 sbr_fbt.h, 1.5, 1.6 sbr_hfadj.c, 1.6, 1.7 sbr_hfadj.h, 1.6, 1.7 sbr_hfgen.c, 1.6, 1.7 sbr_hfgen.h, 1.6, 1.7 sbr_huff.c, 1.6, 1.7 sbr_huff.h, 1.5, 1.6 sbr_noise.h, 1.5, 1.6 sbr_qmf.c, 1.7, 1.8 sbr_qmf.h, 1.7, 1.8 sbr_qmf_c.h, 1.5, 1.6 sbr_syntax.c, 1.6, 1.7 sbr_syntax.h, 1.5, 1.6 sbr_tf_grid.c, 1.6, 1.7 sbr_tf_grid.h, 1.5, 1.6 sine_win.h, 1.5, 1.6 specrec.c, 1.7, 1.8 specrec.h, 1.6, 1.7 ssr.c, 1.5, 1.6 ssr.h, 1.5, 1.6 ssr_fb.c, 1.5, 1.6 ssr_fb.h, 1.5, 1.6 ssr_ipqf.c, 1.5, 1.6 ssr_ipqf.h, 1.5, 1.6 ssr_win.h, 1.5, 1.6 structs.h, 1.7, 1.8 syntax.c, 1.6, 1.7 syntax.h, 1.6, 1.7 tns.c, 1.6, 1.7 tns.h, 1.5, 1.6

[Diego Biurrun]

On Wed, Apr 19, 2006 at 11:27:42AM +0200, Reimar Döffinger wrote:
> On Tue, Apr 18, 2006 at 09:39:39PM +0200, Roberto Togni CVS wrote:
> > Update to faad2 cvs 20040915+MPlayer fixes
> > Patch by me and Emanuele Giaquinta
> 
> Does that mean there will probably no further external updates?

Unless they revert their license change, which at this point seems
unlikely, I think it's safe to consider this code forked.

> Should I try to cleanup my speed improvement patch and submit it?

Sure, why not..

> I heard some other project was using (parts?) of it, does anyone know
> details, e.g. if they did some cleanup work on it?

No idea.  I know that xine also includes a copy of libfaad.

Diego