From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsv: fallback to the default mfx implementation for internal session on Windows
Date: Mon, 15 May 2023 08:47:28 +0000
Message-ID: <1c945c2a228570ecb2ca7efa79343b28dcd7b203.camel@intel.com> (raw)
In-Reply-To: <CA+anqdzGhnC2emt=yyYn5NE7mHXS1LkmBjcg_TWSU8ccPbt9SA@mail.gmail.com>
On Ma, 2023-05-15 at 08:33 +0200, Hendrik Leppkes wrote:
> On Mon, May 15, 2023 at 8:04 AM Xiang, Haihao
> <haihao.xiang-at-intel.com@ffmpeg.org> wrote:
> >
> > From: Haihao Xiang <haihao.xiang@intel.com>
> >
> > The mfx implementation based on D3D11 is expected for an internal
> > session on Windows, however sometimes this implemntation is not
> > supported [1]. A fallback to the default mfx implementation is added in
> > this patch.
> >
> > [1] https://github.com/intel/cartwheel-ffmpeg/issues/246
> >
>
> From the issue description, the user is trying to use it a as software
> library, not a hardware one?
Yes, because the user has sw library only.
> I don't think software fallback, especially an automatic one, is
> really quite appropriate. When someone requests a "qsv" encoder, they
> expect hardware.
It is not a software fallback. it is a fallback to the default one (which might
be hw based or sw based, it is up to user's hw and media stack).
Thanks
Haihao
>
> - Hendrik
> _______________________________________________
> 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".
next prev parent reply other threads:[~2023-05-15 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 6:04 Xiang, Haihao
2023-05-15 6:33 ` Hendrik Leppkes
2023-05-15 8:47 ` Xiang, Haihao [this message]
2023-05-22 1:36 ` 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=1c945c2a228570ecb2ca7efa79343b28dcd7b203.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