Re: [FFmpeg-devel] [PATCH] doc/examples/muxing: Fix av_frame_make_writable usage

2016-11-22 Thread Michael Niedermayer
On Wed, Nov 23, 2016 at 02:09:14AM +0100, wm4 wrote: > On Mon, 24 Oct 2016 00:12:00 +0200 > Sam Hocevar wrote: > > > This patch moves the av_frame_make_writable() call from fill_yuv_image > > to get_video_frame so that its argument can be the actual frame that > > will be sent to the encoder. > >

Re: [FFmpeg-devel] [PATCH] doc/examples/muxing: Fix av_frame_make_writable usage

2016-11-22 Thread wm4
On Mon, 24 Oct 2016 00:12:00 +0200 Sam Hocevar wrote: > This patch moves the av_frame_make_writable() call from fill_yuv_image > to get_video_frame so that its argument can be the actual frame that > will be sent to the encoder. > > This fixes data corruption issues in codecs that keep reference

Re: [FFmpeg-devel] [PATCH] doc/examples/muxing: Fix av_frame_make_writable usage

2016-11-22 Thread Sam Hocevar
On Mon, Oct 24, 2016, Sam Hocevar wrote: > This fixes data corruption issues in codecs that keep references on > one or several previous frames. This doesn't seem to have gotten much attention. Any comments maybe? -- Sam. ___ ffmpeg-devel mailing l

[FFmpeg-devel] [PATCH] doc/examples/muxing: Fix av_frame_make_writable usage

2016-10-23 Thread Sam Hocevar
This patch moves the av_frame_make_writable() call from fill_yuv_image to get_video_frame so that its argument can be the actual frame that will be sent to the encoder. This fixes data corruption issues in codecs that keep references on one or several previous frames. Signed-off-by: Sam Hocevar