From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GSoC 2025 - OggKate subtitles support
Date: Tue, 4 Mar 2025 19:44:58 +0000
Message-ID: <DM8P223MB0365743E5F43A9AA811DFFEEBAC82@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAHcLANfPkGzSyEJJQ8QAw22o8wL19hmwHPkhmF3zcdL65J6chw@mail.gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Gianluca Cannata
> Sent: Dienstag, 4. März 2025 09:40
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] GSoC 2025 - OggKate subtitles support
>
> Good morning,
>
> I have to write a karaoke solution with FFmpeg libav libraries for a
> project of mine and I have found OggKate subtitles a good choice to
> implement such solution and I am thinking of writing a Kate demuxer and
> decoder along with a filter that will use OpenGL to render Kate
> subtitles
> capabilities on frame.
>
> What do you think ?
>
> There is someone interested in mentoring this proposal project ?
>
> Or is it too overkill ?
>
> Sincerely
>
> Gianluca
> _______________________________________________
Hi Gianluca,
while it's true that "OggKate" doesn't appear to be well-known (I've never heard of it before), but it's also the only officially spec-ed subtitle format in Ogg containers (besides raw text).
I think that fact makes it interesting to implement it - one could also argue that the reason why it isn't widespread yet is that ffmpeg doesn't support it 😊
The license of the reference implementation source code appears to be permissive (https://github.com/Distrotech/libkate?tab=License-1-ov-file#readme), so an adaption might be possible as well - yet, IANAL.
Regarding the effort, I think that the implementation of a renderer is too steep, especially when aiming to support fancy things like animation. Anyway, a specific renderer would not quite fit into the ffmpeg architecture, because:
Every (text) subtitle decoder decodes to ASS format and every (text) subtitle encoder encodes from ASS to its target format. This means that implementing a decoder for OggKate would require to translate the Kate format to ASS.
Since we do have an ASS renderer (via libass), it would be still possible to achieve the goal of rendering those subtitles, even with animations.
I have seen that there are two representations of Kate subtitles: A text format and a bitstream format. What gets muxed into an Ogg container is always the bitstream format, the text/file format is just an extra and not needed, so it can be skipped, which means in turn that there's no need for developing a demuxer.
As mentioned above, for the format to have a chance to become more widespread, there would also need to be an encoder.
Making this a project about developing an encoder+decoder pair for Ogg Kate would appear to be a nice project IMO.
sw
_______________________________________________
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-03-04 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 8:40 Gianluca Cannata
2025-03-04 10:46 ` Nicolas George
2025-03-04 10:56 ` Gianluca Cannata
2025-03-04 11:00 ` Nicolas George
2025-03-04 11:05 ` Gianluca Cannata
2025-03-04 19:44 ` Soft Works [this message]
2025-03-04 21:05 ` epirat07
2025-03-04 21:28 ` Soft Works
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=DM8P223MB0365743E5F43A9AA811DFFEEBAC82@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.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