[FFmpeg-devel] [PATCH] lavfi: port mp test source

Stefano Sabatini stefano.sabatini-lala at poste.it
Thu Aug 11 16:44:50 CEST 2011


On date Wednesday 2011-08-10 02:19:55 +0200, Stefano Sabatini encoded:
> On date Wednesday 2011-08-10 00:42:06 +0200, Michael Niedermayer encoded:
> > On Wed, Aug 10, 2011 at 12:28:17AM +0200, Stefano Sabatini wrote:
> > > On date Tuesday 2011-08-09 21:51:50 +0200, Michael Niedermayer encoded:
> > > > On Tue, Aug 09, 2011 at 08:59:53PM +0200, Stefano Sabatini wrote:
> > > > > On date Tuesday 2011-08-09 16:09:47 +0200, Michael Niedermayer encoded:
> > > > > > On Mon, Aug 08, 2011 at 02:43:15PM +0200, Stefano Sabatini wrote:
> > > > > > > ---
> > > > > > >  doc/filters.texi             |   57 ++++++
> > > > > > >  libavfilter/Makefile         |    1 +
> > > > > > >  libavfilter/allfilters.c     |    1 +
> > > > > > >  libavfilter/vsrc_mptestsrc.c |  392 ++++++++++++++++++++++++++++++++++++++++++
> > > > > > >  4 files changed, 451 insertions(+), 0 deletions(-)
> > > > > > >  create mode 100644 libavfilter/vsrc_mptestsrc.c
> > > > > > 
> > > > > > if it produces same output
> > > > > > then ok
> > > > > 
> > > > > After some comparation with showinfo, I had to change M_PI in my code
> > > > > with 3.141592654, at this point they issue the same output but with
> > > > > some behavior difference, for mp=test frames with number frame%30 are
> > > > > skipped, with mptestsrc they are not (which looks more correct).
> > > > 
> > > > the filter was used to reverse engeneer 8x8 dct based codecs and the
> > > > all black frames can be used to quickly spot where the different
> > > > parts of the test patterns start
> > > 
> > > I used showinfo for that ;-). Anyway how should look the sequence?
> > > 
> > > How about
> > > TEST1 TEST1 ... TEST1 BLACK TEST2 ... TEST2 BLACK ...
> > > ?
> > > 
> > 
> > LGTM
> 
> SLightly different, it is now:
> BLACK TEST1 TEST1 ... TEST1 BLACK TEST2 ... TEST2 BLACK ...
> 
> as in the original code, slightly simpler.
> 
> > > Consider also that I'm adding the possibility to run separately each
> > > single test, in that case having a separation frame is pointless.
> > 
> > the way the filter was used was to create a test video that was then
> > encoded with a closed source encoder that worked only on a different
> > platform and the resulting bitstream analyzed.
> > 
> > seperate files and fighting with a shitty GUI to encode them X times
> > is more work than a single video with black frames.
> > 
> > Anyway this filter is probably largely of historic value so it doesnt
> > matter much.
> 
> I thought it was useful for testing encoding features/performace
> (e.g. compression ratio for each kind of test), anyway it's better to
> have it native rather than as a wrapper. I'll try to focus on a more
> useful filter the next time ;-).
> 
> Relicensed as LGPL.

Applied with GPL license.
-- 
FFmpeg = Fancy and Frenzy Mind-dumbing Programmable Explosive Geisha


More information about the ffmpeg-devel mailing list