From: Marco Vianini <marco_vianini-at-yahoo.it@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Request: make framepool visible externally
Date: Wed, 13 Jul 2022 15:59:19 +0000 (UTC)
Message-ID: <1678518970.1511817.1657727959267@mail.yahoo.com> (raw)
In-Reply-To: <e4f1f4e8-6d6c-7e21-18e2-1a4d18786d12@gmail.com>
On Wednesday, July 13, 2022 at 02:02:18 PM GMT+2, James Almer <jamrial@gmail.com> wrote:
On 7/13/2022 5:03 AM, Marco Vianini wrote:
> Actually I was speaking about framepool, and not bufferpool.
> framepool is intended to get an "AVFrame *" from a pool, by "ff_frame_pool_get".
> At the moment it is available only internally to "libavfilter".
> It permits an important improvement on performances, by using a pool. So it should be very nice if I could use it in my own code.
> To be possible framepool.h should become a public header.
> Thank You
Please, do not top post in this list.
I know you want AVFrames. What i mean is that you should use the
existing buffer pool API to achieve that. Write your own function that
returns a freshly allocated AVFrame that fills the buf[] and data[]
fields with buffers returned by av_buffer_pool_get() instead of
av_buffer_alloc().
_______________________________________________
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".
Sorry, I misunderstood what you mean with previous answer.
However Yes, surely I can write my own code (replicating what already done by framepool).
Thank You
_______________________________________________
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".
prev parent reply other threads:[~2022-07-13 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1645351900.763634.1657643310996.ref@mail.yahoo.com>
2022-07-12 16:28 ` Marco Vianini
2022-07-12 17:15 ` Timo Rothenpieler
2022-07-13 8:21 ` Marco Vianini
2022-07-12 17:19 ` James Almer
2022-07-13 8:03 ` Marco Vianini
2022-07-13 12:01 ` James Almer
2022-07-13 15:59 ` Marco Vianini [this message]
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=1678518970.1511817.1657727959267@mail.yahoo.com \
--to=marco_vianini-at-yahoo.it@ffmpeg.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