On Aug 14, 2009, at 12:11 PM, Chris wrote:

2009/8/13 Adam Dershowitz <[email protected]>:
Any suggestions would be appreciated. For example is there any way to force it to attempt to do real time decoding? Or to flush out the buffer after each read so that the next decode would get the next frame that came in?

I'm not fully qualified to answer but I'll have a go at making a
couple of suggestions!

Firstly you need to be careful because you can't throw away random
p-frames because each p-frame could refer to the next one (or more
than one I think). If you show a p-frame, then miss one, then display
the next one, you'll get errors from ffmpeg and the video will almost
certainly distort  You can only throw frames away if you are prepared
to wait until the next IDR frame comes since an IDR frame is a full
picture (again *I think!*) and it doesn't refer to any other frames.

Thanks for the information.
I am hoping that there is some way that the decoder might be able to help out some. I have been looking at the ffmpeg code, and specifically looking at the -re option. But, it seem that it is only able to slow things down, by sleeping between frames. That option doesn't speed things up by throwing away, or at least not fully decoding, images or frames.

It seems like I should be able to just decode enough to figure out the next image and go to that, without spending all those cycles decoding an image that is already minutes behind "real time".

Again,

thanks,

--Adam
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user

Reply via email to