HI all,
Following up some cool feedback from a kind person who ran some 1.6.2
mplex/mpeg2enc sequences through a commercial SVCD stream validator I finally
got a lead on the issue with motion artefacts when dual-prime motion
estimation is active.
It turns out that under certain circumstances with rapid motion present in the
source image the motion vectors generated can be larger than permitted by the
'f-code' in the picture header.
This is exactly the kind of 'out of MPEG spec' stuff that can cause problems
on hardware decoders but often sails through invisibly in the more flexible
SW players.
I am about 1/2 done a fix in the current developer branch of mpeg2enc: I've
replaced the old reference encoder derived dual-prime code with a clean
from-scratch routine but it now needs to be tested to knock out the coding
bugs. In the meantime I'll probably put a quick-and-dirty work-around into
the stable branch.
cheers,
Andrew
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
