Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/format: make experimental flag works for muxer
Date: Fri, 6 Jun 2025 11:00:35 +0100
Message-ID: <CABGuwE=s3gJm0xATQkmekCr5CZxu2pEsSPDbC7n3sE6VokrTqw@mail.gmail.com> (raw)
In-Reply-To: <20250606095109.GX29660@pb2>

On Fri, 6 Jun 2025, 10:51 Michael Niedermayer, <michael@niedermayer.cc>
wrote:

> On Fri, Jun 06, 2025 at 12:06:34AM +0800, Zhao Zhili wrote:
> > From: Zhao Zhili <zhilizhao@tencent.com>
> >
> > ---
> >  libavformat/avformat.h | 3 +--
> >  libavformat/format.c   | 2 ++
> >  2 files changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/libavformat/avformat.h b/libavformat/avformat.h
> > index 2034d2aecc..6edcf11022 100644
> > --- a/libavformat/avformat.h
> > +++ b/libavformat/avformat.h
> > @@ -470,8 +470,7 @@ typedef struct AVProbeData {
> >  /**
> >   * The muxer/demuxer is experimental and should be used with caution.
> >   *
> > - * - demuxers: will not be selected automatically by probing, must be
> specified
> > - *             explicitly.
> > + * Will not be selected automatically, must be specified explicitly.
> >   */
> >  #define AVFMT_EXPERIMENTAL  0x0004
> >  #define AVFMT_SHOW_IDS      0x0008 /**< Show format stream IDs numbers.
> */
> > diff --git a/libavformat/format.c b/libavformat/format.c
> > index 71018ea6ab..516925e7e4 100644
> > --- a/libavformat/format.c
> > +++ b/libavformat/format.c
> > @@ -95,6 +95,8 @@ const AVOutputFormat *av_guess_format(const char
> *short_name, const char *filena
> >      /* Find the proper file type. */
> >      score_max = 0;
> >      while ((fmt = av_muxer_iterate(&i))) {
> > +        if (fmt->flags & AVFMT_EXPERIMENTAL && !short_name)
> > +            continue;
>
> what does AVFMT_EXPERIMENTAL mean for a muxer ?
>
> * a muxer could generate invalid, non compliant data
> * a muxer could be insecure and exploitable
> * a muxer could lack some feature (iam sure most muxers in most projects
> lack some feature)
>
> I think the first 2 are reasons to use this flag
>

In the case of WebRTC it's 3. The user would expect it to work over the
internet (*Web*RTC after all) but it lacks NACK support so cannot recover
from any packet loss.

Without the experimental flag FFmpeg will get support tickets raised and
claims it is inferior to other implementations. Users will not be aware of
the lack of missing feature otherwise.

So it may be compliant on paper but it's not usable in the real world.

Kieran
_______________________________________________
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".

  reply	other threads:[~2025-06-06 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 16:06 Zhao Zhili
2025-06-05 16:09 ` James Almer
2025-06-05 16:21   ` Zhao Zhili
2025-06-06  4:44   ` [FFmpeg-devel] [PATCH v2] " Zhao Zhili
2025-06-08  1:31     ` Jack Lau
2025-06-06  9:51 ` [FFmpeg-devel] [PATCH] " Michael Niedermayer
2025-06-06 10:00   ` Kieran Kunhya via ffmpeg-devel [this message]
2025-06-06 11:27     ` 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='CABGuwE=s3gJm0xATQkmekCr5CZxu2pEsSPDbC7n3sE6VokrTqw@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    /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