Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	"anton@khirnov.net" <anton@khirnov.net>
Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio related code when MFX_VERSION < 2.0
Date: Sun, 1 May 2022 05:13:45 +0000
Message-ID: <DM8P223MB0365C2074CA9011F9E1CEB43BAFE9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <99d97f51de78fdbe99a309272be81cce2efafd16.camel@intel.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Xiang, Haihao
> Sent: Sunday, May 1, 2022 6:52 AM
> To: anton@khirnov.net; ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio related
> code when MFX_VERSION < 2.0
> 
> On Sun, 2022-05-01 at 03:10 +0000, Soft Works wrote:
> > > -----Original Message-----
> > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > > Xiang, Haihao
> > > Sent: Sunday, May 1, 2022 4:16 AM
> > > To: anton@khirnov.net; ffmpeg-devel@ffmpeg.org
> > > Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio
> related
> > > code when MFX_VERSION < 2.0
> > >
> > > On Sat, 2022-04-30 at 16:51 +0000, Soft Works wrote:
> > > > > -----Original Message-----
> > > > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf
> Of
> > > > > Xiang, Haihao
> > > > > Sent: Wednesday, April 6, 2022 5:38 AM
> > > > > To: anton@khirnov.net; ffmpeg-devel@ffmpeg.org
> > > > > Subject: Re: [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio
> > >
> > > related
> > > > > code when MFX_VERSION < 2.0
> > > > >
> > > > > On Tue, 2022-04-05 at 13:50 +0200, Anton Khirnov wrote:
> > > > > > Quoting Xiang, Haihao (2022-03-11 09:16:25)
> > > > > > > From: Haihao Xiang <haihao.xiang@intel.com>
> > > > > > >
> > > > > > > Audio isn't supported for MFX_VERSION >= 2.0[1][2]. This
> is in
> > > > > > > preparation for oneVPL support
> > > > > > >
> > > > > > > [1]:
> > > > > > >
> > > > >
> > > > >
> > >
> > >
> https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_inte
> > > > > l_media_sdk.html#msdk-full-name-feature-removals
> > > > > > > [2]: https://github.com/oneapi-src/oneVPL
> > > > > > > ---
> > > > > > >  libavcodec/qsv.c     | 5 +++++
> > > > > > >  libavfilter/qsvvpp.c | 6 ++++++
> > > > > > >  libavfilter/qsvvpp.h | 2 ++
> > > > > > >  3 files changed, 13 insertions(+)
> > > > > >
> > > > > > Why not just remove this completely?
> > > > > > None of our QSV code  does anything with audio.
> > > > >
> > > > > It was removed in an older version, however someone objected
> the
> > > > > removal of
> > > > > this.  See
> > > > >
> > >
> > >
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200819061023.44330
> > > > > 4-2-haihao.xiang@intel.com/
> > > >
> > > > I think this was a misunderstanding. I see not objection. One
> was
> > > > just asking "why" and the other one had missed the point that
> audio
> > > > has never been functional.
> > >
> > > Please find the comment below in the original thread
> > >
> > > "This seems like a generic translation from the library errors to
> FF
> > > error
> > > codes. So even if we'll never touch the audio functionality of it,
> I'd
> > > prefer
> > > to have that struct complete already"
> > >
> > > So my understanding was that the reviewer preferred to keep the
> audio
> > > stuff
> > > unchanged for libmfx.
> >
> > Hm, I hadn't see that here:
> >
> >
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200819061023.44330
> 4-2-haihao.xiang@intel.com/
> >
> > Considering the text again:
> >
> > > "This seems like a generic translation from the library errors to
> FF
> > > error
> > > codes. So even if we'll never touch the audio functionality of it,
> I'd
> > > prefer
> > > to have that struct complete already"
> >
> > I understand the idea. Normally those lines wouldn't hurt. But now,
> that
> > we're facing some kind of "#ifdef hell" anyway, I think it would be
> much
> > better to minimize this as much as possible, and there's really no
> point
> > in translating audio error codes.
> > Also, the struct has never been really complete. Instead of
> retaining
> > unused audio error codes, we should better add those that are
> missing
> > (like -21, -22 and others) and relevant.
> >
> > @Thilo - can we get you warm with that?
> >
> > As an alternative, we could simply replace the two audio definitions
> with
> > plain integer values (MFX_ERR_INVALID_AUDIO_PARAM >> -19)
> >
> >
> > This is a small bit only, but before adding the oneVPL stuff, I
> think
> > we should consolidate the conditional stuff as much as possible.
> >
> > As discussed before, we also need to settle for a minimum libmfx SDK
> > version (compile-time, not runtime!). This will allow to drop quite
> > an amount of conditional code, and this cleanup should be done
> before
> > getting to oneVPL.
> 
> Sure, I'll submit a patch for it.
> 
> >
> > Another thing that is a bit unfortunate is that we are duplicating
> this
> > error mapping struct in qsv.c and qsvvpp.c.
> > I don't mean that it should be linked as an external between
> avfilter
> > and avcodec, but it should come (be included) from a single file.
> 
> We moved the static error table to a .h in the past however it
> resulted in link
> error when building FFmpeg with static libraries.

That's why I said that it doesn't need to be exported - just a
single file that can be included/inlined in both cases where it
is used (lavcodec, lavfilter).

Best,
softworkz


 
_______________________________________________
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".

  reply	other threads:[~2022-05-01  5:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  8:16 [FFmpeg-devel] [PATCH v7 00/10] make QSV works with the Intel's oneVPL Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 01/10] configure: ensure --enable-libmfx uses libmfx 1.x Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 02/10] configure: fix the check for MFX_CODEC_VP9 Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 03/10] qsv: remove mfx/ prefix from mfx headers Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 04/10] qsv: load user plugin for MFX_VERSION < 2.0 Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 05/10] qsv: build audio related code when " Xiang, Haihao
2022-04-05 11:50   ` Anton Khirnov
2022-04-06  3:38     ` Xiang, Haihao
2022-04-30 16:51       ` Soft Works
2022-05-01  2:16         ` Xiang, Haihao
2022-05-01  3:10           ` Soft Works
2022-05-01  4:51             ` Xiang, Haihao
2022-05-01  5:13               ` Soft Works [this message]
2022-05-31  8:58                 ` Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 06/10] qsvenc: support multi-frame encode " Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 07/10] qsvenc: support MFX_RATECONTROL_LA_EXT " Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 08/10] qsv: support OPAQUE memory " Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 09/10] qsv: use a new method to create mfx session when using oneVPL Xiang, Haihao
2022-03-11  8:35   ` Hendrik Leppkes
2022-03-11 13:43     ` Xiang, Haihao
2022-03-11 14:00       ` Hendrik Leppkes
2022-03-15  7:24         ` Xiang, Haihao
2022-04-04  9:46           ` Hendrik Leppkes
2022-04-06  3:58             ` Xiang, Haihao
2022-04-28  9:31               ` Xiang, Haihao
2022-03-11  8:16 ` [FFmpeg-devel] [PATCH v7 10/10] configure: add --enable-libvpl option 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=DM8P223MB0365C2074CA9011F9E1CEB43BAFE9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.com \
    --cc=anton@khirnov.net \
    --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