From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] avdevice/lavfi: output wrapped AVFrames
Date: Sat, 2 Jul 2022 22:06:19 +0200
Message-ID: <b53e9539-0c68-d398-6f66-af0339f6bb66@rothenpieler.org> (raw)
In-Reply-To: <YsB/uqE1CQe/XXE3@phare.normalesup.org>
On 02.07.2022 19:26, Nicolas George wrote:
> It is already possible.
Yeah, I noticed that shortly after.
Never before thought to run ffmpeg.c without any inputs, but as long as
you stick to -filter_complex instead of plain -filter, it works great.
> But this device is not meant for ffmpeg.c alone.
>
> It has been explained time and again that libavdevice is useful for
> users of applications that are designed to expect a demuxer, to make
> them use something more exotic than a demuxer.
I never doubted that, though in my case writing the input as a filter
makes a ton more sense, cause filters are a lot better integrated with
the whole hwaccel framework.
With this patch applied, it works via lavfi.c, but you have no control
over the created hwdevice context.
_______________________________________________
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 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 19:52 Timo Rothenpieler
2022-06-30 8:46 ` Anton Khirnov
2022-06-30 9:50 ` Timo Rothenpieler
2022-07-02 17:26 ` Nicolas George
2022-07-02 20:06 ` Timo Rothenpieler [this message]
2022-07-03 13:19 ` Nicolas George
2022-07-03 13:40 ` 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=b53e9539-0c68-d398-6f66-af0339f6bb66@rothenpieler.org \
--to=timo@rothenpieler.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