I have seen this update but it also still uses both a custom get_buffer (the tut was updated to use get_buffer2) and a custom release_buffer.
My custom get_buffer is called but the release_buffer is not. Thus, I'm allocating memory I can't free (or at least I wouldn't know where the best place would be). Stephen Dranger wrote that there are certain circumstances where the pts is not correct and thus he introduced this get/release buffer workaround to always retrieve a correct pts. Can anyone tell me if this is still required? I'd just like to be sure to always get the correct pts. Thanks! > On 28.03.2014, at 00:04, Lou <[email protected]> wrote: > > On Thu, 27 Mar 2014 22:37:35 +0100 > Info || Non-Lethal Applications <[email protected]> > wrote: > >> I’m fairly new to ffmpeg. Thus, I worked through the excellent tutorials of >> Stephen Dranger. > > An updated version of that tutorial is: > https://github.com/chelyaev/ffmpeg-tutorial > _______________________________________________ > 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
