<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">Le 25 janv. 2015 à 04:43, Marcus Johnson <<a href="mailto:bumblebritches57@gmail.com" class="">bumblebritches57@gmail.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-size:large">I'm new and don't know too much about the API, but honestly seeking is the biggest issue I think we can all agree upon, I can't implement certain features because we just can't seek properly</div><div class="gmail_default" style="font-size:large"><br class=""></div><div class="gmail_default" style="font-size:large">I'm not sure how we could rectify this but there has to be something that could be done.</div></div>
_______________________________________________<br class="">Libav-user mailing list<br class=""><a href="mailto:Libav-user@ffmpeg.org" class="">Libav-user@ffmpeg.org</a><br class="">http://ffmpeg.org/mailman/listinfo/libav-user<br class=""></div></blockquote></div><br class=""><div class="">I suppose this is not too off-topic and could help at designing the high level API: what exactly is currently wrong with seeking in FFmpeg? Are there use cases that just don't work? I'm asking because I got it working for a personal project and for all the file formats I've tested it works just fine. I admit it was a bit tricky to implement though, but after understanding how the demuxer and streams work (I mean in general, not FFmpeg specific) it just makes sense.</div><div class=""><br class=""></div><div class="">Lucas</div></body></html>