From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v6 00/10] make QSV works with the Intel's oneVPL Date: Fri, 11 Mar 2022 08:23:31 +0000 Message-ID: <df0e604985209b1bbddea7eecf80ec5de9cb89a9.camel@intel.com> (raw) In-Reply-To: <MN2PR04MB598167C3E8B38B97291E331EBABE9@MN2PR04MB5981.namprd04.prod.outlook.com> On Wed, 2021-10-20 at 06:53 +0000, Soft Works wrote: > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Jean-Baptiste Kempf > > Sent: Wednesday, October 20, 2021 8:01 AM > > To: ffmpeg-devel@ffmpeg.org > > Subject: Re: [FFmpeg-devel] [PATCH v6 00/10] make QSV works with the > > Intel's oneVPL > > > > > > > > On Wed, 20 Oct 2021, at 01:00, Soft Works wrote: > > > > -----Original Message----- > > > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > > > Jean-Baptiste Kempf > > > > Sent: Tuesday, October 19, 2021 11:19 PM > > > > To: ffmpeg-devel@ffmpeg.org > > > > Subject: Re: [FFmpeg-devel] [PATCH v6 00/10] make QSV works with > > > > the > > > > Intel's oneVPL > > > > > > > > Hello, > > > > > > > > On Fri, 15 Oct 2021, at 22:23, Soft Works wrote: > > > > > I really appreciate all the effort that Intel is taking to > > > > improve > > > > > ffmppeg for QSV hw acceleration, but in this case I'm not > > > > convinced > > > > > that this should be merged into ffmpeg at this time. > > > > > > > > > > [...] > > > > > In its current state, oneVPL is all about removal of features > > > > that > > > > > have existed for a long time. > > > > > > > > > > In its current state, it does not provide a single benefit over > > > > > libmfx 1.x > > > > > > > > Indeed. > > > > But libmfx is not supported anymore by upstream, who's moving to > > > > oneVPL, aka mfx 2.0. > > Intel documents say otherwise: > > "Intel® Media SDK API is nearing its final update. Implementation updates, > such as security patches and critical bug fixes, will continue as needed." > > https://www.intel.com/content/www/us/en/develop/documentation/upgrading-from-msdk-to-onevpl/top/faq/how-long-will-intel-media-sdk-be-available.html > > "For currently available hardware, Intel® Media SDK and oneVPL provide the > same access. Existing applications may continue to use Intel® Media SDK." > > https://www.intel.com/content/www/us/en/develop/documentation/upgrading-from-msdk-to-onevpl/top.html > According to this doc, new features are supported in oneVPL only. We will provide av1_qsv encoder which is available for --enable-libvpl only, Please see https://github.com/intel-media-ci/ffmpeg/pull/515/commits/f4b500cb977f9506092831fda8f34b207feae618 if you are interested. 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".
parent reply other threads:[~2022-03-11 8:23 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <MN2PR04MB598167C3E8B38B97291E331EBABE9@MN2PR04MB5981.namprd04.prod.outlook.com>]
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=df0e604985209b1bbddea7eecf80ec5de9cb89a9.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