From: Nicolas Gaullier <nicolas.gaullier@cji.paris>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 0/1] avfilter/framesync: fix forward EOF pts
Date: Mon, 8 Jul 2024 12:36:38 +0000
Message-ID: <MR1P264MB2483FE16333BDD2DF8AAA2169BDA2@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <MR1P264MB2483B06B08378E39527112959BC22@MR1P264MB2483.FRAP264.PROD.OUTLOOK.COM>
>Envoyé : vendredi 14 juin 2024 13:27
>>Envoyé : lundi 3 juin 2024 12:00
>>>Envoyé : mardi 28 mai 2024 11:11
>>>
>>>This a new ping but I post the patch again to get fate cleanly completed on patchwork.
>>>
>>https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=11939
>
>To summarize, and for remembering, the initial commit was 4e0e9ce2dc, 7 years ago, and inserted this:
>ff_outlink_set_status(fs->parent->outputs[0], AVERROR_EOF, AV_NOPTS_VALUE)
>The target of this patch is to make it a:
>ff_outlink_set_status(fs->parent->outputs[0], AVERROR_EOF, eof_pts)
>
>My use case is that I frequently chain the scale filter with the fps filter, and since the scale filter uses framesync since e82a3997cdd6c0 (3rd of May this year), this is becoming a "full" issue
Pinging again, the patch still applies...
Thank you
Nicolas
_______________________________________________
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-07-08 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 9:11 Nicolas Gaullier
2024-05-28 9:11 ` [FFmpeg-devel] [PATCH 1/1] " Nicolas Gaullier
2024-06-03 10:00 ` [FFmpeg-devel] [PATCH 0/1] " Nicolas Gaullier
2024-06-14 11:26 ` Nicolas Gaullier
2024-07-08 12:36 ` Nicolas Gaullier [this message]
2024-07-17 10:09 ` Anton Khirnov
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=MR1P264MB2483FE16333BDD2DF8AAA2169BDA2@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