[FFmpeg-devel] [FFMPEG] [PATCH] cavs encoder

zhihang wang zhihang.wang
Sat Nov 21 00:25:33 CET 2009

> *On my first attempt of an encoder I decided to put my own motion
> estimation code in, even if it was a very simple one.
> The code in motion_est_template.c and motion_est.c seems to have
> some unsuitable assumptions:
> - that a skipped macroblock has motion vector (0,0)
> - that qpel needs different filter functions
> - how the chroma vector is calculated from luma (in qpel case and else)
> - that mid_pred is used for mv prediction
> - and maybe more
> Even if not all of above is correct I think it would be very difficult
> to extend this optimized-for-MPEG-type-video code to a more generic
> handling without having a speed regression. But I do certainly agree
> that H.264 and AVS encoders could share a lot of motion estimation
> code if that were to be written.*
Yes. Need I split the me mode into a common file just  like motion_est.c to
enable h264 and AVS share the same me code? Now, I don't find any me code in
the existing h264 encoder. But if the me model of AVS is written in a single
file, the h264 encoder can share this model.
Best Regards
zhihang wang(???)

More information about the ffmpeg-devel mailing list