On Thu, Nov 24, 2016 at 1:56 AM, wm4 <nfx...@googlemail.com> wrote: > On Wed, 23 Nov 2016 11:40:25 -0800 > Wan-Teh Chang <wtc-at-google....@ffmpeg.org> wrote: > >> On Tue, Nov 22, 2016 at 3:30 PM, wm4 <nfx...@googlemail.com> wrote: >> > On Tue, 22 Nov 2016 23:57:15 +0100 >> > Michael Niedermayer <mich...@niedermayer.cc> wrote: >> > >> >> For example the progress code in the frame threading. >> > >> > Which was recently fixed in Libav AFAIR... >> >> You're right. libav/libavcodec/pthread_frame.c has code similar to my >> ffmpeg patch http://ffmpeg.org/pipermail/ffmpeg-devel/2016-March/190454.html, >> and much more. >> >> Note: libav/libavcodec/pthread_frame.c uses unnecessary (too strong) >> memory barriers in ff_thread_report_progress(). We can fix those when >> the code is merged to ffmpeg. > > You could also just send a patch to them.
Done. I sent a patch to libav-devel last week: https://lists.libav.org/pipermail/libav-devel/2016-November/080903.html Wan-Teh Chang _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel