[Ffmpeg-cvslog] CVS: ffmpeg/libavcodec motion_est_template.c, 1.29, 1.30 utils.c, 1.179, 1.180 avcodec.h, 1.464, 1.465
Guillaume POIRIER
docmaintainerwannabe
Sun May 7 21:59:14 CEST 2006
- Previous message: [Ffmpeg-cvslog] CVS: ffmpeg/libavcodec motion_est_template.c, 1.29, 1.30 utils.c, 1.179, 1.180 avcodec.h, 1.464, 1.465
- Next message: [Ffmpeg-cvslog] CVS: ffmpeg/libavcodec motion_est_template.c, 1.29, 1.30 utils.c, 1.179, 1.180 avcodec.h, 1.464, 1.465
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Hi,
Michael Niedermayer CVS a ?crit :
>Update of /cvsroot/ffmpeg/ffmpeg/libavcodec
>In directory mail:/var2/tmp/cvs-serv10138
>
>Modified Files:
> motion_est_template.c utils.c avcodec.h
>Log Message:
>make zero motion vector threshold user setable
>
>
Could you give us, poor mortals, some more information about this new
option? What happens if you lower/raise it? Why would you want to tune
it (what kind of material, ...)
>+
>+ /**
>+ *
>+ * note: value depends upon the compare functin used for fullpel ME
>+ * - encoding: set by user.
>+ * - decoding: unused
>+ */
>+ int mv0_threshold;
> } AVCodecContext;
>
Somehow, It would be quite cool if MEncoder could use FFmpeg's option
parser, so we wouldn't need to update MEncoder each time we want to take
advantage of lavc's new options.
What would it take to do that?
Guillaume
- Previous message: [Ffmpeg-cvslog] CVS: ffmpeg/libavcodec motion_est_template.c, 1.29, 1.30 utils.c, 1.179, 1.180 avcodec.h, 1.464, 1.465
- Next message: [Ffmpeg-cvslog] CVS: ffmpeg/libavcodec motion_est_template.c, 1.29, 1.30 utils.c, 1.179, 1.180 avcodec.h, 1.464, 1.465
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the ffmpeg-cvslog
mailing list