From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [BROKEN] apad causes infinite hang Date: Mon, 17 Jun 2024 09:38:05 +0200 Message-ID: <CAPYw7P5ynwJd3kKXUDV9te7ODrtFBisb2Hz_kyQXE05QwcWb9g@mail.gmail.com> (raw) In-Reply-To: <171860906559.28895.327110577686261967@lain.khirnov.net> On Mon, Jun 17, 2024 at 9:24 AM Anton Khirnov <anton@khirnov.net> wrote: > Quoting Paul B Mahol (2024-06-14 14:19:13) > > Just try with: > > > > ffmpeg -f lavfi -i sine=d=30 -af apad -f null - > > > > Pressing 'q' will not stop it at all, because current ffmpeg code will > try > > to flush all frames, but because pad filter never receives EOF from next > > filter in chain (sink) it will happily produce frame forever. > > > > Tried to fix ffmpeg.c related code but quickly realized rewrite just made > > it 10 times worse to debug this. > > > > Most clean solution is adding av_buffersink_close() > > I think it would be cleaner to have an API for closing a _source_ (or > any filter that can produce unbounded amounts of output with no new > input). > What do you mean by closing a _source_ ? av_buffersrc_close() already exist. This bug is fixed in Librempeg. Adding a call to close random filter is certainly possible, but such approach is very frowned upon in multi-threaded environments. And once you close all buffersinks the EOF will and must propagate backward to all not-closed filters and their in/out pads. If there is better internal API for filters, feel free to present it to wider audience. > > -- > Anton Khirnov > _______________________________________________ > 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". > _______________________________________________ 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-06-17 7:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-14 12:19 Paul B Mahol 2024-06-17 7:24 ` Anton Khirnov 2024-06-17 7:38 ` Paul B Mahol [this message] 2024-06-17 18:06 ` Nicolas George
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=CAPYw7P5ynwJd3kKXUDV9te7ODrtFBisb2Hz_kyQXE05QwcWb9g@mail.gmail.com \ --to=onemda@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