Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfillter/buffersrc: activate and EOF fix
Date: Thu, 2 Nov 2023 11:03:05 +0100
Message-ID: <ZUNz2Ua2Rc+PQ1lC@phare.normalesup.org> (raw)
In-Reply-To: <CAPYw7P6Uyjf-9M-empOvP-mZaLhfXUTjbYMPUXoWTvBg5BEnjg@mail.gmail.com>

Paul B Mahol (12023-11-02):
> I analyzed it already, It is very sorry state of libavfilter that buffersrc
> keeps sending frames to EOF filtergraph.

So, Paul, I will explain this to you one last time.

Remember high school, when you had math test, and if you just gave the
result you got almost no points even if the result was correct? That was
because solving a math exercise is not just about finding the result, it
is about showing how you reach the result and proving that the result is
correct.

The same goes here. On your own projects, you can change randomly the
code until a bug is no longer triggered and call it fixed.

But in FFmpeg, you are not alone, and when a change is not trivial you
have to prove to your fellow developers that it is correct and
necessary.

So get to work, produce that proof, re-submit the patch with the proof
in the commit message, and then we can talk.

As it is, the need to switch buffersrc to activate is not established,
and therefore it should not be done.

-- 
  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".

  reply	other threads:[~2023-11-02 10:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 12:38 Paul B Mahol
2023-10-27 12:53 ` Nicolas George
2023-10-27 13:07   ` Paul B Mahol
2023-10-27 13:02     ` Nicolas George
2023-10-27 13:18       ` Paul B Mahol
2023-10-27 17:51         ` Paul B Mahol
2023-10-27 17:54           ` Nicolas George
2023-10-27 22:48             ` Paul B Mahol
2023-10-29  9:38               ` Nicolas George
2023-10-29 21:46                 ` Paul B Mahol
2023-10-31 10:55     ` Nicolas George
2023-10-31 20:13       ` Paul B Mahol
2023-10-31 20:14         ` Paul B Mahol
2023-11-01 13:58         ` Nicolas George
2023-11-01 14:15           ` Paul B Mahol
2023-11-01 14:13             ` Nicolas George
2023-11-02  9:56               ` Paul B Mahol
2023-11-02  9:50                 ` Nicolas George
2023-11-02 10:00                   ` Paul B Mahol
2023-11-02 10:03                     ` Nicolas George [this message]
2023-11-02 10:18                       ` Paul B Mahol
2023-11-02 10:15                         ` Nicolas George
2023-11-02 20:05                         ` Tristan Matthews
2023-11-03 19:04                           ` Nicolas George
2023-11-03 20:47                             ` Paul B Mahol
2023-11-04 19:05                               ` Nicolas George
2023-11-01 13:48       ` Jan Ekström
2023-11-01 13:56         ` Nicolas George
2023-11-01 14:23           ` James Almer
2023-11-01 14:28             ` 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=ZUNz2Ua2Rc+PQ1lC@phare.normalesup.org \
    --to=george@nsup.org \
    --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