> -Original Message-
> From: ffmpeg-devel On Behalf Of Fu,
> Linjie
> Sent: Tuesday, February 18, 2020 23:06
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> AV_CODEC_CAP_
Quoting Fu, Linjie (2020-02-19 17:25:30)
> > Yes, that's what I mean. Flush and destroy an AVCodecContext and open a
> > new one. But then why is there a need for this flag?
> >
> Previously I intended to add close and re-init inside specific encoder like
> [1],
> without destroy AVCodecContext,
Quoting Michael Niedermayer (2020-02-19 19:07:28)
> On Tue, Feb 18, 2020 at 05:42:19PM +0100, Anton Khirnov wrote:
> > Quoting Fu, Linjie (2020-02-18 16:06:10)
> > > > Is there even a sufficiently strong use case for this? Why not just
> > >
> > > Like transcoding
On Tue, Feb 18, 2020 at 05:42:19PM +0100, Anton Khirnov wrote:
> Quoting Fu, Linjie (2020-02-18 16:06:10)
> > > Is there even a sufficiently strong use case for this? Why not just
> >
> > Like transcoding reinit-large_420_8-to-small_420_8.h264 (from 352x288 to
> > 240x196)
> > and prefer to keep
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Anton Khirnov
> Sent: Wednesday, February 19, 2020 00:42
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> AV_CODEC_CAP_
Quoting Fu, Linjie (2020-02-18 16:06:10)
> > Is there even a sufficiently strong use case for this? Why not just
>
> Like transcoding reinit-large_420_8-to-small_420_8.h264 (from 352x288 to
> 240x196)
> and prefer to keep the resolution changing in the output stream.
>
> IMHO not modifying the
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Anton Khirnov
> Sent: Tuesday, February 18, 2020 21:32
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> AV_CODEC_CAP_
Quoting Michael Niedermayer (2020-02-17 23:38:31)
> On Mon, Feb 17, 2020 at 06:28:23PM +, Fu, Linjie wrote:
>
> > > > > https://patchwork.ffmpeg.org/patch/14122/
>
> iam hesitating because it feeds encoders with changing resolution resulting
> in potentially undefined behavior ...
>
>
> >
tember 11, 2019 15:12
> > > To: FFmpeg development discussions and patches > > de...@ffmpeg.org>
> > > Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> > > AV_CODEC_CAP_VARIABLE_DIMENSIONS flag
> > >
> > > > -Original Message
> -Original Message-
> From: ffmpeg-devel On Behalf Of Fu,
> Linjie
> Sent: Thursday, October 10, 2019 14:46
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> AV_CODEC_CAP_
> -Original Message-
> From: ffmpeg-devel On Behalf Of Fu,
> Linjie
> Sent: Wednesday, September 11, 2019 15:12
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> AV_CODEC_CAP_
Behalf
> > > Of Michael Niedermayer
> > > Sent: Wednesday, July 31, 2019 14:04
> > > To: FFmpeg development discussions and patches > > de...@ffmpeg.org>
> > > Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> > > AV_CODEC_CAP_VARIA
discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> > AV_CODEC_CAP_VARIABLE_DIMENSIONS flag
> >
> > On Tue, Jul 30, 2019 at 10:27:10AM -0300, James Almer wrote:
> > > On 7/30/
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Michael Niedermayer
> Sent: Wednesday, July 31, 2019 14:04
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH, v2
oun...@ffmpeg.org] On Behalf
> >>> Of Carl Eugen Hoyos
> >>> Sent: Tuesday, July 30, 2019 16:06
> >>> To: FFmpeg development discussions and patches >>> de...@ffmpeg.org>
> >>> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of James Almer
> Sent: Tuesday, July 30, 2019 21:27
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> AV_CODEC_CAP_VARIABLE_DIME
: Tuesday, July 30, 2019 16:06
>>> To: FFmpeg development discussions and patches >> de...@ffmpeg.org>
>>> Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
>>> AV_CODEC_CAP_VARIABLE_DIMENSIONS flag
>>>
>>> Am Di., 30. Juli 2019 um 06:46 U
s and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH, v2 2/4] avc/avcodec: add
> > AV_CODEC_CAP_VARIABLE_DIMENSIONS flag
> >
> > Am Di., 30. Juli 2019 um 06:46 Uhr schrieb Linjie Fu :
> > >
> > > Add AV_CODEC_CAP_VARIABLE_DIMEN
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: Tuesday, July 30, 2019 16:06
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH, v2
Am Di., 30. Juli 2019 um 06:46 Uhr schrieb Linjie Fu :
>
> Add AV_CODEC_CAP_VARIABLE_DIMENSIONS flag to indicate
> whether encoder supports variable dimension encoding.
Isn't this about variable (or "changing") "resolutions" instead of dimensions?
Carl Eugen
Add AV_CODEC_CAP_VARIABLE_DIMENSIONS flag to indicate whether encoder
supports variable dimension encoding.
Signed-off-by: Linjie Fu
---
[v2]: update API changes.
doc/APIchanges | 3 +++
fftools/cmdutils.c | 2 ++
libavcodec/avcodec.h | 5 +
libavcodec/rawenc.c | 1 +
21 matches
Mail list logo
