[MPlayer-cvslog] r20765 - in trunk/libmpdemux: demuxer.c demuxer.h

[Uoti Urpala]

On Wed, 2006-11-08 at 23:39 +0100, Nico Sabbi wrote:
> Uoti Urpala wrote:
> > or if the value is not suitable for pts use then 2) it should
> >be placed in another field associated with the demuxed packets.

> why there should be a link between demux packets (demux-stream specific)
> and playtime (mux/stream specific) ?
> Don't forget that this function is intended to show on the OSD the value 
> of the current
> playtime, not to be used as a central synchronization clock

Because the only link between stream playtime and what's shown on screen
is through the demux packets. There could be an arbitrary amount of
buffering in between. For example when filling the audio buffer ahead an
arbitrary number of future packets can be demuxed. So what is being
displayed on screen now and what the demuxer is demuxing now need not be
closely related; thus it's wrong to ask the demuxer or stream layer at
display time what they're demuxing at that moment.

If you want to have another time value for OSD in addition to the
current pts values then IMO it should be handled the same way as pts:
"attached" to particular frames when the demuxer creates packets.