On 9/26/15, Moritz Barsnick <barsn...@gmx.net> wrote: > On Sat, Sep 26, 2015 at 10:29:15 +0200, Paul B Mahol wrote: > >> +Merge first input stream with second input stream using per pixel weights >> in >> +the third input stream. 0 means that pixel component from first stream is >> +returned unchanged while 255 for 8-bit videos means that pixel component >> from >> +second stream is returned unchanged. > >> +Merge first input stream with second input stream using per pixel weights >> in >> +the third input stream. > > Merge the first input stream with the second input stream using per > pixel weights in the third input stream. > > (I'm not keen on omitting all those "the"s, though it would work in > this sentence.) > >> 0 means that pixel component from first stream is returned unchanged >> while 255 for 8-bit videos means that pixel component from second >> stream is returned unchanged. > > A value of 0 in the third stream means that the pixel component from > the first stream is returned unchanged, while the maximum value (e.g. > 255 for 8-bit videos) means that the pixel component from the second > stream is returned unchanged. Intermediate values define the amount of > merging between both input streams' pixels. > >> +This filter accepts the following options: >> +@table @option >> +@item planes >> +Set which planes will be processed as bitmap, unprocessed planes will be >> +copied from first stream. >> +By default all planes will be processed. >> +@end table > > Syntax, values? I assume like "extractplanes"'s "planes" option, right? >
Nope, its bitmask, 0 - return first stream unchanged, 1 process only first plane, 2 process only second plane, 3 process 1st and 2nd plane and so on... > Cheers, > Moritz > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
