Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Harish Raja Selvan via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "Martin Storsjö" <martin@martin.st>
Cc: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>,
	Harish Raja Selvan <harish.rajaselvan@multicorewareinc.com>
Subject: [FFmpeg-devel] Re: [GASPP PATCH 1/2] Pass "-machine" options through to armasm
Date: Tue, 20 Jan 2026 07:26:56 +0000
Message-ID: <MA5P287MB46256E7A5D82CCAD5AFEB0B09E89A@MA5P287MB4625.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <MA5P287MB4625F595AC3F35150AAA11759EC9A@MA5P287MB4625.INDP287.PROD.OUTLOOK.COM>

Hi Martin and Rémi,
I wanted to add a bit more context on the practical use case.
There are several large and widely used Windows applications especially in enterprise and creator workflows that remain x64-only and rely heavily on FFmpeg at runtime. Examples include Feishu (Lark), Jianying / CapCut, and DingTalk, which are used at very large scale.
Fully porting these applications to native ARM64 is a significant engineering effort and is taking considerable time. On Windows ARM devices, FFmpeg becomes a major performance bottleneck under x64 emulation.
Using ARM64EC FFmpeg allows existing x64 applications to remain unchanged while enabling performance-critical media paths to run natively on ARM, providing a practical transition path for these applications.
If there are any maintenance concerns, technical challenges, or areas where our help would be useful, we would be glad to support and contribute. Having ARM64EC builds of FFmpeg is important for enabling these real-world use cases.
Best regards,
Harish
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2026-01-20  7:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 12:49 [FFmpeg-devel] " Martin Storsjö via ffmpeg-devel
2025-10-03 12:49 ` [FFmpeg-devel] [GASPP PATCH 2/2] Filter out the cl.exe option -arm64EC from armasm Martin Storsjö via ffmpeg-devel
2025-10-09 12:11 ` [FFmpeg-devel] Re: [GASPP PATCH 1/2] Pass "-machine" options through to armasm Martin Storsjö via ffmpeg-devel
2025-10-10 11:11   ` Harish Raja Selvan via ffmpeg-devel
2025-10-10 13:06     ` Martin Storsjö via ffmpeg-devel
2025-11-07  3:51       ` Harish Raja Selvan via ffmpeg-devel
2025-11-07  8:56         ` Martin Storsjö via ffmpeg-devel
2025-11-17  7:27           ` Harish Raja Selvan via ffmpeg-devel
2026-01-20  7:26             ` Harish Raja Selvan via ffmpeg-devel [this message]
2026-01-20 11:32               ` Rémi Denis-Courmont via ffmpeg-devel
2026-01-20 13:34                 ` Martin Storsjö via ffmpeg-devel
2026-01-20 14:33                   ` Rémi Denis-Courmont via ffmpeg-devel
2026-01-27  7:42                     ` Harish Raja Selvan via ffmpeg-devel
2026-01-27 15:34                       ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-07  9:37         ` Rémi Denis-Courmont via ffmpeg-devel

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=MA5P287MB46256E7A5D82CCAD5AFEB0B09E89A@MA5P287MB4625.INDP287.PROD.OUTLOOK.COM \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=harish.rajaselvan@multicorewareinc.com \
    --cc=martin@martin.st \
    /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