From: Muhammad Faiz <mfcc64@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter/fifo: Remove (a)fifo filters
Date: Sun, 10 Mar 2024 05:37:53 +0700
Message-ID: <CAJsO9v5NAVMJ=XATr-L+2xrHQG5KLssLkbTbmAMqbdTinWmELw@mail.gmail.com> (raw)
In-Reply-To: <CAPYw7P4r_Rqs8-qOZGojuDRPbz=N+r-yLpfoqjSnCXp-OF7mGg@mail.gmail.com>
On Sat, Mar 9, 2024 at 6:11 PM Paul B Mahol <onemda@gmail.com> wrote:
> On Sat, Mar 9, 2024 at 2:09 AM Muhammad Faiz <mfcc64@gmail.com> wrote:
>
> > On Fri, Mar 8, 2024 at 10:30 PM Paul B Mahol <onemda@gmail.com> wrote:
> >
> > > On Fri, Mar 8, 2024 at 4:18 PM Muhammad Faiz <mfcc64@gmail.com> wrote:
> > >
> > > > On Fri, Mar 8, 2024 at 5:40 PM Andreas Rheinhardt <
> > > > andreas.rheinhardt@outlook.com> wrote:
> > > >
> > > > > Muhammad Faiz:
> > > > > > On Tue, Feb 6, 2024 at 3:58 PM Andreas Rheinhardt <
> > > > > > andreas.rheinhardt@outlook.com> wrote:
> > > > > >
> > > > > >> Andreas Rheinhardt:
> > > > > >>> Obsolete since 4ca1fb9d2a91757c8c4c34dd456abf340e3f765f.
> > > > > >>>
> > > > > >>> Signed-off-by: Andreas Rheinhardt <
> > andreas.rheinhardt@outlook.com>
> > > > > >>> ---
> > > > > >>> doc/filters.texi | 9 ---
> > > > > >>> libavfilter/Makefile | 1 -
> > > > > >>> libavfilter/allfilters.c | 2 -
> > > > > >>> libavfilter/fifo.c | 165
> > > > ---------------------------------------
> > > > > >>> 4 files changed, 177 deletions(-)
> > > > > >>> delete mode 100644 libavfilter/fifo.c
> > > > > >>>
> > > > > >>
> > > > > >> Will apply in a few days unless there are objections.
> > > > > >>
> > > > > >> - Andreas
> > > > > >>
> > > > > >>
> > > > > > This breaks backward compatibility.
> > > > > >
> > > > > > Please revert.
> > > > > >
> > > > > > Thank's.
> > > > >
> > > > > What breaks that can't simply be fixed by removing the (a)fifo
> filter
> > > > > from the filterchain?
> > > > >
> > > > > - Andreas
> > > > >
> > > > >
> > > > I use afifo to optimize memory usage.
> > > >
> > >
> > > That statement sync with reality is questionable, fifo filters were
> > mainly
> > > used before .activate was added,
> > > for cases filters used >1 inputs. Now they should be irrelevant, unless
> > > there are bugs in code than this filters just hide more bugs.
> > >
> >
> > Yes, I've used it before .activate was added, and it worked, and still
> > works.
> > Although maybe the bugs have been fixed by .activate, what's wrong if
> > (a)fifo still exist?
> >
>
> As already wrote, lets repeat it again, hiding real bugs. Hiding is not
> correct word,
> it just adds yet another layer in filtergraph to accumulate memory/frames,
> with extra allocations per each frame for linking between prev and next
> frame.
> Which is pointless, as libavfilter internal code already have own queue
> mechanism.
> Check for which filters used after afifo, afifo count of queued frames
> reach > 1 than
> such filters needs fixing. Personally, my mpv visualizer modified script is
> not using afifo filters, and it works fine.
>
>
OK
Thank's
_______________________________________________
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-03-09 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 13:51 Andreas Rheinhardt
2024-02-06 9:00 ` Andreas Rheinhardt
2024-03-08 8:46 ` Muhammad Faiz
2024-03-08 10:40 ` Andreas Rheinhardt
2024-03-08 15:18 ` Muhammad Faiz
2024-03-08 15:29 ` Paul B Mahol
2024-03-09 1:08 ` Muhammad Faiz
2024-03-09 11:10 ` Paul B Mahol
2024-03-09 22:37 ` Muhammad Faiz [this message]
2024-03-08 15:31 ` Andreas Rheinhardt
2024-03-09 0:38 ` Muhammad Faiz
2024-03-09 11:59 ` Andreas Rheinhardt
2024-03-09 22:36 ` Muhammad Faiz
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='CAJsO9v5NAVMJ=XATr-L+2xrHQG5KLssLkbTbmAMqbdTinWmELw@mail.gmail.com' \
--to=mfcc64@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