unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 42607@debbugs.gnu.org
Subject: bug#42607: guix.gnu.org/videos don't play on iOS
Date: Mon, 1 Feb 2021 15:54:02 -0500	[thread overview]
Message-ID: <YBhqakLJgkRwDZQk@jasmine.lan> (raw)
In-Reply-To: <20200729232657.GA15458@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

On Wed, Jul 29, 2020 at 07:26:57PM -0400, Leo Famulari wrote:
> > nginx can easily sniff iOS/Macintosh user agents and serve them an inferior
> > format to match, such as h264 with MP3 audio, which can both be encoded
> > using free software in Guix.
> 
> Here is where the videos are created:
> 
> https://git.savannah.gnu.org/cgit/guix/videos.git/tree/Makefile
> 
> ------
> $(NUMBER).clino.$(VIDEO).webm: \
> 	 $(VIDEO)/$(LOCALE_LANG)/durations.txt        \
> 	 $(VIDEO)/$(LOCALE_LANG)/audios/all.mp3	
> 		ffmpeg -y -f concat -vsync cfr \
> 		-i $(VIDEO)/$(LOCALE_LANG)/durations.txt \
> 		-i $(VIDEO)/$(LOCALE_LANG)/audios/all.mp3 \
> 		-c:a libopus -b:a 192k \
> 		-c:v libvpx-vp9 -crf 31 -b:v 0 -pix_fmt yuv420p \
> 		-af apad -shortest \
> 		-vf fps=25 -threads 4 $(VIDEO)/$(LOCALE_LANG)/videos/$@;
> 		make clean_noCli
> ------
> 
> So, we'd need to add a target that did "-c:a copy -c:v libx264" and add
> some logic to create two videos instead of one. I didn't look into it
> closely yet to see if that will be simple or not.

Coming back to this, I don't remember why I suggested "c:a copy". We
would want to transcode the audio as well, because the standard codec is
h264/aac.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-02-01 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 23:08 bug#42607: guix.gnu.org/videos don't play on iOS Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-29 23:26 ` Leo Famulari
2021-02-01 20:54   ` Leo Famulari [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=YBhqakLJgkRwDZQk@jasmine.lan \
    --to=leo@famulari.name \
    --cc=42607@debbugs.gnu.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
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).