[NUT-devel] [nut]: r614 - docs/nut4cc.txt

[Michael Niedermayer]

On Wed, Feb 13, 2008 at 12:51:01AM -0500, Rich Felker wrote:
> On Tue, Feb 12, 2008 at 04:30:56PM +0100, michael wrote:
> > Author: michael
> > Date: Tue Feb 12 16:30:55 2008
> > New Revision: 614
> > 
> > Log:
> > Choose a 4cc for mpeg4.
> > Bikeshed flames welcome
> > 
> > 
> > Modified:
> >    docs/nut4cc.txt
> > 
> > Modified: docs/nut4cc.txt
> > ==============================================================================
> > --- docs/nut4cc.txt	(original)
> > +++ docs/nut4cc.txt	Tue Feb 12 16:30:55 2008
> > @@ -32,6 +32,7 @@ MJPG    ITU JPEG
> >  MPG4    MS MPEG4v1 (!NOT ISO MPEG4!)
> >  MP42    MS MPEG4v2
> >  MP43    MS MPEG4v3
> > +MP4V    ISO MPEG4 Video
> 
> Would using MP4S present any problems? I know MS used this at one
> point in AVI but I'm unclear on whether it referred to a restricted
> profile or full MPEG-4 ASP. If it's acceptable it would be one less
> difference from AVI.

mp4v and MP4V are listed at http://www.fourcc.org/codecs.php
mp4s is listed with "The first ISO standard codec for use with the Sharp 
digital camera implementing a restricted feature set of MPEG4."
so it somehow feels at least as bad ...


> 
> BTW this document should explicitly mention that DIVX, DIV3, DIV4,
> DX50, 3IVX, XVID, etc. are reserved fourcc values and invalid. :)

We need the fourcc from these to workaround bugs in old implementations
they could surely use mp4v or whatever standard fourcc we choose for their
current generated (MPEG4) content. But not for old (HALF MPEG4).

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Opposition brings concord. Out of discord comes the fairest harmony.
-- Heraclitus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/nut-devel/attachments/20080213/011a48cb/attachment.pgp>