From: Andy Wilkinson <drukargin@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] >=www-client/chromium-6.0.472.33 and h264
Date: Tue, 17 Aug 2010 09:49:22 -0700 [thread overview]
Message-ID: <4C6ABD92.5040608@gmail.com> (raw)
In-Reply-To: <AANLkTinyELNcPiKemr0n2ZsiB=ZGiM6AF_Y28MAJH38u@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
On 08/17/2010 04:54 AM, Nganon wrote:
>
>
> On 17 August 2010 04:26, Andy Wilkinson <drukargin@gmail.com
> <mailto:drukargin@gmail.com>> wrote:
>
> I've noticed that ebuilds of chromium at and later than 6.0.472.33
> no longer use the system-provided ffmpeg, and seem to lose support
> for h264 videos (test any non-webm, html5 video at youtube; it
> will never load).
>
> I've tried doctoring the ebuild to use the system-provided ffmpeg,
> which does not fix h264 video and causes crashes on webm videos:
> probably why we went back to the bundled ffmpeg.
>
> Has anyone else noticed this? Is there a straightforward
> work-around beyond going back to 6.0.472.14ish?
>
> Thanks,
>
> -Andy
>
>
> Using system-ffmpeg is commented as TODO in the ebuild refering to [1].
> There is also bug report[2] related to this. Seems like it maybe fixed
> in a never branch than 472.
>
> [1] http://crbug.com/50678
> [2] http://bugs.gentoo.org/show_bug.cgi?id=329641
>
Thanks for the info. That doesn't entirely answer my question,
though... shouldn't chromium's bundled ffmpeg have h264 support?
Google's youtube.com/html5 page suggests that Chrome (and thus
chromium?) supports h264. Is this a licensing issue going to the open
source build that I've not heard of yet?
Thanks again,
-Andy
[-- Attachment #2: Type: text/html, Size: 2874 bytes --]
next prev parent reply other threads:[~2010-08-17 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 1:26 [gentoo-user] >=www-client/chromium-6.0.472.33 and h264 Andy Wilkinson
2010-08-17 11:54 ` Nganon
2010-08-17 16:49 ` Andy Wilkinson [this message]
2010-08-17 17:58 ` Nganon
2010-08-17 20:42 ` Andy Wilkinson
2010-08-18 11:15 ` Nganon
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=4C6ABD92.5040608@gmail.com \
--to=drukargin@gmail.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox