From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v1 8/8] avcodec/apv_decoder: Provided support for APV decoder
Date: Thu, 24 Apr 2025 20:23:04 +0100
Message-ID: <c864bdc9-6615-43e1-b14e-ef53dfb342dc@jkqxz.net> (raw)
In-Reply-To: <20250423141341.1858303-1-d.kozinski@samsung.com>
On 23/04/2025 15:13, Dawid Kozinski wrote:
> - Added APV decoder wrapper
> - Changes in project configuration file and libavcodec Makefile
> - Added documentation for APV decoder wrapper
>
> Signed-off-by: Dawid Kozinski <d.kozinski@samsung.com>
> ---
> configure | 1 +
> doc/decoders.texi | 27 ++
> libavcodec/Makefile | 1 +
> libavcodec/libapvdec.c | 560 +++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 589 insertions(+)
> create mode 100644 libavcodec/libapvdec.c
>
> ...
This is asking the decoder library to decode all of the frames (primary/non-primary/preview/depth/alpha) found in the access unit, putting the resulting frames in a fifo, and then outputting them one at a time to receive_frame.
What is the aim there and what does the user need to do to achieve it? For typical existing lavc users (such as the ffmpeg utility) this seems likely to be very confusing, as all of the frames will be bunched together in the same stream even though they don't have the same meaning or (likely) the same properties.
For my decoder implementation I am currently outputting only the primary frame, and would appreciate if you have any thoughts on what the right thing to do if there are multiple frames in the access unit is.
I considered decoding an alpha frame and merging it with the primary frame to form a YUVA422P10 frame, but this seemed fragile as the specification places no constraints on the alpha frame (e.g. no requirement that it is 4:0:0 and has the same dimensions as the primary frame) so I decided against including it.
For the other types I have no thoughts on what might be useful and therefore currently ignore them.
Thanks,
- Mark
PS: Are there any official samples with multiple frames? Examples which I didn't make myself would be appreciated for test purposes.
_______________________________________________
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:[~2025-04-24 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250423141345eucas1p1784ac4af60429d8d8dbc0c7018fd9fc0@eucas1p1.samsung.com>
2025-04-23 14:13 ` Dawid Kozinski
2025-04-24 19:23 ` Mark Thompson [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=c864bdc9-6615-43e1-b14e-ef53dfb342dc@jkqxz.net \
--to=sw@jkqxz.net \
--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