Author: victor Date: Sat Dec 22 12:31:34 2007 New Revision: 1640 Log: Clarify libavfilter's direction, as per discussion in issue 302 in bug tracker.
Modified: libavfilter/README Modified: libavfilter/README ============================================================================== --- libavfilter/README (original) +++ libavfilter/README Sat Dec 22 12:31:34 2007 @@ -16,6 +16,33 @@ WRITING FILTERS: There is some documentation on writing basic filters over at the multimedia wiki. See http://wiki.multimedia.cx/index.php?title=FFmpeg_filter_howto +THE RIGTH DEVELOPMENT DIRECTION: + +libavfilter IS a graphics library; therefore for: + +- drawing text + Create a single drawtext filter using freetype +- supporting filters from libmpcodecs + Create a single filter that links to libmpcodecs +- supporting filters from gimp + Create a a single filter that links to it +- reading images + Create a filter using libavcodec +- blending two things + Create a single filter doing the blending using C + +And for the rest use ANSI C. + +THE WRONG DIRECTION: + +libavfilter IS NOT a wraper around another graphics library. +Its libavfilter's job to work with pixels; it IS NOT its job to call +a random_lib(). That would be the last resort if all else fails. + +And in that remote case, there must be a need, a specific thing we +are not able to do easily with a few lines of ANSI C: something like +using libfreetype to render text. + RUNNING IT: The command line syntax for specifying filters is similar to that of mplayer. _______________________________________________ FFmpeg-soc mailing list [email protected] http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc
