From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FFmpeg 5.1
Date: Fri, 8 Jul 2022 12:17:51 +0200
Message-ID: <7e75ad2c-584e-6acc-dc15-89850c4af774@rothenpieler.org> (raw)
In-Reply-To: <5a3163b7-e80a-0a51-6fc4-e793285cf908@gmail.com>
> The lavfi changes, more specifically wrapped_avframe, still rely on
> sizeof(AVFrame) being used outside lavu. We really need to stop
> spreading its use and find a way to change this behavior.
> I have tried like two different solutions and both were rejected, so
> it's not going to be me.
wrapped_avframe is used all over the place in lavd already.
Is that really a problem, as long as it's within another libav* library?
Given we don't support mix-matching library versions in the first place.
The only real way around that would be a get_size function in lavu, and
never using AVFrames on the stack, which is done in quite a lot of places.
_______________________________________________
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-08 10:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 11:35 Michael Niedermayer
2022-06-09 18:13 ` Neal Gompa
2022-06-19 20:59 ` Marton Balint
2022-06-20 0:22 ` Neal Gompa
2022-07-07 22:52 ` Marton Balint
2022-07-07 20:47 ` Michael Niedermayer
2022-07-07 20:51 ` Timo Rothenpieler
2022-07-07 20:54 ` James Almer
2022-07-08 10:17 ` Timo Rothenpieler [this message]
2022-07-08 10:23 ` Timo Rothenpieler
2022-07-08 11:49 ` James Almer
2022-07-08 8:36 ` Jean-Baptiste Kempf
2022-07-08 8:52 ` Paul B Mahol
2022-07-08 13:52 ` Michael Niedermayer
2022-07-08 14:54 ` Leo Izen
2022-07-09 17:17 ` Andreas Rheinhardt
2022-07-21 17:09 ` Michael Niedermayer
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=7e75ad2c-584e-6acc-dc15-89850c4af774@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