From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 2/2] ffmpeg_opt: consider HW acceleration method when selecting decoder
Date: Fri, 29 Jul 2022 09:46:31 +0000
Message-ID: <DM8P223MB0365A8C9322D58E28F8442EBBA999@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAEEMt2mZG0D_tE0YcfNTrjTTMSNULQ2OAaHmRHHZN8o_iUbSFA@mail.gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Ronald S. Bultje
> Sent: Friday, July 29, 2022 10:50 AM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v3 2/2] ffmpeg_opt: consider HW
> acceleration method when selecting decoder
>
> Hi,
>
> On Fri, Jul 29, 2022 at 4:38 PM Xiang, Haihao <
> haihao.xiang-at-intel.com@ffmpeg.org> wrote:
>
> > libdav1d is the preferred AV1 decoder in FFmpeg, libdav1d is always
> used
> > when
> > running the command below even if user expects vaapi or other HW
> > acceleration
> > methods.
> >
>
> I think that is a pretty serious issue. Don't we always want to
> prefer a hw
> decoder by default? I agree there should also be ways to force-select
> specific hw/sw decoders, but shouldn't hw be the default?
I don't think that this would be reasonably possible in any way.
There are a lot of questions which ffmpeg cannot answer, e.g.:
- Which hwaccel to choose?
- Which hwaccel is available?
- Which parameters are required for selecting a device
that is working?
- Is the auto-selected device even capable to decode a certain
input?
(pixel format, bit depth, codec profile, frame size, ...)
For the user who is creating the command line, it is important to
be able to rely on what is going to happen. If they can't command
lines will fail:
- The outputs of hw decoders vary. Some output to hw format, some
to sw format by default. You may need to specify hwaccel_output_format
or use hwdownload
- Depending on the hwaccel, a totally different set of filters
may be required (not to speak of encoders)
- How would you specify that you want a sw decoder instead?
IMO, predictability is the topmost important behavioral aspect
for users (be it humans of machines.. ;-)
Best regards,
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".
next prev parent reply other threads:[~2022-07-29 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 4:30 [FFmpeg-devel] [PATCH v3 1/2] ffmpeg_opt: select a decoder after getting values for per-stream hwdec options Xiang, Haihao
2022-07-25 4:30 ` [FFmpeg-devel] [PATCH v3 2/2] ffmpeg_opt: consider HW acceleration method when selecting decoder Xiang, Haihao
2022-07-29 8:37 ` Xiang, Haihao
2022-07-29 8:50 ` Ronald S. Bultje
2022-07-29 9:46 ` Soft Works [this message]
2022-08-01 1:52 ` Xiang, Haihao
2022-08-01 2:14 ` Soft Works
2022-08-01 2:37 ` Xiang, Haihao
2022-08-01 9:12 ` Anton Khirnov
2022-08-02 7:57 ` 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=DM8P223MB0365A8C9322D58E28F8442EBBA999@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz@hotmail.com \
--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