From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avdevice/lavfi: output wrapped AVFrames
Date: Sat, 2 Jul 2022 10:54:52 +0200
Message-ID: <20220702085452.GZ396728@pb2> (raw)
In-Reply-To: <20220630152206.15366-1-timo@rothenpieler.org>
[-- Attachment #1.1: Type: text/plain, Size: 1303 bytes --]
On Thu, Jun 30, 2022 at 05:22:06PM +0200, Timo Rothenpieler wrote:
> This avoids an extra copy of potentially quite big video frames.
> Instead of copying the entire frames data into a rawvideo packet it
> packs the frame into a wrapped avframe packet and passes it through
> as-is.
> Unfortunately, wrapped avframes are set up to be video frames, so the
> audio frames unfortunately continue to be copied.
>
> Additionally, this enabled passing through video frames that previously
> were impossible to process, like hardware frames or other special
> formats that couldn't be packed into a rawvideo packet.
> ---
> libavdevice/lavfi.c | 87 +++++++++--------------
> tests/ref/fate/filter-metadata-cropdetect | 3 +-
> 2 files changed, 36 insertions(+), 54 deletions(-)
seems to get this stuck:
./ffmpeg -f lavfi -i 'amovie=fate-suite/wavpack/num_channels/eva_2.22_6.1_16bit-partial.wv,asplit=3[out1][a][b]; [a]showwaves=s=340x240,pad=iw:ih*2[waves]; [b]showspectrum=s=340x240[spectrum]; [waves][spectrum] overlay=0:h [out0]' file-waves.avi
(stuck as in OOM killed)
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Nations do behave wisely once they have exhausted all other alternatives.
-- Abba Eban
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-07-02 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 15:22 Timo Rothenpieler
2022-07-02 8:54 ` Michael Niedermayer [this message]
2022-07-02 12:34 ` Paul B Mahol
2022-07-02 12:44 ` Michael Niedermayer
2022-07-05 11:26 ` Timo Rothenpieler
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=20220702085452.GZ396728@pb2 \
--to=michael@niedermayer.cc \
--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