unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Video subtitles
Date: Thu, 20 Dec 2018 22:08:45 +0100	[thread overview]
Message-ID: <CAE4v=phHtu41efLBEXpod1DcF98z6Smckr+sjZDsQZ7r2WaRxg@mail.gmail.com> (raw)
In-Reply-To: <87pntwsjmz.fsf@elephly.net>

Hello,

Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2018. dec. 20.,
Cs, 9:26):
>
>
> Hi Laura,
>
> > The first question I need to answer is if subtitles are going to be
> > present all the time as part of the video, or they should be able to
> > be disabled. We had that discussion somewhere, but if they are going
> > to be present as part of the video (hardsubs) only .srt and .ass - the
> > ones created by default by aegisub - are supported by ffmpeg:
> > https://trac.ffmpeg.org/wiki/HowToBurnSubtitlesIntoVideo
>
> The subtitles should be provided as a separate file, so that they can
> easily be swapped out or disabled.  Some container formats allow
> embedding the subtitles, but we would need to embed all subtitles in all
> language variants of all video files, and this seems like more work.
> Having the subtitles as separate files is more convenient for
> processing.
>

Yes, and the embeding into the container can be automated at the end if needed.

> > I remembered how much time each audio file lasted, so I added one
> > subtitle for each svg file that appears in the video - they were just
> > three- with the full content of what is said in the audio.
>
> It is more common to have a single subtitle file per video.

It would be ok to have a single subtitle file.

>
> > The drawback of this is that each svg file in the video has the full
> > subtitle text before the speaker mentions those words - I will ask
> > Björn tomorrow to upload it to their IPFS so that you can see what I
> > mean.
>
> You can time the appearance of text.  I’ve only ever written srt
> subtitle files by hand before, but they are all similar in that they
> associate a piece of text with a timestamp.  The text is then displayed
> at the specified time only.
>
> You can figure out the appropriate timestamps by playing back the video
> and recording the times when something is said that should be titled.
>

So to make this more explicit, you could break down the text to smaller
chunks, then time the appearance of those.

> > When choosing the format of the subtitles, Ricardo mentioned that it
> > was better using usf because it had support for styling. The good news
> > is that aegisub allows us to do so in their own interface, but  in
> > their .ass format, one of the two that supports ffmpeg,  which is not
> > compatible,  I guess, with the formats mentioned in po4a for
> > translation. However the .ass subtitle can be exported as .ttxt -
> > which is an XML, and that can be converted back to .ass.
>
> “.ass” files are very popular and very rich in styling features.  “.usf”
> files are less commonly seen in the wild.
>
> I have no strong opinions about using “.usf”.  “.ass” may just be fine.
> Apparently, it can be converted to po files for translation with
> “sub2po”, which is part of the “translate” toolkit.  I have no
> experience with this, and I think it would be better to use a format
> that didn’t require even more tools to work with.
>
> This shouldn’t block you, though.  It is fine to use Aegisub manually to
> create the initial subtitle and then convert it to another format.
> Aegisub does not need to be part of the automated process to compile the
> videos.
>
> --
> Ricardo
>
>

I believe that we don't want to do anything fancy with the subtitles, so I
guess any format would be just fine, provided we have tool support.

Best regards,
g_bor

      parent reply	other threads:[~2018-12-20 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  1:55 Video subtitles Laura Lazzati
2018-12-20  7:46 ` Pierre Neidhardt
2018-12-20  8:11 ` Ricardo Wurmus
2018-12-20  8:31   ` Pierre Neidhardt
2018-12-20 20:03   ` Laura Lazzati
2018-12-20 21:26     ` Ricardo Wurmus
2018-12-20 22:14       ` Laura Lazzati
2018-12-21 19:45         ` Ricardo Wurmus
2018-12-20 21:08   ` Gábor Boskovits [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE4v=phHtu41efLBEXpod1DcF98z6Smckr+sjZDsQZ7r2WaRxg@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).