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 mpg1 ISO MPEG1 Video mpg2 ISO MPEG2 Video MRLE MS RLE @@ -93,4 +94,4 @@ P<type><interleaving><bits> little endia PFD[32] would for example be signed 32 bit little endian IEEE float -FIXME mpeg4/dv/gray16/audio codecs/multi chan interleaving +FIXME dv/gray16/audio codecs/multi chan interleaving
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. BTW this document should explicitly mention that DIVX, DIV3, DIV4, DX50, 3IVX, XVID, etc. are reserved fourcc values and invalid. :) Rich
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
On Wed, Feb 13, 2008 at 01:03:53PM +0100, Michael Niedermayer wrote:
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 ...
OK, sounds good then.
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).
Then let's specify them specifically as meaning broken pseudo-mpeg4 streams. This will discourage their use for correct data. Rich
participants (3)
-
michael -
Michael Niedermayer -
Rich Felker