From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avformat/movenc: Check that cts fits in 32bit Date: Sun, 31 Mar 2024 13:30:26 -0300 Message-ID: <6aa524e2-8686-4cc7-883c-30d281d9bcb0@gmail.com> (raw) In-Reply-To: <20240331114019.3801-1-michael@niedermayer.cc> On 3/31/2024 8:40 AM, Michael Niedermayer wrote: > Fixes: Assertion av_rescale_rnd(start_dts, mov->movie_timescale, track->timescale, AV_ROUND_DOWN) <= 0 failed at libavformat/movenc.c:3694 > Fixes: poc2 > > Found-by: Wang Dawei and Zhou Geng, from Zhongguancun Laboratory > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > --- > libavformat/movenc.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/libavformat/movenc.c b/libavformat/movenc.c > index ae94d8d5959..5617a2620c5 100644 > --- a/libavformat/movenc.c > +++ b/libavformat/movenc.c > @@ -6194,6 +6194,12 @@ int ff_mov_write_packet(AVFormatContext *s, AVPacket *pkt) > if (ret < 0) > return ret; > > + if (pkt->pts != AV_NOPTS_VALUE && > + (uint64_t)pkt->dts - pkt->pts != (int32_t)((uint64_t)pkt->dts - pkt->pts)) { > + av_log(s, AV_LOG_WARNING, "pts/dts pair unsupported\n"); > + return AVERROR_PATCHWELCOME; > + } Any such check should happen in check_pkt(), called directly above. And afaict there's no reason to not support 64bit cts. Even in mov_write_edts_tag() we check for it and write a version 1 of the box that supports 64bit values. Maybe the problem is that MOVIentry.cts is an int, when it should be an int64_t like start_cts? Can you test the following? > diff --git a/libavformat/movenc.h b/libavformat/movenc.h > index 08d580594d..e736c92750 100644 > --- a/libavformat/movenc.h > +++ b/libavformat/movenc.h > @@ -49,11 +49,11 @@ typedef struct MOVIentry { > uint64_t pos; > int64_t dts; > int64_t pts; > + int64_t cts; > unsigned int size; > unsigned int samples_in_chunk; > unsigned int chunkNum; ///< Chunk number if the current entry is a chunk start otherwise 0 > unsigned int entries; > - int cts; > #define MOV_SYNC_SAMPLE 0x0001 > #define MOV_PARTIAL_SYNC_SAMPLE 0x0002 > #define MOV_DISPOSABLE_SAMPLE 0x0004 _______________________________________________ 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:[~2024-03-31 16:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-31 11:40 Michael Niedermayer 2024-03-31 16:30 ` James Almer [this message] 2024-04-01 15:38 ` Michael Niedermayer 2024-04-01 15:45 ` James Almer 2024-04-01 16:53 ` 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=6aa524e2-8686-4cc7-883c-30d281d9bcb0@gmail.com \ --to=jamrial@gmail.com \ --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