Re: [FFmpeg-devel] [PATCH V3 1/3] avutil: add ROI data struct and bump version

2018-12-27 Thread Guo, Yejun
> -Original Message- > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > Of Derek Buitenhuis > Sent: Friday, December 28, 2018 12:42 AM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH V3 1/3] avutil: add ROI data struct and >

Re: [FFmpeg-devel] [PATCH V3 1/3] avutil: add ROI data struct and bump version

2018-12-27 Thread Derek Buitenhuis
On 27/12/2018 11:05, Guo, Yejun wrote: > enum AVActiveFormatDescription { > @@ -200,6 +206,19 @@ typedef struct AVFrameSideData { > AVBufferRef *buf; > } AVFrameSideData; > > +typedef struct AVROI { > +/* coordinates at frame pixel level. > + * It will be extended internally if the

[FFmpeg-devel] [PATCH V3 1/3] avutil: add ROI data struct and bump version

2018-12-26 Thread Guo, Yejun
The encoders such as libx264 support different QPs offset for different MBs, it makes possible for ROI-based encoding. It makes sense to add support within ffmpeg to generate/accept ROI infos and pass into encoders. Typical usage: After AVFrame is decoded, a ffmpeg filter or user's code generates