[XviD-devel] [BUG??] New I/P decision code

Christoph Lampert chl at math.uni-bonn.de
Wed Mar 5 10:26:26 CET 2003


On Tue, 4 Mar 2003, elcabesa wrote:
> maybe i have choose a wrong subject ofr this post, or maybe new Syskin code is 
> right and old was not..
> but today cvs lead to a 7% bigger file than yesterday cvs checkout..
> i simply can't tell you if syskin code break something. today there were 2 or 
> 3 independent cvs commit and something make xvid produce this bigger file
> 
> it can be that now xvid  use the right max_iframe=)
> 
> my test was done a fixed_quant=4  without enabling b-frames, qpel or anithing 
> else.
> 
> i was thinking that the "problem" came form syskin patch since  other one was 
> a simply code speedup by unrolling loops
> see you

Hi,
my unrolling was only for PLAIN-C parts, and internal checksums were not
changed, but that of course doesn't mean anything... 

Still, I would again suggest an automatic mailing list which sends all
commits to CVS to the subscribers. I found this link as a reference: 

http://www.durak.org/cvswebsites/howto-cvs/node39.html

This makes it much more comfortable to track down bugs in freshly commited
code. 

gruel 




More information about the XviD-devel mailing list