From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/rtpenc: Add flag AVFMT_NODIMENSIONS.
Date: Sat, 29 Mar 2025 22:49:24 +0100
Message-ID: <20250329214924.GR4991@pb2> (raw)
In-Reply-To: <CAO4LPj_nUcjKYMpcA5OFa1nzRH=ya-nU9V3AgpU-aVRca_B-Uw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 887 bytes --]
Hi Koushik
On Fri, Mar 28, 2025 at 11:30:05PM -0700, Koushik Dutta wrote:
> Yes, that’s what I am doing. I am repacketizing h264 and hevc without
> inspection of the stream itself. RTSP over tcp can transmit rtp packets up
> to 64k. Some cameras utilize this to reduce fragmentation overhead but
> those large packets need to be fragmented for udp rebroadcast on typical
> network mtu.
>
> I could inspect the stream for sps and then parse the dimensions out of
> there, or maybe set some dummy values on the rtp encoder somehow and work
> around this. But neither of those seemed like proper solutions given rtp
> doesn’t need to know the steam dimensions for all but 2 codecs.
ok, will apply
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Why not whip the teacher when the pupil misbehaves? -- Diogenes of Sinope
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
prev parent reply other threads:[~2025-03-29 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 20:13 koushd
2025-03-28 23:39 ` Michael Niedermayer
2025-03-29 6:30 ` Koushik Dutta
2025-03-29 21:49 ` Michael Niedermayer [this message]
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=20250329214924.GR4991@pb2 \
--to=michael@niedermayer.cc \
--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