From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_h264: don't support P010 format
Date: Fri, 25 Nov 2022 16:47:53 -0300
Message-ID: <12d8e532-f236-83b8-61cf-6c9ee72b10ee@gmail.com> (raw)
In-Reply-To: <DM8P223MB0365B9C253872D9766C4FD4FBA0E9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
On 11/25/2022 3:03 PM, Soft Works wrote:
>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>> Anton Khirnov
>> Sent: Friday, November 25, 2022 2:46 PM
>> To: FFmpeg development discussions and patches <ffmpeg-
>> devel@ffmpeg.org>
>> Cc: Haihao Xiang <haihao.xiang@intel.com>
>> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_h264: don't support
>> P010 format
>>
>> Why?
>
> It's rarely used. There's not even a hwaccel that can decode this.
The dxva2/d3d11 hwaccels seemingly do, as does the qsv decoder. And
being rarely used alone is not a reason to remove something. There needs
to be some benefit to justify it (Simplifying maintenance, removing
legacy code, etc).
Also, p010 can be generated by swscale, and the only other software
pixel format supported in this list is nv12, which is 8bit. If we remove
p010, we would be making 10bit encodings not longer work with the output
of software decoders as input, right?
_______________________________________________
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-11-25 19:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 5:22 Xiang, Haihao
2022-11-25 13:45 ` Anton Khirnov
2022-11-25 18:03 ` Soft Works
2022-11-25 19:47 ` James Almer [this message]
2022-11-25 23:20 ` Soft Works
2022-11-25 23:25 ` James Almer
2022-11-25 23:26 ` Dong, Ruijing
2022-11-25 23:34 ` James Almer
2022-11-25 23:46 ` Dong, Ruijing
2022-11-25 23:51 ` Soft Works
2022-11-25 23:57 ` James Almer
2022-11-26 0:58 ` Soft Works
2022-11-26 1:00 ` James Almer
2022-11-26 2:31 ` Soft Works
2022-11-26 2:35 ` James Almer
2022-11-26 2:54 ` Soft Works
2022-11-28 1:57 ` Xiang, Haihao
2022-11-25 23:47 ` Soft Works
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=12d8e532-f236-83b8-61cf-6c9ee72b10ee@gmail.com \
--to=jamrial@gmail.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