From: Devraj Ajmera via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Devraj Ajmera <devrajajmera077@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] lavf/whip: improve RTP muxer error message
Date: Fri, 30 Jan 2026 17:35:47 +0530
Message-ID: <CANX1iD9ys-xS1HyJsOfhPHDqotdWiBuOckk4kLNW29t01iRpiA@mail.gmail.com> (raw)
In-Reply-To: <CANX1iD-yv0fgHGT+9RnZoJi6o4_PH9csGbamXwohM-T94rui8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3072 bytes --]
> I think the av_unreachable() should be used with a reason
>
> So maybe av_unreachable("RTP muxer should be enabled");
>
> BTW, it seems you use wrong indent here.
Thanks for the suggestion.
I have updated the code to use av_unreachable() with an explicit
reason string, and fixed the indentation to match the existing
FFmpeg style.
An updated patch reflecting these changes has been generated
and sent.
Regards,
Devraj
On Fri, Jan 30, 2026 at 11:02 AM Devraj Ajmera <devrajajmera077@gmail.com>
wrote:
> > configure already deps the rtp_muxer via whip_muxer_select, so it should
> never hit this error.
>
> > So maybe use av_unreachable() to replace current error handling?
>
> That makes sense. Since configure already enforces the RTP dependency via
> whip_muxer_select, this code path should indeed be unreachable at runtime.
>
> I have updated the code to replace the current error handling with
> av_unreachable() accordingly, and will send an updated patch reflecting
> this change.
>
> Regards,
> Devraj
>
> On Sat, Jan 24, 2026 at 9:04 PM Devraj Ajmera <devrajajmera077@gmail.com>
> wrote:
>
>> Hi Jack,
>>
>> > configure already deps the rtp_muxer via whip_muxer_select, so it
>> should never hit this error.
>> > So maybe use av_unreachable() to replace current error handling?
>>
>> That makes sense. If configure already enforces the RTP dependency via
>> whip_muxer_select, then this code path should indeed be unreachable.
>>
>> Using av_unreachable() here sounds reasonable. I will prepare an updated
>> patch replacing the current error handling accordingly.
>>
>> Noted.
>>
>> Regards,
>> Devraj
>>
>> On Fri, Jan 23, 2026 at 12:01 PM Devraj Ajmera <devrajajmera077@gmail.com>
>> wrote:
>>
>>> Hi Timo,
>>>
>>> Thanks for the insightful comment.
>>>
>>> You are right that if WHIP hard-depends on RTP, this might be better
>>> handled at configure time rather than at runtime. The intent of this
>>> patch was limited to improving the clarity of the existing error path,
>>> without changing behavior.
>>>
>>> I agree this deserves a closer look. Would you prefer addressing this
>>> by tightening the configure dependencies for the WHIP muxer, or by
>>> adjusting the error handling (e.g. AVERROR_BUG) in this code path?
>>>
>>> Thanks,
>>> Devraj
>>>
>>> On Fri, Jan 23, 2026 at 11:42 AM Devraj Ajmera <
>>> devrajajmera077@gmail.com> wrote:
>>>
>>>> Hi Jack,
>>>>
>>>> Thanks for the review.
>>>>
>>>> You are right, the "WHIP:" prefix is unnecessary since av_log already
>>>> has context.
>>>> I have updated the patch accordingly and sent a revised version.
>>>>
>>>> Regards,
>>>> Devraj Ajmera
>>>>
>>>> On Tue, Jan 20, 2026 at 5:15 PM Devraj Ajmera <
>>>> devrajajmera077@gmail.com> 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.
>>>>>
>>>>> Regards,
>>>>> Devraj Ajmera
>>>>>
>>>>
[-- Attachment #2: 0001-lavf-whip-mark-RTP-muxer-lookup-as-unreachable.patch --]
[-- Type: application/octet-stream, Size: 1157 bytes --]
[-- Attachment #3: 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-30 12:06 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
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 [this message]
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=CANX1iD9ys-xS1HyJsOfhPHDqotdWiBuOckk4kLNW29t01iRpiA@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=devrajajmera077@gmail.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