all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: 38045@debbugs.gnu.org, bug-gnuzilla@gnu.org
Subject: bug#38045: Video Rendering Issues on IceCat
Date: Mon, 04 Nov 2019 11:36:40 -0500	[thread overview]
Message-ID: <87zhhblhsc.fsf__46318.2615859964$1572885497$gmane$org@netris.org> (raw)
In-Reply-To: <874kzjmww2.fsf@netris.org>

Earlier, I wrote:
> I have a hypothesis of what might have happened here.
> 
> Since the upgrade to version 68, the IceCat package in GNU Guix is no
> longer using our system ffmpeg.

Sorry, I forgot to mention why I think this might be relevant.  The
reason is because upstream Firefox adopts the approach of downloading
certain codecs in pre-compiled form, to avoid certain patent concerns.
That's not necessary when using Guix's system ffmpeg library, but maybe
Mozilla rigged the bundled ffmpeg library to avoid including support for
those codecs.

       Mark

  parent reply	other threads:[~2019-11-04 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87blts4gmv.fsf@gmail.com>
2019-11-03 16:33 ` Video Rendering Issues on IceCat Raghav Gururajan
2019-11-03 22:37   ` bug#38045: " Christopher Lemmer Webber
2019-11-04  0:41   ` Chris Marusich
2019-11-04 13:02   ` Raghav Gururajan
     [not found]   ` <973472324a8a0c24073a9f7106bff044@disroot.org>
2019-11-04 16:25     ` Mark H Weaver
     [not found]     ` <874kzjmww2.fsf@netris.org>
2019-11-04 16:36       ` Mark H Weaver [this message]
2020-01-16  6:24   ` bug#38045: IceCat: some codecs don't work without workaround Mark H Weaver
2020-01-16 12:29     ` bug#38831: " Julien Lepiller
2019-12-31 14:24 Jakub Kądziołka

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='87zhhblhsc.fsf__46318.2615859964$1572885497$gmane$org@netris.org' \
    --to=mhw@netris.org \
    --cc=38045@debbugs.gnu.org \
    --cc=bug-gnuzilla@gnu.org \
    --cc=raghavgururajan@disroot.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.