From: Thilo Borgmann <thilo.borgmann@mail.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Hardware purchase request Apple M2
Date: Tue, 7 Feb 2023 21:25:14 +0100
Message-ID: <6868f4be-6870-5a0c-78e3-52a570eeec18@mail.de> (raw)
In-Reply-To: <CAHGibzEqYU8vJSOXATXrMtgy=OHcqEUy8BaaM2_jp3r=9Lz6gg@mail.gmail.com>
Am 07.02.23 um 21:19 schrieb Devin Heitmueller:
> On Mon, Feb 6, 2023 at 6:24 AM Thilo Borgmann <thilo.borgmann@mail.de> wrote:
>> Martin pointed out we don't need an M2 for FATE as the instruction sets are equal on both machines.
>
> It may be worth noting that while the M1 and M2 have the same
> instruction set, there is no guarantee the video processing blocks are
> identical. At a minimum we know that the ProRes acceleration supports
> 8K resolutions in the M2.
>
> I got burned by a subtle change in behavior for videotoolbox between
> Intel and M1, so it's possible there are comparable differences
> between M1 and M2. If the tests include validating hardware
> acceleration then there may still be benefits in running the tests on
> both platforms.
Thanks for throwing that in. AFAICT we still don't cover hw accells in FATE, though.
-Thilo
_______________________________________________
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-02-07 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 3:17 Thilo Borgmann
2023-02-06 8:18 ` Jean-Baptiste Kempf
2023-02-06 9:29 ` Paul B Mahol
2023-02-06 11:24 ` Thilo Borgmann
2023-02-07 20:19 ` Devin Heitmueller
2023-02-07 20:25 ` Thilo Borgmann [this message]
2023-02-07 21:41 ` Martin Storsjö
2023-02-18 11:43 ` Neal Gompa
2023-02-23 9:44 ` Stefano Sabatini
2023-02-23 12:47 ` Thilo Borgmann
2023-02-23 15:27 ` Stefano Sabatini
2023-02-23 20:12 ` Michael Niedermayer
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=6868f4be-6870-5a0c-78e3-52a570eeec18@mail.de \
--to=thilo.borgmann@mail.de \
--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