From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v1 2/8] avcodec/apv_parser: Added parser implementation for APV format
Date: Wed, 23 Apr 2025 11:27:03 -0300
Message-ID: <c6788f2c-ae55-4fcf-b0a2-a95d8ab67d81@gmail.com> (raw)
In-Reply-To: <20250423141226.1857892-1-d.kozinski@samsung.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1156 bytes --]
On 4/23/2025 11:12 AM, Dawid Kozinski wrote:
> - Added constants definitions for APV parser
> - Provided parsing following APV RFC
> - APV parser registration
>
> Signed-off-by: Dawid Kozinski <d.kozinski@samsung.com>
> ---
> configure | 2 +
> libavcodec/Makefile | 2 +
> libavcodec/apv.h | 93 ++++++++
> libavcodec/apv_parse.c | 32 +++
> libavcodec/apv_parse.h | 81 +++++++
> libavcodec/apv_parser.c | 141 +++++++++++
> libavcodec/apv_ps.c | 503 ++++++++++++++++++++++++++++++++++++++++
> libavcodec/apv_ps.h | 188 +++++++++++++++
> libavcodec/parsers.c | 1 +
> 9 files changed, 1043 insertions(+)
> create mode 100644 libavcodec/apv.h
> create mode 100644 libavcodec/apv_parse.c
> create mode 100644 libavcodec/apv_parse.h
> create mode 100644 libavcodec/apv_parser.c
> create mode 100644 libavcodec/apv_ps.c
> create mode 100644 libavcodec/apv_ps.h
Seeing Mark wrote a CBS implementation for this native decoder, this
parser should make use of it instead of duplicating all the parsing code.
See the AV1 parser for an example of the CBS API.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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:[~2025-04-23 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250423141230eucas1p1962c2698d09aced37fa5551493a693b8@eucas1p1.samsung.com>
2025-04-23 14:12 ` Dawid Kozinski
2025-04-23 14:27 ` James Almer [this message]
2025-04-23 21:14 ` Mark Thompson
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=c6788f2c-ae55-4fcf-b0a2-a95d8ab67d81@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