On Mon, Oct 21, 2013 at 12:13 PM, Carl Eugen Hoyos <ceho...@ag.or.at> wrote: > Robert Krüger <krueger@...> writes: > >> In case of the files I am talking about here, there are no recovery >> point SEIs after the first frame so libavformat/avcodec is probably >> doing everything correctly, too. Since I think I know that these >> streams in fact do have random access points, I will probably have to >> parse the h264 metadata myself and apply some heuristics in my >> application but filing a ticket does not seem to make sense as it does >> not appear to be a defect and I don't think anyone would have an >> interest to work on such heuristics or further investigation, how >> random access points can be found in such a stream (if they exist, >> which I have yet to prove). > > I don't know how you come to the conclusion that (both > library and application) users wouldn't want the > heuristic (last week something probably related was > committed).
Even better. Which commit are you talking about? > Please provide the sample, Carl Eugen I'll be more than happy to do that. How do you want me to do it? Open a ticket (if so, what would be an appropriate topic/title in your opinion?) or by some other means? > > _______________________________________________ > Libav-user mailing list > Libav-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/libav-user _______________________________________________ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user