Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] fftools/ffmpeg and libavdevice/sdl issue
Date: Thu, 14 Dec 2023 01:47:44 +0100
Message-ID: <ZXpQsKbNogNlor3i@mariano> (raw)
In-Reply-To: <170245852534.8914.12550775596488175101@lain.khirnov.net>

On date Wednesday 2023-12-13 10:08:45 +0100, Anton Khirnov wrote:
> Quoting Zhao Zhili (2023-12-12 18:27:39)
[...]
> Honestly I don't see how this could be done in ffmpeg CLI without
> disgusting hacks, but before that the question is:

> why is there an SDL
> "muxer" and why would anyone want to use it in ffmpeg CLI? What actual
> use cases does it serve that cannot be better handled otherwise?

As the author of the first sdl.c muxer, maybe I can answer to this
question. It was done partly as an exercise and for fun, but also
because this was useful extremely handy for testing (e.g. to display
the output of a filterchain from ffmpeg, or to display a streamed
video in realtime).

The final goal was (still is) to unify all the tools as very thin
instances of the library. Even if this might be not practical, I think
it is a good final design plan (e.g. ffprobe might be turned to a
custom muxer, ffplay would be the realtime output of a filtergraph
connected to a rendering device, ffmpeg would be a data filtergraph
processor, and you can mix rendering and encoding if you add a movie
sink to the game).
_______________________________________________
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".

  parent reply	other threads:[~2023-12-14  0:47 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 [this message]
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
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=ZXpQsKbNogNlor3i@mariano \
    --to=stefasab@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