Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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 20:57:48 -0300
Message-ID: <fd5d1e88-0ca8-19c3-cb75-748127111048@gmail.com> (raw)
In-Reply-To: <DM8P223MB036599931827C9CB8E6200D0BA0E9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On 11/25/2022 8:51 PM, Soft Works wrote:
> 
> 
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>> James Almer
>> Sent: Saturday, November 26, 2022 12:35 AM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_h264: don't support
>> P010 format
>>
>> On 11/25/2022 8:26 PM, Dong, Ruijing wrote:
>>> [AMD Official Use Only - General]
>>>
>>> Will it make sense to accept P010 input, however encode to h264
>> 8bit?
>>
>> If it works (the encoder accepts the 10 bit input even if it encodes
>> it
>> as 8bit), then i don't see why not. I assume it would also be faster
>> than using swscale to convert said 10bit input to nv12 before passing
>> that to the encoder.
>>
>> Removing support for a pixel format as input in an encoder needs a
>> reason other than "It's rarely used", more so when it's a single
>> line.
>> It either needs to not work, or somehow get in the way of further
>> improvements.
> 
> Oh sorry, I noticed that there was a misunderstanding.
> 
> When I said "It's rarely used", I didn't mean that as a justification
> for the removal, it was meant as an explanation why none of the
> hwaccels has implemented it.
> 
> softworkz

Alright, then i'll repeat my question: Does it work? And I don't mean 
the encoder outputting a 10bit h264 stream, since you made it clear it 
doesn't, i mean accepting 10bit input in p010 pixel format and 
outputting a valid stream and not garbage.
If it does, then there's no reason to remove this line. If it does not, 
then that should have been mentioned in the patch as the reason why this 
is being done.
_______________________________________________
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-11-25 23:57 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
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 [this message]
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=fd5d1e88-0ca8-19c3-cb75-748127111048@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