From: "Dong, Ruijing" <Ruijing.Dong@amd.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_h264: don't support P010 format
Date: Fri, 25 Nov 2022 23:26:33 +0000
Message-ID: <SJ1PR12MB61947400106449995EEF3DB2950E9@SJ1PR12MB6194.namprd12.prod.outlook.com> (raw)
In-Reply-To: <4bcec8d4-8593-9a23-3130-8aa52b1f3c11@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
[AMD Official Use Only - General]
Will it make sense to accept P010 input, however encode to h264 8bit?
Thanks,
Ruijing
-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of James Almer
Sent: Friday, November 25, 2022 6:25 PM
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_h264: don't support P010 format
On 11/25/2022 8:20 PM, Soft Works wrote:
>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>> James Almer
>> Sent: Friday, November 25, 2022 8:48 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_h264: don't support
>> P010 format
>>
>> 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
>
> No, only for HEVC and VP9. Probably for AV1 as well in the near future.
Well, then that is a good reason to not remove support in this encoder for a pixel format that not only our software scaler can generate, but decoders using hwaccel backends can output too.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmpeg-devel&data=05%7C01%7Cruijing.dong%40amd.com%7Cf449421fd89948ad96cc08dacf3c324b%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C638050154742304108%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xFeOvsaJw%2F9BlPifrqx33Pv8GurJ1N2lVyuUYHIOClo%3D&reserved=0
To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 17151 bytes --]
[-- Attachment #3: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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 23:26 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
2022-11-25 23:20 ` Soft Works
2022-11-25 23:25 ` James Almer
2022-11-25 23:26 ` Dong, Ruijing [this message]
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=SJ1PR12MB61947400106449995EEF3DB2950E9@SJ1PR12MB6194.namprd12.prod.outlook.com \
--to=ruijing.dong@amd.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