On Sun, Mar 8, 2015 at 5:06 AM, Vittorio Giovara
<[email protected]> wrote:
> The container cropping is applied only when difference is within 16
> pixels, and the smallest value between the two is chosen.
>
> Bug-Id: 383
> Signed-off-by: Vittorio Giovara <[email protected]>
> ---
>  libavcodec/h264_slice.c | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/libavcodec/h264_slice.c b/libavcodec/h264_slice.c
> index 6f22c87..bd81ba9 100644
> --- a/libavcodec/h264_slice.c
> +++ b/libavcodec/h264_slice.c
> @@ -1023,13 +1023,10 @@ static int init_dimensions(H264Context *h)
>  {
>      int width  = h->width  - (h->sps.crop_right + h->sps.crop_left);
>      int height = h->height - (h->sps.crop_top   + h->sps.crop_bottom);
> -    int crop_present = h->sps.crop_left  || h->sps.crop_top ||
> -                       h->sps.crop_right || h->sps.crop_bottom;
>
>      /* handle container cropping */
> -    if (!crop_present &&
> -        FFALIGN(h->avctx->width,  16) == h->width &&
> -        FFALIGN(h->avctx->height, 16) == h->height) {
> +    if (FFALIGN(h->avctx->width,  16) == FFALIGN(width,  16) &&
> +        FFALIGN(h->avctx->height, 16) == FFALIGN(height, 16)) {
>          width  = h->avctx->width;
>          height = h->avctx->height;
>      }


I though we discussed on IRC recently, and the consensus was that
container cropping would be best left to the API-user to handle?

- Hendrik
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to