Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-02-01 Thread Li, Zhong
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > Of Li, Zhong > Sent: Tuesday, January 30, 2018 10:06 AM > To: FFmpeg development discussions and patches > <ffmpeg-devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-29 Thread Li, Zhong
-- > > >>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On > > >>> Behalf Of James Almer > > >>> Sent: Thursday, January 18, 2018 1:15 PM > > >>> To: ffmpeg-devel@ffmpeg.org > > >>> Subject: Re: [FFmpeg-devel] [P

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-26 Thread Michael Niedermayer
peg-devel-boun...@ffmpeg.org] On Behalf > >>> Of James Almer > >>> Sent: Thursday, January 18, 2018 1:15 PM > >>> To: ffmpeg-devel@ffmpeg.org > >>> Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to > >>> AVCodecParameters > >&g

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-21 Thread Li, Zhong
> > As mentioned in the thread for that patch already, writing new code using > deprecated API should really be avoided. > > The way I see it, if someone really needs to know coded w/h (which is > typically an internal technical detail of no relevance to users), they should > decode a frame and

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-19 Thread James Almer
> Sent: Thursday, January 18, 2018 1:15 PM >>> To: ffmpeg-devel@ffmpeg.org >>> Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to >>> AVCodecParameters >>> >>> On 1/18/2018 2:03 AM, Zhong Li wrote: >>>> coded_width/height may be different f

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-19 Thread Hendrik Leppkes
eg.org >> Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to >> AVCodecParameters >> >> On 1/18/2018 2:03 AM, Zhong Li wrote: >> > coded_width/height may be different from width/height sometimes >> >> > (e.g, crop or lowres cases). >

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-18 Thread Li, Zhong
> -Original Message- > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf > Of James Almer > Sent: Thursday, January 18, 2018 1:15 PM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to > AVCodecParameters &

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-18 Thread Hendrik Leppkes
On Thu, Jan 18, 2018 at 6:14 AM, James Almer wrote: > On 1/18/2018 2:03 AM, Zhong Li wrote: >> coded_width/height may be different from width/height sometimes > >> (e.g, crop or lowres cases). > > Which is why it's not a field that belongs to AVCodecParameters. > > Codec level

Re: [FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-17 Thread James Almer
On 1/18/2018 2:03 AM, Zhong Li wrote: > coded_width/height may be different from width/height sometimes > (e.g, crop or lowres cases). Which is why it's not a field that belongs to AVCodecParameters. Codec level cropping has nothing to do with containers. Same with lowres, which is an internal

[FFmpeg-devel] [PATCH 1/2] lavc: Add coded_w/h to AVCodecParameters

2018-01-17 Thread Zhong Li
coded_width/height may be different from width/height sometimes (e.g, crop or lowres cases). ffprobe always show coded_width/height same as width/height since they are overwritten. This fixes tiket #6958. Signed-off-by: Zhong Li --- libavcodec/avcodec.h | 7 +++