[FFmpeg-devel] [PATCH] probetest.c

Kostya kostya.shishkov
Tue Sep 15 20:04:22 CEST 2009

On Tue, Sep 15, 2009 at 07:39:59PM +0200, Vitor Sessak wrote:
> Michael Niedermayer wrote:
>> On Mon, Sep 14, 2009 at 05:19:03PM +0200, Michael Niedermayer wrote:
>>> Some simple probe testing code should be attached
>>> its output, aka formats that detect random data with a score >25 are:
>>> Failure of h261 probing code with score=50 type=0 p=B53 size=2
>>> Failure of vc1test probing code with score=50 type=0 p=40E size=4
>>> Failure of h263 probing code with score=50 type=0 p=C1E size=4
>>> Failure of idcin probing code with score=50 type=0 p=E93 size=8
>>> Failure of mm probing code with score=50 type=0 p=FC0 size=128
>>> Failure of dv probing code with score=75 type=1 p=E85 size=256
>>> Failure of vmd probing code with score=50 type=0 p=AF4 size=512
>>> Failure of mpeg probing code with score=52 type=0 p=D9C size=4096
>>> Failure of dts probing code with score=51 type=1 p=B8F size=8192
>>> maintainers of the listed formats should look into fixing their probe
>>> code!
>>> ill try to look at h26*/mpeg if i find the time, that said if someone
>>> else is faster thats welcome of course ...
>> and as everyone celebrates victory, probetest returns from the depths of
>> hell stronger and more evil to devour more demuxers
>> heres the output up to 32k
> [...]
>> Failure of mpc8 probing code with score=100 type=3 p=85A size=64

May I say that it would fail in many cases since any string of uppercase
letters starting with 'MPCK' can be parsed as valid Moosepack SV8 file
with strange but valid tags?

More information about the ffmpeg-devel mailing list