From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Subject: [FFmpeg-devel] [PATCH] avfilter/fifo: Remove unused buffer frame
Date: Wed, 16 Feb 2022 07:02:33 +0100
Message-ID: <AM7PR03MB6660669417257EF473FE5C058F359@AM7PR03MB6660.eurprd03.prod.outlook.com> (raw)
Forgotten in 03c8fe49ea3f2a2444607e541dff15a1ccd7f0c2.
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
---
What is actually the use-case of these filters? The documentation states
that they are auto-inserted, yet this is no longer true any more since
4ca1fb9d2a91757c8c4c34dd456abf340e3f765f.
libavfilter/fifo.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/libavfilter/fifo.c b/libavfilter/fifo.c
index 1c7be88ae1..8b34055fde 100644
--- a/libavfilter/fifo.c
+++ b/libavfilter/fifo.c
@@ -38,13 +38,6 @@ typedef struct Buf {
typedef struct FifoContext {
Buf root;
Buf *last; ///< last buffered frame
-
- /**
- * When a specific number of output samples is requested, the partial
- * buffer is stored here
- */
- AVFrame *out;
- int allocated_samples; ///< number of samples out was allocated for
} FifoContext;
static av_cold int init(AVFilterContext *ctx)
@@ -65,8 +58,6 @@ static av_cold void uninit(AVFilterContext *ctx)
av_frame_free(&buf->frame);
av_free(buf);
}
-
- av_frame_free(&s->out);
}
static int add_to_queue(AVFilterLink *inlink, AVFrame *frame)
--
2.32.0
_______________________________________________
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 reply other threads:[~2022-02-16 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 6:02 Andreas Rheinhardt [this message]
2022-02-16 8:08 ` Paul B Mahol
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=AM7PR03MB6660669417257EF473FE5C058F359@AM7PR03MB6660.eurprd03.prod.outlook.com \
--to=andreas.rheinhardt@outlook.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