From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] fftools/ffplay: migrate to SDL3
Date: Sat, 3 Jan 2026 14:12:01 +0100
Message-ID: <aVkVodBZ0Ut6h_gC@phare.normalesup.org> (raw)
In-Reply-To: <tencent_6F01BD6B827FDAAE463899C295B5D06BD20A@qq.com>
Zhao Zhili via ffmpeg-devel (HE12026-01-03):
> The ffplay vulkan renderer is focus on hardware decoding interoperation and better
> colorspace support. I don't think SDL3 can replace it directly.
Both should be in libavdevice, and ffplay should be using libavdevice
for its video and audio output.
Regards,
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2026-01-03 13:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 22:41 [FFmpeg-devel] " Marcin Serwin via ffmpeg-devel
2026-01-03 4:41 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2026-01-03 8:46 ` Marcin Serwin via ffmpeg-devel
2026-01-03 4:50 ` Gyan Doshi via ffmpeg-devel
2026-01-03 8:48 ` Marcin Serwin via ffmpeg-devel
2026-01-03 13:13 ` Nicolas George via ffmpeg-devel
2026-01-03 13:59 ` Neal Gompa via ffmpeg-devel
2026-01-03 14:29 ` Nicolas George via ffmpeg-devel
2026-01-03 5:40 ` Zhao Zhili via ffmpeg-devel
2026-01-03 7:12 ` Gyan Doshi via ffmpeg-devel
2026-01-03 8:59 ` Marcin Serwin via ffmpeg-devel
2026-01-03 12:59 ` Zhao Zhili via ffmpeg-devel
2026-01-03 13:12 ` Nicolas George via ffmpeg-devel [this message]
2026-01-03 15:14 ` Zhao Zhili via ffmpeg-devel
2026-01-03 15:16 ` Nicolas George via ffmpeg-devel
2026-01-03 15:39 ` Zhao Zhili via ffmpeg-devel
2026-01-03 15:50 ` Nicolas George 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=aVkVodBZ0Ut6h_gC@phare.normalesup.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=george@nsup.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