From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/3] lavc/qsvenc: use the right alignment instead of hard coded value
Date: Mon, 22 May 2023 01:38:40 +0000
Message-ID: <f613b7fa8f55565b5f19c0e0b147c02d90000c59.camel@intel.com> (raw)
In-Reply-To: <20230518065438.144156-1-haihao.xiang@intel.com>
On Do, 2023-05-18 at 14:54 +0800, Xiang, Haihao wrote:
> From: Haihao Xiang <haihao.xiang@intel.com>
>
> Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
> ---
> libavcodec/qsvenc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/qsvenc.c b/libavcodec/qsvenc.c
> index 0ed1f757d4..2c38fbf0dc 100644
> --- a/libavcodec/qsvenc.c
> +++ b/libavcodec/qsvenc.c
> @@ -1909,7 +1909,7 @@ static int submit_frame(QSVEncContext *q, const AVFrame
> *frame,
> } else {
> /* make a copy if the input is not padded as libmfx requires */
> /* and to make allocation continious for data[0]/data[1] */
> - if ((frame->height & 31 || frame->linesize[0] & (q->width_align -
> 1)) ||
> + if ((frame->height & (q->height_align - 1) || frame->linesize[0] &
> (q->width_align - 1)) ||
> (frame->data[1] - frame->data[0] != frame->linesize[0] *
> FFALIGN(qf->frame->height, q->height_align))) {
> int tmp_w, tmp_h;
> qf->frame->height = tmp_h = FFALIGN(frame->height, q-
> >height_align);
Will apply this patchset
- Haihao
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-05-22 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 6:54 Xiang, Haihao
2023-05-18 6:54 ` [FFmpeg-devel] [PATCH 2/3] lavc/qsvenc: avoid data copy if possible Xiang, Haihao
2023-05-18 6:54 ` [FFmpeg-devel] [PATCH 3/3] lavc/qsvenc: make sure continuous allocation Xiang, Haihao
2023-05-22 1:38 ` Xiang, Haihao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f613b7fa8f55565b5f19c0e0b147c02d90000c59.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git