On Fri, 20 Dec 2019 at 19:03, Josh Allmann <joshua.allm...@gmail.com> wrote: > > On Fri, 20 Dec 2019 at 15:36, Philip Langdale <phil...@overt.org> wrote: > > > > On 2019-11-18 17:13, Josh Allmann wrote: > > > This patch is meant to be an entry point for discussion around an > > > issue we are having with flushing the nvenc encoder while doing > > > segmented transcoding. Hopefully there will be a less kludgey > > > workaround than this. > > > > Hi Josh, > > > > I happened to see your email recently, and took a quick look into > > this. It seems that encoders are allowed to implement .flush() and > > then avcodec_flush_buffers() can be called on them like on a > > decoder. So I've posted a patch that does this (with the same impl > > that you had). If that works for you, then that's all it takes - > > no need for a new API call because there's already one you can use. > > That would be perfect - thought .flush() was decode-only for some > reason. Thank you! > > Josh
Related: For CLI usage, does this affect the behavior of the global output option -flush_packets 1 When the NVENC encoder is in use, in any way? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
