This solves the problem discussed in
https://ffmpeg.org/pipermail/ffmpeg-devel/2015-September/179238.html
by allowing AVCodec::write_header to be delayed until after packets have been
run through required bitstream filters in order to generate global extradata.
It also provides a mechanism by
This solves the problem discussed in
https://ffmpeg.org/pipermail/ffmpeg-devel/2015-September/179238.html
by allowing AVCodec::write_header to be delayed until after packets have been
run through required bitstream filters in order to generate global extradata.
It also provides a mechanism by
Le sextidi 16 vendémiaire, an CCXXIV, Rodger Combs a écrit :
> + * FIXME: Data allocated here would be leaked if there's a failure before
> + * write_header is called. Ban allocations? Add a `deinit` cleanup
> function?
I would definitely favour the "deinit" idea. This is similar to
On Wed, Oct 07, 2015 at 09:50:05PM -0500, Rodger Combs wrote:
> This solves the problem discussed in
> https://ffmpeg.org/pipermail/ffmpeg-devel/2015-September/179238.html
> by allowing AVCodec::write_header to be delayed until after packets have been
> run through required bitstream filters in
This solves the problem discussed in
https://ffmpeg.org/pipermail/ffmpeg-devel/2015-September/179238.html
by allowing AVCodec::write_header to be delayed until after packets have been
run through required bitstream filters in order to generate global extradata.
It also provides a mechanism by
