From: muiz2 via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: muiz2 <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] mov demuxer: use int64_t for next_ts (PR #20313)
Date: Fri, 22 Aug 2025 04:05:46 +0300 (EEST)
Message-ID: <20250822010546.7AB8E6801F9@ffbox0-bg.ffmpeg.org> (raw)
PR #20313 opened by muiz2
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20313
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20313.patch
d1b96c380826c505a8c7e655b5ad4fdb0c2de167 fixes some hevc seeking issues
but will int overflow when timestamp is >int_max.
From eddaae989ef0fe6897274bb0662a42b43fd886dd Mon Sep 17 00:00:00 2001
From: Muiz Yusuff <muiz@google.com>
Date: Fri, 22 Aug 2025 01:01:48 +0000
Subject: [PATCH] mov demuxer: use int64_t for next_ts
d1b96c380826c505a8c7e655b5ad4fdb0c2de167 fixes some hevc seeking issues
but will int overflow when timestamp is >int_max.
---
libavformat/mov.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libavformat/mov.c b/libavformat/mov.c
index e9a582e5aa..ac0c01a67f 100644
--- a/libavformat/mov.c
+++ b/libavformat/mov.c
@@ -11299,7 +11299,8 @@ static int mov_seek_stream(AVFormatContext *s, AVStream *st, int64_t timestamp,
{
MOVStreamContext *sc = st->priv_data;
FFStream *const sti = ffstream(st);
- int sample, time_sample, ret, next_ts, requested_sample;
+ int sample, time_sample, ret, requested_sample;
+ int64_t next_ts;
unsigned int i;
// Here we consider timestamp to be PTS, hence try to offset it so that we
--
2.49.1
_______________________________________________
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".
reply other threads:[~2025-08-22 1:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250822010546.7AB8E6801F9@ffbox0-bg.ffmpeg.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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