From: Traian Coza <traian.coza@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Traian Coza <traian.coza@gmail.com>
Subject: [FFmpeg-devel] [PATCH 0/1] Text to Bitmap conversion implemented!
Date: Tue, 3 May 2022 14:31:13 -0400
Message-ID: <20220503183114.870470-1-traian.coza@gmail.com> (raw)
I've modified my previous patch to fix a number of aesthetic issues.
First, I have only one commit now.
Second, I have read the Contributing section and I think I respected all the conventions mentionned there.
Third, I have rebased my commit to be up-to-date with the central repo.
Tell me if there's anything else I need to do.
Original email body:
I added the possibility of converting text-based subtitle tracks (such as subrip or ass) to bitmap-based subtitle tracks (such as dvd_subtitle).
I accomplished this by using libass, and basically using the code from vf_subtitles.c to render text subtitles and store the images in the AVSubtitle structure.
Of course, this functionality will only work when ffmpeg is configured with --enable-libass.
Traian Coza (1):
fftools: Implemented text to bitmap subtitles!
fftools/Makefile | 2 +
fftools/ffmpeg.c | 35 ++++-
fftools/text_to_bitmap.c | 303 +++++++++++++++++++++++++++++++++++++++
fftools/text_to_bitmap.h | 37 +++++
libavcodec/avcodec.h | 9 ++
5 files changed, 385 insertions(+), 1 deletion(-)
create mode 100644 fftools/text_to_bitmap.c
create mode 100644 fftools/text_to_bitmap.h
--
2.34.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".
next reply other threads:[~2022-05-03 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 18:31 Traian Coza [this message]
2022-05-03 18:31 ` [FFmpeg-devel] [PATCH 1/1] fftools: Implemented text to bitmap subtitles! Traian Coza
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=20220503183114.870470-1-traian.coza@gmail.com \
--to=traian.coza@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