From: "Jan Ekström" <jeebjp@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v3 0/3] Initial support for fragmented TTML muxing
Date: Tue, 12 Dec 2023 09:32:24 +0200
Message-ID: <20231212073242.10967-1-jeebjp@gmail.com> (raw)
Changes compared to v2:
* General rebase.
* Limited the test to the first overlapping lines that
finish at around 24.5 seconds. This brings us down to 430 lines
per test (of which there are two).
* Switched from the rawvideo to the data muxer.
This enables pushing TTML together with another track (usually video)
as part of CMAF Ingest, as defined by the DASH-IF Live Media Ingest
Protocol.
Currently does not function well with just the subtitle track unless
the API user explicitly requests fragmentation with a nullptr packet,
as the generic fragmentation decision logic is based on tracks which
do not require squashing.
Currently does support overlapping subtitles, but the implementation
utilizes another packet queue for it, which is probably not optimal.
Recommendations on how to improve things are welcome.
Jan
Jan Ekström (3):
tests/fate-run: add support for specifying the final encode muxer in
`transcode`
avcodec/avpacket: add functionality to prepend to AVPacketLists
avformat/movenc: add support for fragmented TTML muxing
libavcodec/avpacket.c | 20 +-
libavcodec/packet_internal.h | 2 +
libavformat/movenc.c | 9 -
libavformat/movenc_ttml.c | 157 ++++++-
tests/fate-run.sh | 4 +-
tests/fate/mov.mak | 21 +
tests/ref/fate/mov-mp4-fragmented-ttml-dfxp | 430 ++++++++++++++++++++
tests/ref/fate/mov-mp4-fragmented-ttml-stpp | 430 ++++++++++++++++++++
8 files changed, 1054 insertions(+), 19 deletions(-)
create mode 100644 tests/ref/fate/mov-mp4-fragmented-ttml-dfxp
create mode 100644 tests/ref/fate/mov-mp4-fragmented-ttml-stpp
--
2.43.0
_______________________________________________
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 reply other threads:[~2023-12-12 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 7:32 Jan Ekström [this message]
2023-12-12 7:32 ` [FFmpeg-devel] [PATCH v3 1/3] tests/fate-run: add support for specifying the final encode muxer in `transcode` Jan Ekström
2023-12-12 7:32 ` [FFmpeg-devel] [PATCH v3 2/3] avcodec/avpacket: add functionality to prepend to AVPacketLists Jan Ekström
2023-12-12 7:32 ` [FFmpeg-devel] [PATCH v3 3/3] avformat/movenc: add support for fragmented TTML muxing Jan Ekström
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=20231212073242.10967-1-jeebjp@gmail.com \
--to=jeebjp@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