Hello. Hello. Yes, I have switched to the most recent version, of course. I would prefer the latest. But the result is exactly the same. I am not working with files. My app captures screenshots, encodes it, sends over the network, decodes it, and shows on another PC. So I am totally contained in my own app. So what was working very well stopped working. Well, not stopped, but that huge latency give me about 5-6 seconds of delay. So it is like 40 - 50 frames in my app. Also I have seen, that it is encoder functions which is the problem. Thank you for your response.
On Wed, Jul 18, 2012 at 3:42 PM, Alexandre Millette <[email protected]> wrote: > Hi. > >> switching from avcodec-52.dll to avcodec-53.dll >> > > > It probably won't solve the issue, but maybe you could try using > avcodec-54.dll since it's the latest release? Or is there a reason why you > need the older one? > > >> >> It outputs any data after like more than 100 >> frames fed. And before that it was only 1 frame. > > > The same video that could be played with 1 frame latency now has a 100+ > frames latency? > Have you tried other h264 files? Other formats? > If it's specific to a file or to a set of files coming form the same > encoder, maybe it's because of a header value that isn't standard: I would > then recommend checking the patch notes between the 2 releases to know what > could have changed. > > Also, are all the frames returned, simply really late? I'm wondering if > you're maybe missing a lot of frames and it isn't a latency issue at all. > > Hope it helps a bit, > Alex M > _______________________________________________ > Libav-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/libav-user _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
