[MPlayer-dev-eng] The NUT backward pointers

[D Richard Felker III]

On Mon, Apr 12, 2004 at 06:52:29PM +0200, Moritz Bunkus wrote:
> Hi,
> 
> > Nut files absolutely MUST NOT contain non-monotone timestamps.
> 
> Ah, that's my clue for a question I've maent to ask for some time
> now. How will B frames be stored in nut? Same as in AVI (packed
> bitstream)? Non packed? If non packed, in coding or display order? How
> will they be timestamped? I'm experimenting with non-packed bitstream,
> coding order in Matroska, but mplayer is not too happy about the
> timestamps I hand it, and unless nut just stores a packed bitstream with
> dummy frames then it'll have some problems as well (mplayer specific,
> not due to the file format).

Sorry, I wasn't being clear. Of course B frames are stored in coded
order with correct timestamps on each, which means the timestamps are
"non-monotone". But the monotonicity rule can only be violated for
out-of-order decoding, nothing else.

The packing like in AVI is absolutely forbidden. Each NUT packet must
containe EXACTLY ONE coded frame, whether audio or video. Putting
multiple frames in a single container packet is not allowed.

BTW, Michael, do we need an "out of order" flag for frames? Or
something like that?

Rich


P.S. I HATE B FRAMES