From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>, ludo@chbouib.org
Subject: Re: Outreachy project infrastructure
Date: Fri, 23 Nov 2018 12:38:36 +0100 [thread overview]
Message-ID: <CAE4v=phS2b7HmHpJPnmUekAzgCuVXsKWFbT=FRm4sLmnJooJaA@mail.gmail.com> (raw)
In-Reply-To: <878t1k2h29.fsf@elephly.net>
Hello Ricardo,
Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2018. nov. 23.,
P, 12:02):
>
>
> Hi Gábor,
>
> > I would propose the following: do not show slides and screen recording
> > at the same time, and make a transition between them
> > when we switch.
>
> The slides are turned into a video segment; the terminal session
> recordings as well. The final step is just to concatenate them to a
> single video track. This can be done with ffmpeg. All of these
> segments would be silent. A single narration audio file is then merged
> as the audio track.
Ok, that is manageable. I would still consider some transition to make it more
visually appealing. we can use for example the fade filter or similar.
>
> > Have the narrator optionally overlaid onto the video
> > (for example in the bottom right corner), and make the narrator
> > screen the video when we have neither screen recording nor slides to
> > show.
>
> My preference is to not have a video of the narrator at all, actually.
> This avoids problems of embedding / overlaying video without obscuring
> the content, recording quality differences, etc. I think for 3 minute
> videos the slide content / terminal session recordings would be
> sufficient.
It is definitely easier that way, and we can make a lot of simplifying
assumptions.
I would still consider having a placeholder image to cover for the
possibility that
there might be parts where no slide or screen recording is shown. But we might
make it a policy to always show something. WDYT?
>
> --
> Ricardo
>
Best regards,
g_bor
next prev parent reply other threads:[~2018-11-23 11:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 13:51 Outreachy project infrastructure Gábor Boskovits
2018-11-21 14:37 ` Laura Lazzati
2018-11-21 15:34 ` Julien Lepiller
2018-11-21 15:19 ` Ricardo Wurmus
2018-11-21 20:18 ` Laura Lazzati
2018-11-21 22:28 ` Ricardo Wurmus
2018-11-22 1:13 ` Laura Lazzati
2018-11-22 12:32 ` Thorsten Wilms
2018-11-22 13:12 ` Ricardo Wurmus
2018-11-22 14:23 ` Thorsten Wilms
2018-11-22 20:11 ` Björn Höfling
2018-11-23 1:54 ` Laura Lazzati
2018-11-23 9:04 ` Ricardo Wurmus
2018-11-23 10:24 ` Gábor Boskovits
2018-11-23 11:01 ` Ricardo Wurmus
2018-11-23 11:38 ` Gábor Boskovits [this message]
2018-11-23 12:27 ` Ricardo Wurmus
2018-11-25 23:08 ` Björn Höfling
2018-11-26 0:30 ` Laura Lazzati
2018-11-26 14:07 ` Björn Höfling
2018-11-26 15:40 ` Laura Lazzati
2018-11-29 15:19 ` Laura Lazzati
2018-11-29 15:36 ` Ricardo Wurmus
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=phS2b7HmHpJPnmUekAzgCuVXsKWFbT=FRm4sLmnJooJaA@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@chbouib.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).