Re: [XviD-devel] todo/action list

["daniel smith" <danielsmith@xxxxxxxxxxxxxxxx>]

i would add:

VFW
* simplify interface - remove some 2-pass options no-one uses, create alternate 
"really really simple" front-end with 4 or 5 options max.

DSHOW
* import all of Nic's nice code

XVIDCORE
* track down why xvid can't properly encode/decode sequences of odd 
widths/heights - mpeg4 spec says we should handle *any* resolution, even 322*243

XVIDCORE/IMAGE
* colorspace mmx patches/optimizations

XVIDCORE/ME
* investigate "good" field-based motion estimation methods

XVIDCORE/DCT
* use fast/inaccurate fdct/idct for b-frames

----- Original Message -----
From: "peter ross" <suxen_drol@xxxxxxxxxxx>
Date: Sat, 31 Aug 2002 12:11:38 +1000 
To: xvid-devel@xxxxxxxx
Subject: [XviD-devel] todo/action list


> hey all.
> while we've twidling our thumbs, let's make a todo/action list.
> ---
> 
> BUGS
> * rework timebase/timeincr code
> * interlacing bug
> * zero idct coeff issue
> 
> XVIDCORE
> * adds skals fast vlc code [IN PROGRESS]
> * examine/implement new fdct algo [IN PROGRESS]
> * fix invalid memory access; mentioned by gruel
> * incorporate platform independant 2-pass vbr
> * prefiltering
> * api v3.
> 
> XVIDCORE/ME
> * optimise getpmv/macroblock structure
> * permit different motion search algos to be selected at runtime
> 
> XVIDCORE/BFRAMES
> * 2pass statistics and mvhiting
> * add dynamic fcode/bcode
> 
> XVIDCORE/DECODER
> * auto/width height detection
> * cleanup bframe mb_decoding functions
> * post processing
> 
> FRONTENDS
> * import quicktime frontend into cvs & clean up
> * contact nullsoft about their winamp3 plugin interface;
>   currently their implementation does not do xvid justice.
> 
> FRONTENDS/VFW
> * export a Configure() function, such that vfw can be configured
>   from the commandline/shortcut, e.g. rundll32 xvid.dll,Configure
> 
> -- pete

-- 
_______________________________________________
Get your free email from http://www.astroboymail.com

Powered by Outblaze