From: David Dominguez via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: David Dominguez <ddominguez@fagormultimedia.com> Subject: [FFmpeg-devel] [PATCH] avformat/mpegtsenc: Limit TS invalid messages Date: Thu, 2 Oct 2025 23:36:33 +0200 Message-ID: <20251002213633.2515472-1-ddominguez@fagormultimedia.com> (raw) 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. Signed-off-by: David Dominguez <ddominguez@fagormultimedia.com> --- libavformat/mpegtsenc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavformat/mpegtsenc.c b/libavformat/mpegtsenc.c index 6935b71cfe..d66055e1dc 100644 --- a/libavformat/mpegtsenc.c +++ b/libavformat/mpegtsenc.c @@ -1596,7 +1596,7 @@ static void mpegts_write_pes(AVFormatContext *s, AVStream *st, set_af_flag(buf, 0x10); q = get_ts_payload_start(buf); // add 11, pcr references the last byte of program clock reference base - if (dts != AV_NOPTS_VALUE && dts < pcr / SYSTEM_CLOCK_FREQUENCY_DIVISOR) + if (is_start && dts != AV_NOPTS_VALUE && dts < pcr / SYSTEM_CLOCK_FREQUENCY_DIVISOR) av_log(s, AV_LOG_WARNING, "dts < pcr, TS is invalid\n"); extend_af(buf, write_pcr_bits(q, pcr)); q = get_ts_payload_start(buf); -- 2.34.1 _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next reply other threads:[~2025-10-02 21:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-10-02 21:36 David Dominguez via ffmpeg-devel [this message] 2025-10-05 19:46 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel 2025-10-06 5:53 ` 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=20251002213633.2515472-1-ddominguez@fagormultimedia.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=ddominguez@fagormultimedia.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 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