[Ffmpeg-cvslog] r6963 - trunk/libavformat/riff.c

[Michael Niedermayer]

Hi

On Sun, Nov 12, 2006 at 06:33:59PM +0200, Oded Shimon wrote:
> On Sun, Nov 12, 2006 at 05:31:49PM +0100, Diego Biurrun wrote:
> > On Sun, Nov 12, 2006 at 05:22:11PM +0200, Oded Shimon wrote:
> > > On Sat, Nov 11, 2006 at 03:08:40AM +0100, Michael Niedermayer wrote:
> > > > 
> > > > On Sat, Nov 11, 2006 at 01:22:08AM +0000, M?ns Rullg?rd wrote:
> > > > > michael <subversion at mplayerhq.hu> writes:
> > > > > 
> > > > > > Log:
> > > > > > libnut uses "MP3 " for mp3
> > > > > >
> > > > > > Modified: trunk/libavformat/riff.c
> > > > > > ==============================================================================
> > > > > > --- trunk/libavformat/riff.c	(original)
> > > > > > +++ trunk/libavformat/riff.c	Sat Nov 11 01:29:49 2006
> > > > > > @@ -200,6 +200,7 @@
> > > > > >      // for NuppelVideo (nuv.c)
> > > > > >      { CODEC_ID_PCM_S16LE, MKTAG('R', 'A', 'W', 'A') },
> > > > > >      { CODEC_ID_MP3, MKTAG('L', 'A', 'M', 'E') },
> > > > > > +    { CODEC_ID_MP3, MKTAG('M', 'P', '3', ' ') },
> > > > > 
> > > > > Nooooo.  We were trying to get rid of those invalid bogus tags from
> > > > > riff.c.  Don't add more of them.
> > > > 
> > > > nut per spec uses the avi-riff tags to identify codecs, libnut uses
> > > > "MP3 " ...
> > > > ask oded why
> > > 
> > > I actually don't know myself. Ask Rich, he told me to do it. :/ BTW, I use 
> > > "mp3 " (no caps).
> > 
> > Fix libnut then?  And I agree that this is confusing.  Does NUT use the
> > same identifiers as AVI, 0x55 then, or not?
> 
> It used to be 0x55 .
> 
> 21:02:41 <dalias> if he comes back mention that twocc is not allowed
> 21:02:56 <dalias> all nut ids must be alphabetic (case?)
> 21:03:23 <@ods15> really?
> 21:03:35 <@ods15> cause currently i use \x00\x55 for mp3...
> 21:03:57 <dalias> mp3 has always been "mp3 "
> 21:04:31 <@ods15> heh, i (and nutmerge) didn't know...
> 21:04:51 <dalias> ok fix nutmerge soon :)
> 
> 
> When he told me that I figured I just missed some decision that was agreed 
> upon during the 

hmm i do remember some short list of "sane" ids and codecs to be posted, i
think noone really objected to it but
1. the spec says avi-riff
2. noone is willing to maintain a codec_tag mapping table which has a similar
   size as what avi does support
3. 0x0055 is just a number like 1 is one in mpeg, i see no advantage in using
   'm' + ('p'<<8) + ('3'<<16) ...


> very long and boring fourcc flamewar which i didn't bother 
> reading carefully.

fully agree, iam sick of this "a number called fourcc is worse then a number
used in mpeg-ps" thing

[...]
-- 
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