[Ffmpeg-devel] Re: [RFC] mpeg2 422 encoding.

[Baptiste COUDURIER]

Hi

Michael Niedermayer wrote:
> [...]
> 
> no, there are no motion vectors for chroma the chroma vectors are the same
> as the luma vactors (ignoring scaling & rounding ...)
> 
> and i dont think that theres a relation between -me xyz, the number of b
> frames and the (-mbd bits) bug its probably just a "coincidence"
> you should rather look at the mb_decision != 0 specific code, i also
> think that the mbd bits bug isnt critical and could be dealt with after
> 422 encoding support has been added
> 

All right then,

A new patch is attached I only inlined encode_mb, and mpeg1_encode_mb in
mpeg12.c, I left START/STOP TIMER funcs around encode_picture.
Interlaced encoding in 422 works. I removed all encode_mb_hq changes for
now.

I get good performance with that patch. Equal/faster on xeon 2.8ghz. I
wonder why faster sometimes, maybe inlining whole encode_mb did that.
What do you get ?

-- 
Baptiste COUDURIER                              GnuPG Key Id: 0x5C1ABAAA
SMARTJOG S.A.                                    http://www.smartjog.com
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
Phone: +33 1 49966312
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 422_mpeg2_encoding.patch
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20060507/6837296b/attachment.asc>