unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: Guix-devel <guix-devel@gnu.org>
Cc: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Video subtitles
Date: Wed, 19 Dec 2018 22:55:34 -0300	[thread overview]
Message-ID: <CAPNLzUOrzjK444U61G4H21vHVm8vMu5mjPyT3Lx+PhVedwHocA@mail.gmail.com> (raw)

Hi!

I have been playing with aegisub today and I would like to share my
experience with that tool, your ideas about how video subtitles should
be included, and your advice too.

I installed aegisub from guix, and when I open it, it has a GUI. There
you load your video, in my case I loaded the final video - the one
everybody loved with Dennis pics, that already had my voice - and
started from there. And ended up with a a final video with subtitles
included. But don't stop reading here.

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

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. 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.

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.

I find a solution for not getting the whole text of the subtitle at
once, that is creating each svg/cli session/whatever
appears-in-the-video-if-needed with their audio and subtitle
separately and glue every piece of video as a last step with ffmpeg.
Apparently, that is possible according to
https://trac.ffmpeg.org/wiki/Concatenate - have not tried it yet.
However, I don't know if, in case of wanting to have the subtitles
separately - not  hardsubs-  in this latter case if it is possible to
concatenate them and use them outside the video.

Sorry if the mail is too long, or if sth is messy, please, let me know.

Regards :)
Laura

             reply	other threads:[~2018-12-20  1:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20  1:55 Laura Lazzati [this message]
2018-12-20  7:46 ` Video subtitles 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

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=CAPNLzUOrzjK444U61G4H21vHVm8vMu5mjPyT3Lx+PhVedwHocA@mail.gmail.com \
    --to=laura.lazzati.15@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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).