From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] fftools/ffmpeg and libavdevice/sdl issue
Date: Tue, 19 Dec 2023 20:48:39 +0200
Message-ID: <2528070.x0Nq1CDqbv@basile.remlab.net> (raw)
In-Reply-To: <20231219165840.GY6420@pb2>
Le tiistaina 19. joulukuuta 2023, 18.58.40 EET Michael Niedermayer a écrit :
> so the idea is that we cannot access any GUI in any code from anything in
> libavformat and probably all other libs, ever
No. The idea is that a command line program cannot use the GUI, and a library
can only use the GUI if the main program is a GUI program.
> no debug with graphical output
> no vissualizuation of anything
> no devices
> no libs that expose anything that would need a GUI for configuration
You can do all those things as long as you assume that the main program is a
GUI program running the Mac-specific UI main loop. AFAICT, you can write a
macOS OpenGL or Metal video output device and a CoreAudio audio output device,
and any GUI program that uses FFmpeg can then use those devices.
Trying to fit this into a generic portable command line tool is not going to
work though. Then SDL adds the extra problem that it probably only works with
its own API driving the main loop, and not just any API layered on top of Mac
GUI frameworks. If so, the only proper way to support it (on Mac) is to make a
dedicated player. Of course, it's also possible to skip support for SDL on
Mac.
Lastly, it has been made clear by the proponents of the muxer that this is but
a convenient trick so that a real muxer can be swapped for a renderer wherever
a muxer is expected. In other words, it is a literal kludge (from the
wiktionary: "Any construction or practice, typically crude yet effective,
designed to solve a problem temporarily or expediently"). That's pretty much
the antithesis of good and sound API design.
--
Rémi Denis-Courmont
http://www.remlab.net/
_______________________________________________
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-12-19 18:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 17:27 Zhao Zhili
2023-12-12 18:04 ` Nicolas George
2023-12-13 4:19 ` Zhao Zhili
2023-12-13 17:30 ` [FFmpeg-devel] Mailinglist conduct [was: [RFC] fftools/ffmpeg and libavdevice/sdl issue] Ronald S. Bultje
2023-12-13 9:08 ` [FFmpeg-devel] [RFC] fftools/ffmpeg and libavdevice/sdl issue Anton Khirnov
2023-12-13 9:31 ` Zhao Zhili
2023-12-13 10:06 ` Anton Khirnov
2023-12-13 10:37 ` Zhao Zhili
2023-12-13 10:45 ` Nicolas George
2023-12-13 10:49 ` Anton Khirnov
2023-12-13 9:44 ` Nicolas George
2023-12-14 0:47 ` Stefano Sabatini
2023-12-14 7:48 ` Anton Khirnov
2023-12-14 9:35 ` Nicolas George
2023-12-16 15:18 ` Stefano Sabatini
2023-12-18 17:33 ` Anton Khirnov
2023-12-18 19:58 ` Michael Niedermayer
2023-12-18 20:02 ` Nicolas George
2023-12-19 7:23 ` Rémi Denis-Courmont
2023-12-19 9:29 ` Nicolas George
2023-12-19 10:43 ` Rémi Denis-Courmont
2023-12-19 12:51 ` Nicolas George
2023-12-19 14:47 ` Rémi Denis-Courmont
2023-12-19 16:58 ` Michael Niedermayer
2023-12-19 18:48 ` Rémi Denis-Courmont [this message]
2023-12-19 18:55 ` Nicolas George
2023-12-19 19:36 ` Michael Niedermayer
2023-12-15 12:37 ` Alexander Strasser 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=2528070.x0Nq1CDqbv@basile.remlab.net \
--to=remi@remlab.net \
--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