From: Nicolas Gaullier <nicolas.gaullier@cji.paris> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avfilter/framesync: fix forward EOF pts Date: Thu, 23 May 2024 14:39:49 +0000 Message-ID: <MR1P264MB248303CAE8DBE69F2466C4C09BF42@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM> (raw) In-Reply-To: <20240521193836.136062-1-nicolas.gaullier@cji.paris> >Envoyé : mardi 21 mai 2024 21:39 > >Note1: when the EOF pts is not accurate enough, the last frame can be dropped by vf_fps with default rounding. > >Note2: vf_scale use framesync since e82a3997cdd6c0894869b33ba42430ac3, >so this is a very commonplace scenario. > >For example: >./ffprobe -f lavfi testsrc=d=1,scale,fps -of flat \ > -count_frames -show_entries stream=nb_read_frames > >Before: >streams.stream.0.nb_read_frames="24" > >After: >streams.stream.0.nb_read_frames="25" >--- > libavfilter/framesync.c | 23 +++++++++++------------ > 1 file changed, 11 insertions(+), 12 deletions(-) Ping ? Here is another straight way to highlight the issue with a format filter auto-inserting a scale filter thus implying framesync: >ffprobe -v debug -f lavfi testsrc=d=1,format=yuv420p,fps -count_frames shows: Before: [auto_scale_0 @ X] [framesync @ X] Sync level 0 [Parsed_fps_2 @ X] EOF is at pts 24 [Parsed_fps_2 @ X] Dropping frame with pts 24 [Parsed_fps_2 @ X] 25 frames in, 24 frames out; 1 frames dropped, 0 frames duplicated. After: [auto_scale_0 @ X] [framesync @ X] Sync level 0 [Parsed_fps_2 @ X] EOF is at pts 25 [Parsed_fps_2 @ X] Writing frame with pts 24 to pts 24 [Parsed_fps_2 @ X] 25 frames in, 25 frames out; 0 frames dropped, 0 frames duplicated. _______________________________________________ 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".
prev parent reply other threads:[~2024-05-23 14:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-21 19:38 Nicolas Gaullier 2024-05-23 14:39 ` Nicolas Gaullier [this message]
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=MR1P264MB248303CAE8DBE69F2466C4C09BF42@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM \ --to=nicolas.gaullier@cji.paris \ --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