On Mon, Mar 04, 2002 at 12:23:42PM +0100, Zdenek Kabelac wrote: > Hello > > I'd like to relase some CVS snapshot this week - but I'd > like to know if there are some serious bugs which might > either completely stop compilation on some linux boxes or > just you get some permament crashes. > > As a feature of the day I've added native support for XviD. > So let's just try and test - if someone has some reasonable > defines for this codec let me know - I'd like to > put there some good initial values so it would not produce > 'blocky' images - for now it looks like using Quality 5 > might be good idea - but if there is anyone who has deeper > knowledge about this codec and which values seems to be > good one let me know.
I do not know much about it, but I used the values from core/examples/xvid_encore.c from the xvid dist (21-01-02), and they seem to be okay. The quality (set by motion_search) seems to have the largest effect, but higher quality also slows it down. > Oh and be prepared it will be crashing with some DivX files > as it has some compatibility issues and also it seems > to be producing a lot of 'unsupported like' messages... > > But I would have say it's currently the fastest codec for TV capturing Yes :-). I will declare it to my favorite encoder for my TV recordings now. Greetings, Oliver -- It's true! The author of masqmail mailed to you! See http://masqmail.cx/masqmail/
msg02904/pgp00000.pgp
Description: PGP signature
