[MPlayer-cvslog] r19258 - trunk/DOCS/tech/oggless-xiph-codecs.txt

[Michael Niedermayer]

Hi

On Sun, Jul 30, 2006 at 02:40:51PM +0200, Alex Beregszaszi wrote:
> Hi,
> 
> > > > dont know now what the differences beween your text and mine are
> > > > so i feel a little uneasy with working with your text, i hope you
> > > > wont mind if i keep working on mine
> > > 
> > > Better if you rethink this after looking at the latest one.
> >
> > ive no interrest to work on your xml conversation of my document!
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> > why on earth should i?!
> 
> uhm. Maybe an RFC document gives more technical background the proposal?
> We want the way to be widespread. As an RFC it has a reputation, its not
> just "a document on mplayerhq" or like that.
> 
> You dont want to have this as an RFC?

read what i wrote!

furthermore, before this can become an RFC / be proposed to IETF or
whatever the process is  ... it needs to be more mature and your way
of droping random comments from posts on nut-devel into it is not
making it more mature but less
first you added some completly nonsense way of storing a global header
in .mov, baptiste (who knows the mov & mp4 specs) explained how vorbis
global headers could/should be stored and you simply copy and pasted that,
of course the mp4 way only applied to audio codecs, even i noticed that
though my knowledge of the mov/mp4 container spec is far from perfect so i
didnt dare at first to add them to the spec ...


so if you are not willing to read and understand the mp4/mov specs (a few days
boring work, so i fully understand if you wont read them, after all i neither
plan to read them) then please dont attempt to write a specification on how to 
store something in one of these containers, the result would not help anyone
and would never be accepted as a RFC
writing a specification is not a "dump random ideas into a text file" thing
everything has to be carefully disscussed, thought through and checked against
the relevant container specs

you probably also expect ISO/ITU/... to carefully consider everything when
writing their specs ...

[...]

-- 
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