[NUT-devel] r19110 - trunk/DOCS/tech/nut.txt

[Oded Shimon]

On Mon, Jul 17, 2006 at 10:39:08PM +0300, Ivan Kalvachev wrote:
> 2006/7/17, Rich Felker <dalias at aerifal.cx>:
> >On Sun, Jul 16, 2006 at 03:43:11PM +0300, Ivan Kalvachev wrote:
> >> >> Could we perhaps generalize that format to include all codecs with
> >> >> several chunks of extradata, not only ogg based codecs?  I'm not aware
> >> >> of any others, but for all I know they might exist.
> >> >
> >> >ok, but the following needs disscussion:
> >> >A always choose ogg style lacing
> >> >B always choose v + packet data (nut style)
> >> >C use whatever matroska uses + one of the above for the cases not
> >> >supported by
> >> >matroska
> >>
> >> I don't think there is place for discussion. Always use nut style.
> >
> >No, read my post about the intent...
> >The demuxer has nothing to do with parsing this information. It's part
> >of the codec layer. If it were part of the demuxer layer, we would
> 
> If that was true then what is this commit doing in nut.txt?
[..]
> 
> Michael,
> You say that if somebody objects you will revert this. I don't think
> that agreement would need 22 mails in comments.
> So please revert and get it back to drawing board.

I say just revert but make a codec documents giving details about several 
codecs in nut where the wrapping isn't obvious (like vorbis).

Ivan, vorbis doesn't expect 3 extradata according to the spec, it expect 
the first 3 audio packet to be the headers. I think this is insane enough 
that it allows us to break their spec instead of ours.

- ods15