From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [PATCH] avformat/rtpenc: use unsigned type for ssrc option
Date: Fri, 27 Feb 2026 01:15:30 +0100
Message-ID: <aaDiIqxBZMMOjJW4@neo> (raw)
In-Reply-To: <SY8P300MB034845458FFAD335144E15FE8368A@SY8P300MB0348.AUSP300.PROD.OUTLOOK.COM>
[-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --]
On Fri, Feb 20, 2026 at 08:24:08PM +0000, NEKO ASAKURA via ffmpeg-devel wrote:
> The ssrc option used AV_OPT_TYPE_INT with range [INT_MIN, INT_MAX],
> but the underlying struct field is uint32_t and RFC 3550 defines SSRC
> as a 32-bit identifier covering the full [0, UINT32_MAX] range. This
> caused ffmpeg to reject any SSRC value above INT_MAX (~2.1 billion),
> which is roughly half of all valid values.
>
> The auto-generated fallback path (av_get_random_seed()) already
> returns uint32_t and can produce values above INT_MAX, creating an
> inconsistency where the automatic path succeeds but the explicit
> -ssrc option rejects the same value.
>
> Change the option to AV_OPT_TYPE_UINT with range [0, UINT32_MAX]
> to match the field type and allow the full identifier space.
>
> Fixes ticket #9080.
>
> Signed-off-by: Neko Asakura <neko.asakura@outlook.com>
> ---
> libavformat/rtpenc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
will be applied as soon as someone approves: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22302/commits
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The educated differ from the uneducated as much as the living from the
dead. -- Aristotle
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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-02-27 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 20:24 [FFmpeg-devel] " NEKO ASAKURA via ffmpeg-devel
2026-02-27 0:15 ` Michael Niedermayer via ffmpeg-devel [this message]
2026-02-27 1:16 ` [FFmpeg-devel] " 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=aaDiIqxBZMMOjJW4@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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