[FFmpeg-devel] [PATCH] Add libavsequencer.

Vitor Sessak vitor1001
Wed Aug 25 18:35:39 CEST 2010


Sebastian Vater wrote:
> Ronald S. Bultje a ?crit :
>> Hi,
>>
>> On Wed, Aug 25, 2010 at 8:36 AM, Sebastian Vater
>> <cdgs.basty at googlemail.com> wrote:
>>   
>>> My plan to implement the tests is, that I write, while playback &
>>> mixing, to a text file containing the internal dump of the player / BSS
>>> / mixer structures. This has to be done twice, one for original
>>> TuComposer, and one for AVSequencer.
>>>     
>> Why not just compare the PCM output? If they are identical for a bunch
>> of files, likely the mixer works the same as before. This is how all
>> FFmpeg regtests works (http://fate.ffmpeg.org/).

I suggest you also add a few FATE tests to your local tree, it is very 
handy to know if your own changes are not breaking things.

> My plan here was to take all IFF-TCM1 files I have for the test, whose
> number is around 1000, let's say for an average duration of 3 mins as
> 32-bit 44,1kHz stereo samples, we would have a total duration around
> 3000 minutes, which is around 50 hours of total playback time. Storing
> such a huge amount requires lots of HDD space (1211 MB for 60 minutes).

Or you could just store the MD5 of the output stereo data and see which 
of them match the MD5 of the TUComposer output (supposing everything is 
integer-only). Then, for those who differ, you check in more detail what 
is happening.

-Vitor



More information about the ffmpeg-devel mailing list