[FFmpeg-devel] [RFC] Lavfi test system

[Jai Menon]

On Sun, Jan 10, 2010 at 4:49 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Sun, Jan 10, 2010 at 12:08:30PM +0530, Jai Menon wrote:
>> On Sun, Jan 10, 2010 at 5:36 AM, Stefano Sabatini
>> <stefano.sabatini-lala at poste.it> wrote:
>> > On date Saturday 2010-01-09 15:43:34 +0100, Michael Niedermayer encoded:
>> >> On Sat, Jan 09, 2010 at 02:58:30PM +0100, Stefano Sabatini wrote:
>> >> > On date Friday 2010-01-08 03:48:37 +0100, Michael Niedermayer encoded:
>> >> > > also dont use avi as output but something that supports timestamps so
>> >> > > they are tested as well (filters may change them)
>> >> >
>> >> > Both avi and nut fail with some of the pixel formats supported, maybe
>> >> > I'll be more lucky with mp4/mov.
>> >> >
>> >> > But I want to know if there is some way to fix them, for example for
>> >> > AVI there doesn't seem to be fourCC tags for some of the pixel formats
>> >> > we support, the same for NUT (we can maybe fix the latter extending
>> >> > its specs), anyway I believe we should fail if some pixel format is
>> >> > not supported during encoding.
>> >> >
>> >> > Any thought?
>> >>
>> >> read fourcc.org or M$ specs
>> >
>> > Ah, funny that I have to read a third party site for something related
>> > to a M$ standard. This reminds me of why computer tech sucks so much.
>> >
>> >> read nut4cc.txt
>> >
>> > From the mplayer/DOCS/tech/nut.txt
>> >
>> > |the nut spec has been moved to another svn repo you can find it at:
>> > |http://svn.mplayerhq.hu/nut/docs/nut.txt?view=markup
>> > |
>> > |its future location will be in a git repository, ill update this file
>> > |here when its location changes again
>> >
>> > The referenced page is missing.
>> >
>> > Then I tried:
>> > http://nut-container.org/
>> >
>> > The link to the specification leads nowhere.
>> >
>> > I googled in search of some reference to the nut repo in vain.
>> >
>> > Then I tried:
>> > svn list svn://svn.mplayerhq.hu/nut
>> >
>> > and finally I got the repo.
>> >
>> > Please fix the dangling links.
>>
>> The links are valid, just that websvn isn't available anymore.
>> Might I suggest pushing it to github/gitorious etc, it would be useful
>> if people could view the documentation without having to create a
>> checkout.
>
> or someone could just make a cronjob that does
> svn up and put that on a public http accessable directory

Sure that works too. The publically hosted git repo could be done by
anyone. This however requires root at mphq's help :)

-- 
Jai Menon