From: Nuo Mi <nuomi2021@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Nuo Mi <nuomi2021@gmail.com>
Subject: [FFmpeg-devel] [PATCH v4 0/6] Add mp4 and ts support for vvc
Date: Mon, 29 Jan 2024 22:54:26 +0800
Message-ID: <TYSPR06MB643320DE227C4F77C754C489AA7E2@TYSPR06MB6433.apcprd06.prod.outlook.com> (raw)
Major chagnes since v3:
movenc: ff_mov_write_packet, get cenc nal_size_length from par->extradata[4] (James, Thomas)
isom_tags: remove vvc from ff_codec_movvideo_tags (James)
mpegtsenc: mpegts_check_bitstream, use long variable names to enhance code readability.(Andreas)
mpegtsenc: mpegps_read_packet, remove duplicate vvc entry (Marton)
Nuo Mi (4):
avformat/mpegtsenc: refact mpegts_check_bitstream to loop up table
avformat/mpegtsenc: refact, move h264, hevc startcode checking to
check_h26x_startcode
avformat/mpegtsenc: refact, remove h264, hevc magic numbers for
nal_type
avformat/mpegtsenc: refact out h26x_prefix_aud
Thomas Siedel (2):
avformat/mp4: add muxer support for H266/VVC
avformat: add ts stream types for H266/VVC
configure | 2 +-
libavformat/Makefile | 6 +-
libavformat/isom.c | 1 +
libavformat/mov.c | 6 +
libavformat/movenc.c | 41 +-
libavformat/mpeg.c | 3 +
libavformat/mpeg.h | 1 +
libavformat/mpegts.c | 2 +
libavformat/mpegts.h | 1 +
libavformat/mpegtsenc.c | 173 ++++---
libavformat/vvc.c | 971 ++++++++++++++++++++++++++++++++++++++++
libavformat/vvc.h | 99 ++++
12 files changed, 1239 insertions(+), 67 deletions(-)
create mode 100644 libavformat/vvc.c
create mode 100644 libavformat/vvc.h
--
2.25.1
_______________________________________________
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".
reply other threads:[~2024-01-29 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=TYSPR06MB643320DE227C4F77C754C489AA7E2@TYSPR06MB6433.apcprd06.prod.outlook.com \
--to=nuomi2021@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