[XviD-devel] MV-clipping problem?

[skal]

	hi all,

On Wed, 2004-02-25 at 04:07, Radek Czyz wrote:
> skal wrote:
> 
> > 	Hi all,
> > 
> > 	amongst the ref bitstreams, there are some
> > 	nasty ones with huge, out-of-boundary, MVs.
> > 	Eg.:
> > 	vcon_ge_23_ace_l*.bits
> > 	vcon_a1ge_13_ace_l*.bits   (qpel)
> > 
> > 	When xvid_decraw is fed with them, valgrind reports
> > 	invalid reads during MC. Unfortunately, i was unable
> > 	to locate the possibly faulty MV-clipping func.
> > 
> > 	Could someone confirm?
> 
> I think there isn't one. Decoder is kinda designed to crash with broken
> bitstreams, unfortunately.

> ..
	Radek: attention! These are not "broken" bitstreams, but rather
	"stress" bitstreams. The dMVs are perfectly valid ([-2048,2047],
	with fcode=7), yet perfectly non-sense.

	Jim: The ref bitstreams are available here:
	ftp://ftp.tnt.uni-hannover.de/pub/MPEG/video/conformance/version_2/

	Bye!
Skal