From: Chen Yufei <cyfdecyf@gmail.com>
To: "Xiang, Haihao" <haihao.xiang@intel.com>
Cc: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 0/1] avfilter/vf_vpp_qsv: apply 3D LUT from file
Date: Tue, 23 Jan 2024 20:09:16 +0800
Message-ID: <CAAoCq2tLBLEW16J8B7QvfvV59+HYUniwsYKtwUgniGEwdh95LQ@mail.gmail.com> (raw)
In-Reply-To: <179e2295ac2ba399cef97625e2cb61464c20bea6.camel@intel.com>
On Tue, Jan 23, 2024 at 10:00 AM Xiang, Haihao <haihao.xiang@intel.com> wrote:
>
> On Sa, 2024-01-20 at 23:14 +0800, Chen Yufei wrote:
> > This patch adds support for applying 3D LUT from file using oneVPL VPP.
> >
> > PATCH v1 uses VA-API to create LUT surface. Because oneVPL can't work with VA-
> > API on Windows,
> > this version now creates LUT in system memory (MFX_RESOURCE_SYSTEM_SURFACE)
> > and let oneVPL
> > copy LUT to video memory.
> >
> > Note: requires oneVPL-intel-gpu version >= 24.1.1 because this version
> > contains
> > a fix for creating LUT in video memory.
> > (For details, refer to
> > https://github.com/oneapi-src/oneVPL-intel-gpu/issues/307)
>
> Please bump a new runtime version, then you may check the runtime version for
> this feature.
What does "bump a new runtime version" mean? Could you please provide
more details?
I'm confused about the version number of libvpl and oneVPL-intel-gpu.
I looked at the implementation of `QSV_RUNTIME_VERSION_ATLEAST`, and
tried to print `mfxVersion` stored in `vpp->qsv`.
I can only get 2.10 which is the version of libvpl (2.10.1 actually)
on my system.
I've also looked at the build directory of oneVPL-intel-gpu on my
system, the compile commands defines following
-DMEDIA_VERSION_STR="24.1.2" -DMFX_API_VERSION="2.10+"
Do you mean I should just use `QSV_RUNTIME_VERSION_ATLEAST(ver, 2,
10)` to check the runtime version?
Does this guarantee the underlying oneVPL-intel-gpu would be >= 24.1.1 then?
>
> Thanks
> Haihao
>
>
> >
> > Chen Yufei (1):
> > avfilter/vf_vpp_qsv: apply 3D LUT from file.
> >
> > libavfilter/Makefile | 8 +-
> > libavfilter/lut3d.c | 669 +++++++++++++++++++++++++++++++++++++++
> > libavfilter/lut3d.h | 13 +
> > libavfilter/vf_lut3d.c | 590 +---------------------------------
> > libavfilter/vf_vpp_qsv.c | 113 ++++++-
> > 5 files changed, 799 insertions(+), 594 deletions(-)
> > create mode 100644 libavfilter/lut3d.c
> >
>
--
Best regards,
Chen Yufei
_______________________________________________
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".
next prev parent reply other threads:[~2024-01-23 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 15:14 Chen Yufei
2024-01-20 15:14 ` [FFmpeg-devel] [PATCH v2 1/1] " Chen Yufei
2024-01-24 11:39 ` Anton Khirnov
2024-01-25 16:16 ` Chen Yufei
2024-01-28 10:31 ` Anton Khirnov
2024-01-28 12:22 ` Paul B Mahol
2024-01-28 13:51 ` Zhao Zhili
2024-01-28 14:10 ` Anton Khirnov
2024-01-28 15:46 ` Zhao Zhili
2024-01-28 16:52 ` Anton Khirnov
2024-01-28 17:27 ` Zhao Zhili
2024-01-29 3:01 ` Chen Yufei
2024-01-29 3:28 ` Zhao Zhili
2024-01-29 12:09 ` Chen Yufei
2024-01-29 17:07 ` Anton Khirnov
2024-01-30 2:59 ` Chen Yufei
2024-02-03 11:09 ` Chen Yufei
2024-01-23 1:59 ` [FFmpeg-devel] [PATCH v2 0/1] " Xiang, Haihao
2024-01-23 12:09 ` Chen Yufei [this message]
2024-01-24 7:24 ` Xiang, Haihao
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=CAAoCq2tLBLEW16J8B7QvfvV59+HYUniwsYKtwUgniGEwdh95LQ@mail.gmail.com \
--to=cyfdecyf@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=haihao.xiang@intel.com \
/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