[NUT-devel] [PATCH] fourcc spec

[Ivan Kalvachev]

2006/4/18, Michael Niedermayer <michaelni at gmx.at>:
> Hi
>
> On Sat, Apr 15, 2006 at 05:30:38PM -0400, Rich Felker wrote:
> [...]
> > > and may i suggest to do mpeg audio/video more consistant?
> > >
> > > mpegX      video "MXV",0 (M1V,M2V,M4V)
> > > AC3     "AC3",0
> > > H26X    "H26X"
> >
> > Looks good. What about h263+? :)
>
> i feared such a question, as it requres us to decide about where to
> draw the line for profiles, later versions of a codec and so on
> what about 4:2:2 mpeg2?
>
>
> >
> > > mp3     "MP3",0
> >
> > And "MP2",0 "MP1",0 ...?
>
> and what about mpeg1-mp3 vs. mpeg2-mp3 IIRC there are a few differences
>
>
> >
> > > and a generic suggestion that the file extension should be used as
> > > fourcc if theres a well known filename extension for the elementary
> > > stream
> > > and generic suggestion 2 if theres a well known avi fourcc then that
> > > should be used
> >
> > These seem reasonable.
> > Can we clarify that the "well known avi fourcc" should refer to the
> > compression format and not a specific implementation name or marketing
> > crap?
>
> yes
>
> [...]

I though we are going to ommit FourCC definition on purpose.
We are either going to follow avi/MS fourcc, or follow the path of
matroska - defining our own completely ridiculous reinventions.

How about defining an syntax or allowing inclusion of as many aliases
as possible?
e.g.

"ISO14496-2;MPEG-4;XviD;XVID;xvid;DX50;DIVX;FM40"

This for sure will guarantee that any player could recognize the format :)

we could add and more additional info in brakets. E.g.
{XviD,XVID,xvid}(bs=130,ver=1.1.0).