[MPlayer-dev-eng] [PATCH] playback timing

[Pásztor Szilárd]

Reimar Döffinger:
> This most likely wrong and will play wrong (i.e. too fast speed) any files
> with damaged frames and possibly completely break AVI files with 0-size
> frames.
> Without being able to distinguish which case this is (a damaged frame,
> a frame that does not contain any changed data but should be displayed
> for some time, or incomplete data as the first field for PAFF is) this
> is unlikely to be possible to fix _correctly_.

You are basically right in every point but I still disagree.
It's far far more common to have healthy but incomplete frames returned for
the first field than to have broken files.
And there's one thing to consider. What is more important, being able to play
damaged files as nicely as possible while being unable to play practically
all available and healthy interlaced h264 streams, or the other way around?

If it were to vote, I'd go for the second option.
But, then again, you are right in knowing that this is more like a workaround
than a 100% correct fix. The best solution would be to convince h264 decoders
not to return with incomplete frames (first fields) at all.
Any hints on how to leook for that?

s.

  ----------------------------------------------------------------------------
  |  Hard work often pays off after time, but laziness always pays off now.  |
  ----------------------------------------------------------------------------