[FFmpeg-devel] [PATCH] Add libavsequencer.
Ronald S. Bultje
Wed Aug 25 18:22:03 CEST 2010
On Wed, Aug 25, 2010 at 12:21 PM, Ronald S. Bultje <rsbultje at gmail.com> wrote:
> On Wed, Aug 25, 2010 at 12:15 PM, Sebastian Vater
> <cdgs.basty at googlemail.com> wrote:
>> Ronald S. Bultje a ?crit :
>>> 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/).
>> 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).
>> We either should use then a lower sample rate (4kHz output should be
>> enough for a fate test), or we use mp3 64kbit/s as output codec.
> You're getting good at this. :-). I don't think you need 3 minutes,
> that samplerate is indeed high also.
Oh, and mp3 is not a great idea, we want to keep tests minimal and fast.
More information about the ffmpeg-devel