[FFmpeg-devel] [PATCH] libvpx: alt reference frame / lag

Reimar Döffinger Reimar.Doeffinger
Tue Jun 15 20:51:38 CEST 2010

On Tue, Jun 15, 2010 at 12:18:29PM -0400, John Koleszar wrote:
> The encoder doesn't and shouldn't know what the user is going to do
> with the data. People can and have defined their own transports.
> Framing aside, I don't think it makes sense to combine the two packets
> because they can be semantically different. One of the two could be
> droppable, for example. Many applications want to treat these packets
> independently (consider streaming, video conferencing). One example
> might be to apply different error correction to the two packets.

Could maybe someone explain what exactly this is about?
You seem to be talking about two packets with the same time stamp that
a decoder might want to decode differently for each?
That makes no sense to me, if the have the same time stamp, they are
supposed to be displayed at the same time, which makes no sense and the
decoder really should output only one of them...

More information about the ffmpeg-devel mailing list