[x264-devel] out-of-range motion vectors

[CAdevel]

>
> dia: --merange is the max number of iterations. Since each iteration moves
> one pixel, it's also the max range.
> hex: --merange/2 is the max number of iterations. Since each iteration
> moves up to 2 pixels, --merange is also the max range.
> umh: --merange is the average radius of the grid part of the search, but
> any given block may use more or less depending on whether it predicts the
> mv to be large. umh then calls hex for another merange/2 iterations. So
> the max range is about --merange*3.
> esa: Simply examines all possible mvs within --merange.


Look at those maximum motion vectors I found:
--me hex with:
    --merange 24   -> 168
    --mvrange 24   ->  39
--me esa with:
    --merange 16    -> 272
    --mvrange 16     -> 37

So using the --mvrange option the motion vectors make sense, but using the
--merange option they do not. Or am I wrong?


In all cases the search starts at some predicted location, not at (0,0).


Is this inside the macroblock or anywhere in the picture? How is this
predicted start location calculated?

Cor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.videolan.org/pipermail/x264-devel/attachments/20070731/1fd25bfc/attachment-0001.htm 
-------------- next part --------------
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
http://mailman.videolan.org/listinfo/x264-devel