Re[2]: [XviD-devel] New Motion Estimation (from sysKin) committed to branch

Marc FD xvid-devel@xvid.org
Tue, 24 Sep 2002 17:20:27 +0200


----- Message d'origine -----
De : "Radoslaw 'sysKin' Czyz" <syskin@bigpond.com>
À : <xvid-devel@xvid.org>
Envoyé : mardi 24 septembre 2002 16:29
Objet : Re[2]: [XviD-devel] New Motion Estimation (from sysKin) committed to
branch


> Hi
>
> >> I'll re-do the changes to the cvs' encoder.c and post them, ok?
>
> > Sure, please do.
>
> OK I did. I attach all affected files, it should work (I'll never
> write 'it will work' again ;> ) when old files are just replaced with
> new ones.
>
> Now, allow me to write a small 'todo' list.
> What we need to make it work even better, is:
> - mmx-ed sad16v. sad16v is a base of entire P-frame search if inter4v
> is on, but we currently only have XMM-ed version. All other
> architectures will also use cpu-specific, but not optimal, code.
>
> It's defined as follows:
> uint32_t sad16v(const uint8_t * const cur,
>                 const uint8_t * const ref,
>                 const uint32_t stride,
>                 int32_t *sad)
> {
>         sad[0] = sad8(cur, ref, stride);
>         sad[1] = sad8(cur + 8, ref + 8, stride);
>         sad[2] = sad8(cur + 8*stride, ref + 8*stride, stride);
>         sad[3] = sad8(cur + 8*stride + 8, ref + 8*stride + 8, stride);
>
>         return sad[0]+sad[1]+sad[2]+sad[3];
> }

it's so easy to do, i think one of the CVS guys should do it ;)

>
> - hinted ME & B-frames. Well it shouldn't be difficult to fix, I have
> no idea why it doesn't work. I mean for P-frames only, of course. It
> speeds up 2nd pass without affecting quality (or it's increasing it a
> bit).

BTW, can you try a mode when Hinted ME would be used in one pass ??
i know it would be a bit slower but it would allow advanced pre-processing.