From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 685C844E35 for ; Fri, 25 Nov 2022 23:34:01 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 1451468B413; Sat, 26 Nov 2022 01:33:58 +0200 (EET) Received: from mail-oa1-f52.google.com (mail-oa1-f52.google.com [209.85.160.52]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 70A9768B0D6 for ; Sat, 26 Nov 2022 01:33:51 +0200 (EET) Received: by mail-oa1-f52.google.com with SMTP id 586e51a60fabf-13bd2aea61bso6822129fac.0 for ; Fri, 25 Nov 2022 15:33:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=C7WosSsLwDpb1bX15FA1rgTbfpIJJARtlFdK+5/yWIM=; b=VOsJmTqUsyw0oIPeVey95jyAo2UOwO0RDhdo5mU+bii9JBlZEzZZhNtC35g0zB9aCj TxkjYlVQ3YaHuaOdQ8zH0kUy1wPHtkyI1spBfNp7U7b4Pr9u7JoFKpLAxpIZDK6sqD9V XqqU8SDGg4nysLZFZardltBDe2+eVxpJuzwFQnQWBsEy0cAY+Z4GOcGGl/6K4Tl5YDbH HKGyKiqhs3OLLFgIpaFG32IVYzEb5xli4O/mHgeiGlLisV3fyhlbcXYzmZ+49Eygkgqv uh0+9L8oLORzTYuAaiSXJbsOM68cSfzX16nBvDpJGQIa5tEYtjknMF0cOIkFT788cmOx SBsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=C7WosSsLwDpb1bX15FA1rgTbfpIJJARtlFdK+5/yWIM=; b=QbTUz2WsaqBn89Ww9HqVhk3cYtNrZw6Bv6SOnaJRkMHZe4qQ/2cnIjTK+lmemQovQZ sh0/aB58b/jtboeBeunjPa2hvsAQxffkCGiLuLww0tRlUQtxtqscnxnC0OrMjCqyMTvW 6OP+izmcvhD6MJ1hG3RGyG0mHD9xU8DNSV4ybqqceqb7wmo0UEnPZhebMaMOIKLgnNDd ogNmzFeX6Ym9nLgrNYrPG/tofO50QA7I48Itf9uuyj7qENR5rhUl7jVWrsrAt3O1j5cZ 63mQK7YYDOlju69eoZl+uBmCnI6+S8AKfwPX6l/VS9UjLscGcB+ffUtmHwDTbkSzKrK7 UufQ== X-Gm-Message-State: ANoB5pkpJloLUBCs9TbsOVG/Cl6Biu7/5wghUzbSM2IKj7Hu4I7U1TdG AGo36L2q5y0wpFVn6e0UHXNiXQDPYQE= X-Google-Smtp-Source: AA0mqf5hzmipxRyqf6B4HBDvIKzBfoBbFxd+dcyOcdeD8NZquV+tqMJUrIUl0nYGDLEEpd0GJApdJA== X-Received: by 2002:a05:6870:8dc6:b0:13b:ed4c:2fbd with SMTP id lq6-20020a0568708dc600b0013bed4c2fbdmr22059202oab.169.1669419229609; Fri, 25 Nov 2022 15:33:49 -0800 (PST) Received: from [192.168.0.15] ([181.85.72.69]) by smtp.gmail.com with ESMTPSA id r11-20020a9d750b000000b006621427ecc7sm2178392otk.60.2022.11.25.15.33.48 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Nov 2022 15:33:49 -0800 (PST) Message-ID: Date: Fri, 25 Nov 2022 20:34:33 -0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: <20221124052209.520239-1-haihao.xiang@intel.com> <166938393779.4503.7930861168279237996@lain.khirnov.net> <12d8e532-f236-83b8-61cf-6c9ee72b10ee@gmail.com> <4bcec8d4-8593-9a23-3130-8aa52b1f3c11@gmail.com> From: James Almer In-Reply-To: Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvenc_h264: don't support P010 format X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: 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. > > Thanks, > Ruijing > > -----Original Message----- > From: ffmpeg-devel 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 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 On Behalf Of >>>>> Anton Khirnov >>>>> Sent: Friday, November 25, 2022 2:46 PM >>>>> To: FFmpeg development discussions and patches >>>> devel@ffmpeg.org> >>>>> Cc: Haihao Xiang >>>>> 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". > > > _______________________________________________ > 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".