From: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Timo Rothenpieler <timo@rothenpieler.org>
Subject: [FFmpeg-devel] Re: [PATCH] lavf/whip: improve RTP muxer error message
Date: Thu, 22 Jan 2026 03:12:08 +0100
Message-ID: <a5e45d58-985f-4d6a-af38-6a0e24e013be@rothenpieler.org> (raw)
In-Reply-To: <CANX1iD8J5UH6VxDL_sRSaYiub0PeupBS=77grR0_6JwrUEF0aw@mail.gmail.com>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 422 bytes --]
On 20.01.2026 12:45, Devraj Ajmera via ffmpeg-devel wrote:
> Hello,
>
> This patch improves the error message shown when the RTP muxer
> cannot be guessed in the WHIP muxer, making the failure reason
> clearer to users.
Shouldn't this whole condition be returning AVERROR_BUG instead, and
configure have proper dependencies set, so that the whip muxer can't be
enabled without rtp, if it hard-depends on it?
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3203 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
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-22 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 11:45 [FFmpeg-devel] " Devraj Ajmera via ffmpeg-devel
2026-01-22 0:50 ` [FFmpeg-devel] " Jack Lau via ffmpeg-devel
2026-01-22 2:12 ` Timo Rothenpieler via ffmpeg-devel [this message]
2026-01-23 6:12 ` Devraj Ajmera via ffmpeg-devel
2026-01-23 6:31 ` Devraj Ajmera via ffmpeg-devel
2026-01-23 7:27 ` Jack Lau via ffmpeg-devel
2026-01-24 15:34 ` Devraj Ajmera via ffmpeg-devel
2026-01-30 5:32 ` Devraj Ajmera via ffmpeg-devel
2026-01-30 8:28 ` Jack Lau via ffmpeg-devel
2026-01-30 12:05 ` Devraj Ajmera via ffmpeg-devel
2026-02-11 7:04 ` Devraj Ajmera via ffmpeg-devel
2026-02-11 8:29 ` Jack Lau 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=a5e45d58-985f-4d6a-af38-6a0e24e013be@rothenpieler.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=timo@rothenpieler.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