From: Michael Fabian 'Xaymar' Dirks <michael.dirks@xaymar.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/5] avcodec: Require AMF SDK v1.4.23 or newer
Date: Thu, 13 Jan 2022 00:49:20 +0100
Message-ID: <36b60db3-044e-cf2b-dfad-f931726a7f5e@xaymar.com> (raw)
In-Reply-To: <CA+anqdy4KLTEp-BUbSjP3eBw4numszA5_juSweAsFjd9niDvjw@mail.gmail.com>
I'm unsure what compatibility is broken here, since AMD's AMF SDK does not verify the drivers AMF Runtime, or the other way around. At least from my experience writing an AMF integration for another software and testing with current hardware, older Drivers work just fine. If necessary I can port the entire compatibility structures I built for another open source software to FFmpeg, which would extend the minimum driver version to 19.7.1 and would include drivers that cause stack and heap corruptions, weird dlopen/LoadLibrary issues, and more.
If you meant compatibility with older versions of the SDK, it is possible. Since this is meant to add new features, increasing the minimum SDK version felt line the better choice than allowing users to build amfenc "wrong" and getting a completely different set of options out of FFmpeg.
On 2022-01-13 00:20, Hendrik Leppkes wrote:
> On Thu, Jan 13, 2022 at 12:18 AM Michael Fabian 'Xaymar' Dirks
> <info@xaymar.com> wrote:
>> From: Michael Fabian 'Xaymar' Dirks <michael.dirks@xaymar.com>
>>
>> Increasing the minimum AMF SDK version allows us to support
>> more recent hardware and drivers, which is necessary to fix
>> some of the discrepancies between older and newer drivers on
>> AMD hardware with FFmpeg.
> 1.4.23 was just released in December, merely a month ago, correct?
> Is there no way to maintain compatibility, or at least more of it, as
> well as supporting new hardware?
>
> - Hendrik
> _______________________________________________
> 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".
next prev parent reply other threads:[~2022-01-12 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 23:17 Michael Fabian 'Xaymar' Dirks
2022-01-12 23:17 ` [FFmpeg-devel] [PATCH 2/5] avcodec/amfenc: Set all color metadata for AMF Michael Fabian 'Xaymar' Dirks
2022-07-10 10:22 ` Marton Balint
2022-01-12 23:17 ` [FFmpeg-devel] [PATCH 3/5] avcodec/amfenc: Add the new usage presets Michael Fabian 'Xaymar' Dirks
2022-01-12 23:17 ` [FFmpeg-devel] [PATCH 4/5] avcodec/amfenc: Add "High Motion Quality Boost" option Michael Fabian 'Xaymar' Dirks
2022-01-12 23:17 ` [FFmpeg-devel] [PATCH 5/5] avcodec/amfenc: Add missing profiles Michael Fabian 'Xaymar' Dirks
2022-07-10 10:26 ` Marton Balint
2022-01-12 23:20 ` [FFmpeg-devel] [PATCH 1/5] avcodec: Require AMF SDK v1.4.23 or newer Hendrik Leppkes
2022-01-12 23:49 ` Michael Fabian 'Xaymar' Dirks [this message]
2022-07-06 20:48 ` Michael Fabian 'Xaymar' Dirks
-- strict thread matches above, loose matches on Subject: below --
2022-01-12 22:49 Michael Fabian 'Xaymar' Dirks
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=36b60db3-044e-cf2b-dfad-f931726a7f5e@xaymar.com \
--to=michael.dirks@xaymar.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