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 00:39:22 +0100
Message-ID: <20250328233922.GM4991@pb2> (raw)
In-Reply-To: <20250326201313.48298-1-koushd@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]
Hi
On Wed, Mar 26, 2025 at 01:13:13PM -0700, koushd@gmail.com wrote:
> From: Koushik Dutta <koushd@gmail.com>
>
> Not all rtp formats require the video dimensions to be available
> up front. H264 and HEVC will send them as stream parameters.
> The flag is restrictive and prevents RTP repacketization
> without parsing the codec information out of the stream.
>
> This change checks to see if the codec parameters are available
> on the rtp formats that need it.
>
> Signed-off-by: Koushik Dutta <koushd@gmail.com>
> ---
> libavformat/rtpenc.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
In general when muxing a stream, the dimensions are known
Can you explain what you are doing with rtpenc that lacks
known dimensions ?
is this some sort of low latency remuxing ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Some people wanted to paint the bikeshed green, some blue and some pink.
People argued and fought, when they finally agreed, only rust was left.
[-- 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".
next prev parent reply other threads:[~2025-03-28 23:39 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 [this message]
2025-03-29 6:30 ` Koushik Dutta
2025-03-29 21:49 ` Michael Niedermayer
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=20250328233922.GM4991@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