[MPlayer-cvslog] CVS: main/DOCS/tech mpcf.txt,1.67,1.68

Michael Niedermayer michaelni at gmx.at
Sat Mar 5 00:29:08 CET 2005


On Friday 04 March 2005 21:39, D Richard Felker III wrote:
> > so we should IMHO
> > * require players to warn the user about detected damages (players not
> > doing this would not be compliant to the nut spec)
> "Warning the user" is fairly vague; hard to determine if the player is
> compliant or not. What if the player is an embedded device with no
> message display? 

it has a display for the video, it can display a tiny icon like the https 
icons of browsers, this of course can be disabled by the user

> Or what if the user specifies -quiet/-silent? Do 
> these violate the spec? :)


> > maybe we should just drop the index mess and return to a single index at
> > the end, it would be so much simpler for the muxer and demuxer and damage
> > to the index could be detected very quickly while still allowing (slow)
> > seeking in damaged files
> > rich whats your oppinion about that?
> I like it a lot. But I still think we need a good way for dealing with
> excessive numbers of keyframes, e.g. audio, while still seeking to the
> nearest keyframe (including all keyframes). This is orthogonal from
> what we've been talking about but I'd still like to know if you have a
> clean solution for it.

see max_index_distance, it was always there, you didnt like it IIRC, but i 
dunno why


"nothing is evil in the beginning. Even Sauron was not so." -- Elrond

More information about the MPlayer-cvslog mailing list