[NUT-devel] Re: r19110 - trunk/DOCS/tech/nut.txt
Michael Niedermayer
michaelni at gmx.at
Mon Jul 17 01:39:18 CEST 2006
Hi
On Mon, Jul 17, 2006 at 12:58:47AM +0200, Baptiste Coudurier wrote:
> Hi
>
> Michael Niedermayer wrote:
> > Hi
> >
> > On Sun, Jul 16, 2006 at 05:52:25PM -0400, Rich Felker wrote:
> > [...]
> >>> then there are some mov based codecs like qdm2 which maybe need several
> >>> chunks, they currently simply copy a whole set of mov chunks blindly
> >>> into extradata in ffmpeg, that of course is a terrible mess which
> >>> someone should fix in ffmpeg ...
> >> Any good ideas? If the mov atoms aren't hard to parse I wonder if
> >> original Qt codecs should just be allowed to keep their mov atoms...
> >
> > hmm, ive no strong objections here ...
> >
> > iam also thinking that maybe we should simply ignore these closed
> > propriatary mov based codecs, i really doubt anyone will want to
> > store them in nut ever anyway ...
> >
> > [...]
> >
>
> What do you mean "proprietary" mov ? Consider that now mov/isom/mp4/3gp
> is ISO file format reference.
propriatary mov based _codecs_, stuff where you need to sign an NDA or
worse to see the specs (SVQ3/...)
>
> Im thinking of jpeg 2000 extradata, that has a chance to be in NUT some
> day,
jpeg 2000 has extradata? its a image based (=intra only) codec it shouldnt
have much extradata ...
> same for qclp (3g2 audio codec)
i cant comment on a codec for which i have no specs or source code
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is
More information about the NUT-devel
mailing list