From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] amfenc: Update the min version to 1.4.28.0 for AMF SDK.
Date: Fri, 27 Jan 2023 21:34:13 +0530
Message-ID: <defe3307-ee88-4344-d684-5bf56a658c7d@gyani.pro> (raw)
In-Reply-To: <836e1532-b398-461f-aefb-aff78536d558@betaapp.fastmail.com>
On 2023-01-27 09:30 pm, Jean-Baptiste Kempf wrote:
> On Fri, 27 Jan 2023, at 16:58, Gyan Doshi wrote:
>> On 2023-01-27 09:17 pm, Jean-Baptiste Kempf wrote:
>>> Hello,
>>>
>>> On Tue, 20 Dec 2022, at 18:48, Dmitrii Ovchinnikov wrote:
>>>> Hi,
>>>>
>>>>>> When was this release released?
>>>> The release was 13.12.2022
>>>>>> Is it headers only or is it runtime too?
>>>> it still supports old drivers, but to use the av1 encoder, you need an
>>>> up-to-date driver version and a supported graphics card.
>>> I've tested this patch and it works.
>>>
>>> Can someone apply this, please?
>> Only the first one?
> I tested both, including the second one (AV1 encoding support) and it works.
Ok, since Dmitrii is the AMF maintainer, will do.
Regards,
Gyan
_______________________________________________
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:[~2023-01-27 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 15:20 Dmitrii Ovchinnikov
2022-12-20 15:20 ` [FFmpeg-devel] [PATCH 2/2] libavcodec/amfenc: add AV1 encoding support Dmitrii Ovchinnikov
2022-12-20 16:41 ` [FFmpeg-devel] [PATCH 1/2] amfenc: Update the min version to 1.4.28.0 for AMF SDK Jean-Baptiste Kempf
2022-12-20 17:48 ` Dmitrii Ovchinnikov
2023-01-27 15:47 ` Jean-Baptiste Kempf
2023-01-27 15:58 ` Gyan Doshi
2023-01-27 16:00 ` Jean-Baptiste Kempf
2023-01-27 16:04 ` Gyan Doshi [this message]
2023-01-27 17:11 ` Gyan Doshi
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=defe3307-ee88-4344-d684-5bf56a658c7d@gyani.pro \
--to=ffmpeg@gyani.pro \
--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