From: "Jan Ekström" <jeebjp@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/2] avdevice: deprecate opengl outdev
Date: Mon, 26 Feb 2024 18:47:58 +0200
Message-ID: <CAEu79SYP+x_idHTWU8Fwoz+PJW-87BG4AsGO0D40u+rNY6i+zA@mail.gmail.com> (raw)
In-Reply-To: <20240221113356.203887-1-jdek@itanimul.li>
On Wed, Feb 21, 2024 at 1:34 PM J. Dekker <jdek@itanimul.li> wrote:
>
> Signed-off-by: J. Dekker <jdek@itanimul.li>
> ---
> doc/outdevs.texi | 2 +-
> libavdevice/opengl_enc.c | 11 +++++++++++
> libavdevice/version_major.h | 2 ++
> 3 files changed, 14 insertions(+), 1 deletion(-)
As during FOSDEM there seemed to be a consensus that we should move to
removing this, I agree with the idea behind this patch.
Additionally, both during FOSDEM as well as right now I successfully
built this module on Fedora 39 and tried `ffmpeg -v verbose -re -i
"https://megumin.fushizen.eu/videos/HidamariHoneycombED.mp4" -vf
scale=w=640:h=360,format=yuv420p -map 0:v -f sdl "SDL output"` and it
seems like while a 0x0 (?) window is created (without any decorations
- so you only notice it when you alt-tab), it does not seem to show up
on the desktop. So while it seemingly works with RGB input on Windows,
at least rgb24 didn't work on Fedora, either. yuyv422 and uyvy422
failed completely and the out device didn't take them in (which is
probably an SDL2 limitation?).
Regards,
Jan
_______________________________________________
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:[~2024-02-26 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 11:33 J. Dekker
2024-02-21 11:33 ` [FFmpeg-devel] [PATCH v2 2/2] avdevice: deprecate sdl outdev J. Dekker
2024-02-21 12:32 ` [FFmpeg-devel] [PATCH v2 1/2] avdevice: deprecate opengl outdev Lynne
2024-02-26 15:43 ` Anton Khirnov
2024-02-28 9:31 ` J. Dekker
2024-02-26 16:47 ` Jan Ekström [this message]
2024-02-27 1:42 ` Zhao Zhili
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=CAEu79SYP+x_idHTWU8Fwoz+PJW-87BG4AsGO0D40u+rNY6i+zA@mail.gmail.com \
--to=jeebjp@gmail.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