From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avfilter/split: switch to activate() Date: Sat, 5 Mar 2022 13:56:34 +0100 Message-ID: <CAPYw7P6WbXNU8jneTAi3OTJPa_Vq=rrhGBbOaj4ZFeYnR38mww@mail.gmail.com> (raw) In-Reply-To: <YiNDvA0MV7MaNRFA@phare.normalesup.org> On 3/5/22, Nicolas George <george@nsup.org> wrote: > Paul B Mahol (12022-03-04): >> No, wait must stop. >> >> The issue is that EOF is never reported if there is >1 frame left in >> queue before EOF for filters that do not use .activate (and use >1 >> inputs). > > Let me tell it one more time: > > split should not require switching to activate to work, including EOF. > There is a bug somewhere, and your analysis is not enough to know > exactly where. > > Until I understand what is going on exactly and if there is a framework > bug that needs fixing, I demand you hold. > Your patronizing and authoritarian tone is not helping you in any way. As you have no technical understanding in general and in this special case anyway, will gonna apply this working solution soon. Unless you provide clear and concise explanation why this should not be applied as is. My analysis was very clean, your ignorance and belittling tone is not helping at all. > -- > Nicolas George > _______________________________________________ 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:[~2022-03-05 12:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-01 13:27 Paul B Mahol 2022-03-03 18:30 ` Nicolas George 2022-03-03 20:58 ` Paul B Mahol 2022-03-04 13:13 ` Nicolas George 2022-03-04 22:49 ` Paul B Mahol 2022-03-05 11:04 ` Nicolas George 2022-03-05 12:56 ` Paul B Mahol [this message] 2022-03-05 19:37 ` Nicolas George 2022-03-06 14:08 ` 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='CAPYw7P6WbXNU8jneTAi3OTJPa_Vq=rrhGBbOaj4ZFeYnR38mww@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