Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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/mpegtsenc: Limit TS invalid messages
Date: Sun, 5 Oct 2025 21:46:00 +0200
Message-ID: <aOLK-NyVsdwdWA82@neo> (raw)
In-Reply-To: <20251002213633.2515472-1-ddominguez@fagormultimedia.com>


[-- Attachment #1.1: Type: text/plain, Size: 1136 bytes --]

Hi

On Thu, Oct 02, 2025 at 11:36:33PM +0200, David Dominguez via ffmpeg-devel wrote:
> mpegts_write_pes() warns when DTS - PCR is negative. This is
> done to detect frames that are late for decoding, meaning that
> timestamping is wrong or the muxrate value is insufficient.
> 
> But this comparison only makes sense on the first packet of
> the frame. After that the comparison will always be negative
> as DTS doesn't change until the next frame, resulting in
> hundreds of useless warnings.
> 
> Addtionaly, for long key frames that take several frame periods
> to transmity false warnings may be issued if max_delay
> is low enough. For example, in low latency CC video.
> 
> Limiting the warning to the start of frame transmission fixes
> these issues.

This doesnt feel right, the time a frame is decoded has
to be after all of its parts are transmitted
But there are other people here, who know mpeg-ts much better than i
do

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The worst form of inequality is to try to make unequal things equal.
-- 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

  reply	other threads:[~2025-10-05 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 21:36 [FFmpeg-devel] " David Dominguez via ffmpeg-devel
2025-10-05 19:46 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-10-06  5:53   ` [FFmpeg-devel] " Kieran Kunhya 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=aOLK-NyVsdwdWA82@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 http://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/ http://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