From: James Almer <jamrial-at-gmail.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] avformat/mov_muxer: Extended MOV muxer to handle APV video content
Date: Mon, 7 Jul 2025 12:23:17 -0300
Message-ID: <b93d5eaa-9e01-4bc9-9ef3-5fea018f0ea9@gmail.com> (raw)
In-Reply-To: <20250508103000.4093344-1-d.kozinski@samsung.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1012 bytes --]
On 5/8/2025 7:30 AM, Dawid Kozinski wrote:
> - Changes in mov_write_video_tag function to handle APV elementary stream
> - Provided structure APVDecoderConfigurationRecord that specifies the decoder configuration information for APV video content
>
> Signed-off-by: Dawid Kozinski <d.kozinski@samsung.com>
> ---
> libavformat/Makefile | 2 +-
> libavformat/apv.c | 830 ++++++++++++++++++++++++++++++++++++++++
> libavformat/apv.h | 88 +++++
> libavformat/isom_tags.c | 1 +
> libavformat/movenc.c | 52 +++
> 5 files changed, 972 insertions(+), 1 deletion(-)
> create mode 100644 libavformat/apv.c
> create mode 100644 libavformat/apv.h
>
There's a lot of duplicate parsing code here. We should instead reuse
the existing CBS implementation.
Add https://gist.github.com/jamrial/631a2b0b7dafb3f0a9596a24621cb79d to
make cbs_apv available in lavf and use the CBS API to parse the
bitstream (It will have a ff_lavf_cbs_* prefix). See movenccenc.c
[-- 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".
prev parent reply other threads:[~2025-07-07 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250508103007eucas1p1b398715260c2a0fedb5e63c7658bdde7@eucas1p1.samsung.com>
2025-05-08 10:30 ` Dawid Kozinski
2025-07-07 15:23 ` 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=b93d5eaa-9e01-4bc9-9ef3-5fea018f0ea9@gmail.com \
--to=jamrial-at-gmail.com@ffmpeg.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