From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v5 1/2] vaapi: support VAProfileH264High10 decoding
Date: Mon, 17 Apr 2023 07:12:52 +0000
Message-ID: <3e78b700f20b4674a92141e06548977e02c8b704.camel@intel.com> (raw)
In-Reply-To: <35c6106440efd7ee3df5952e46c606ad1666826c.camel@intel.com>
On Wo, 2023-04-12 at 03:08 +0000, Xiang, Haihao wrote:
> On Do, 2023-04-06 at 15:26 +0800, Jianfeng Zheng wrote:
> > Hi Haihao,
> >
> > I think high10 intra encoding would also be supported as well. But I
> > havn't made strict
> > test. It could be opened as well in an additional patch after some more
> > test.
>
> It is fine for me. I'll push this patchset if no more comments.
>
Pushed, thx
- Haihao
>
> >
> > Thanks
> > Jianfeng
> >
> > Xiang, Haihao <haihao.xiang-at-intel.com@ffmpeg.org> 于2023年4月6日周四 15:12写道:
> > >
> > > On Vr, 2023-03-31 at 19:54 +0800, jianfeng.zheng wrote:
> > > > see https://github.com/intel/libva/pull/664
> > > >
> > > > Signed-off-by: jianfeng.zheng <jianfeng.zheng@mthreads.com>
> > > > ---
> > > > libavcodec/h264_slice.c | 9 ++++++++-
> > > > libavcodec/vaapi_decode.c | 5 +++++
> > > > 2 files changed, 13 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/libavcodec/h264_slice.c b/libavcodec/h264_slice.c
> > > > index 7767e16cf1..d05b83a121 100644
> > > > --- a/libavcodec/h264_slice.c
> > > > +++ b/libavcodec/h264_slice.c
> > > > @@ -809,8 +809,15 @@ static enum AVPixelFormat
> > > > get_pixel_format(H264Context
> > > > *h, int force_callback)
> > > > *fmt++ = AV_PIX_FMT_YUV444P10;
> > > > } else if (CHROMA422(h))
> > > > *fmt++ = AV_PIX_FMT_YUV422P10;
> > > > - else
> > > > + else {
> > > > +#if CONFIG_H264_VAAPI_HWACCEL
> > > > + // Just add as candidate. Whether VAProfileH264High10
> > > > usable
> > > > or
> > > > + // not is decided by vaapi_decode_make_config() defined in
> > > > FFmpeg
> > > > + // and vaQueryCodingProfile() defined in libva.
> > > > + *fmt++ = AV_PIX_FMT_VAAPI;
> > > > +#endif
> > > > *fmt++ = AV_PIX_FMT_YUV420P10;
> > > > + }
> > > > break;
> > > > case 12:
> > > > if (CHROMA444(h)) {
> > > > diff --git a/libavcodec/vaapi_decode.c b/libavcodec/vaapi_decode.c
> > > > index ab8c12e364..dd55cbd6f1 100644
> > > > --- a/libavcodec/vaapi_decode.c
> > > > +++ b/libavcodec/vaapi_decode.c
> > > > @@ -398,6 +398,11 @@ static const struct {
> > > > MAP(MPEG4, MPEG4_ADVANCED_SIMPLE,
> > > > MPEG4AdvancedSimple),
> > > > MAP(MPEG4, MPEG4_MAIN, MPEG4Main ),
> > > > +#if VA_CHECK_VERSION(1, 18, 0)
> > > > + MAP(H264, H264_HIGH_10_INTRA,
> > > > + H264High10 ),
> > > > + MAP(H264, H264_HIGH_10, H264High10 ),
> > > > +#endif
> > > > MAP(H264, H264_CONSTRAINED_BASELINE,
> > > > H264ConstrainedBaseline),
> > > > MAP(H264, H264_MAIN, H264Main ),
> > >
> > > Pathset LGTM, but I wonder high 10 and high 10 intra are supported for
> > > decoding
> > > however only high 10 is supported for encoding. does high 10 intra not
> > > work
> > > as
> > > expected for encoding ?
> > >
> > > Thanks
> > > 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".
> > _______________________________________________
> > 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".
>
> _______________________________________________
> 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".
_______________________________________________
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-04-17 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 11:54 jianfeng.zheng
2023-04-06 7:06 ` Xiang, Haihao
2023-04-06 7:26 ` Jianfeng Zheng
2023-04-12 3:08 ` Xiang, Haihao
2023-04-17 7:12 ` 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=3e78b700f20b4674a92141e06548977e02c8b704.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