From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 4/4 v2] avcodec/h264dec: add support for LCEVC enhancement
Date: Fri, 26 Jul 2024 09:21:21 -0300
Message-ID: <6d919c4c-d89f-4c62-ab29-4a3e15066d3c@gmail.com> (raw)
In-Reply-To: <172199637808.21344.1103797707765183066@lain.khirnov.net>
On 7/26/2024 9:19 AM, Anton Khirnov wrote:
> Quoting James Almer (2024-07-26 14:10:46)
>> On 7/26/2024 4:55 AM, Anton Khirnov wrote:
>>> Quoting James Almer (2024-07-22 00:53:50)
>>>> Signed-off-by: James Almer <jamrial@gmail.com>
>>>> ---
>>>> configure | 2 +-
>>>> libavcodec/avcodec.h | 5 +++++
>>>> libavcodec/h264_picture.c | 1 +
>>>> libavcodec/h264_slice.c | 15 ++++++++++++++
>>>> libavcodec/h264dec.c | 41 ++++++++++++++++++++++++++++++++++++---
>>>> libavcodec/h264dec.h | 3 +++
>>>> 6 files changed, 63 insertions(+), 4 deletions(-)
>>>
>>> Does this need to be integrated into individual decoders? Can't the
>>> generic path apply it based on the presence of AV_FRAME_DATA_LCEVC sdide
>>> data and AV_CODEC_EXPORT_DATA_ENHANCEMENTS being set?
>>
>> Individual decoders still need to be aware of lcevc metadata being
>> present to do things like allocating the output frame, because afaik i
>> can't call get_buffer2() from the main/user thread. So is it worth
>> moving things to the generic code when DR1 decoders will still need
>> extra considerations?
>
> Can it not be handled in ff_get_buffer()? And even if not - there'd
> still be a lot less code that needs to be duplicated across every
> decoder supporting this.
I'll try that.
_______________________________________________
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:[~2024-07-26 12:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 22:53 [FFmpeg-devel] [PATCH 1/4 v2] avutil/frame: add an LCEVC enhancement data payload side data type James Almer
2024-07-21 22:53 ` [FFmpeg-devel] [PATCH 2/4 v2] libavcodec/h2645_sei: export raw LCEVC metadata James Almer
2024-07-22 0:02 ` Lynne via ffmpeg-devel
2024-07-22 0:14 ` James Almer
2024-07-21 22:53 ` [FFmpeg-devel] [PATCH 3/4 v2] avcodec: add LCEVC decoding support via LCEVCdec James Almer
2024-07-22 11:16 ` Frank Plowman
2024-07-21 22:53 ` [FFmpeg-devel] [PATCH 4/4 v2] avcodec/h264dec: add support for LCEVC enhancement James Almer
2024-07-26 7:55 ` Anton Khirnov
2024-07-26 12:10 ` James Almer
2024-07-26 12:19 ` Anton Khirnov
2024-07-26 12:21 ` James Almer [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=6d919c4c-d89f-4c62-ab29-4a3e15066d3c@gmail.com \
--to=jamrial@gmail.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