From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OlPcC-0003hB-2B for garchives@archives.gentoo.org; Tue, 17 Aug 2010 17:06:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 52F73E0C02 for ; Tue, 17 Aug 2010 17:06:19 +0000 (UTC) Received: from mail-px0-f181.google.com (mail-px0-f181.google.com [209.85.212.181]) by pigeon.gentoo.org (Postfix) with ESMTP id DC234E0B5B for ; Tue, 17 Aug 2010 16:49:25 +0000 (UTC) Received: by pxi5 with SMTP id 5so3382813pxi.40 for ; Tue, 17 Aug 2010 09:49:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type; bh=CjvZXM3cM5ZEJfAxdvazA68Azt/gn5qR+CIWtM6+0co=; b=QWp/PcR+KY3SSffmDa+ZIejg8vbLRwMUdO7pWAm74nRGFkvLfc0mpoQHXmWwgSUzlt 5VanAE8qzidzpDezDFe4bB3umx5CTAFb+FoLju/oIyoUQoKr9+UA5aXWmQ7JCJLwSQw6 Cl1IDP2zhkAOGTbPhQl+ONuxTQfUtN+v5Mzzw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; b=u4dQpuvYcVplfbZ/pE+AaD88XlA9SyGqWoqNASM0AxJKJqmo1kpNT2KKmU50oomkg/ x6quU79e/icKlnucuFjb0meEEGac8OQoqxmRyxrN8fj+8SJyBBm26ajv9/xupvv4c6jy saZ7b8EyqcDu3/j37OBQIZuIZviAcYAoeNJ3I= Received: by 10.114.53.4 with SMTP id b4mr1961053waa.190.1282063765444; Tue, 17 Aug 2010 09:49:25 -0700 (PDT) Received: from [192.168.0.110] (cpe-76-93-116-213.socal.res.rr.com [76.93.116.213]) by mx.google.com with ESMTPS id 33sm14663349wad.18.2010.08.17.09.49.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 17 Aug 2010 09:49:24 -0700 (PDT) Message-ID: <4C6ABD92.5040608@gmail.com> Date: Tue, 17 Aug 2010 09:49:22 -0700 From: Andy Wilkinson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100727 Thunderbird/3.1.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] >=www-client/chromium-6.0.472.33 and h264 References: <4C69E545.6080800@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------070009080109000208040404" X-Archives-Salt: 34865f90-0151-46ee-993b-eb38713306d4 X-Archives-Hash: c8b26f6f0fbba6ed6a14d0db8b3f1746 This is a multi-part message in MIME format. --------------070009080109000208040404 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 08/17/2010 04:54 AM, Nganon wrote: > > > On 17 August 2010 04:26, Andy Wilkinson > 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 --------------070009080109000208040404 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 08/17/2010 04:54 AM, Nganon wrote:


On 17 August 2010 04:26, Andy Wilkinson = <drukargin@gmail.com&g= t; 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?=C2=A0 Is there a straightforw= ard 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].=C2=A0
There is also bug report[2] related to this. Seems like it maybe fixed in a never branch than 472.


Thanks for the info.=C2=A0 That doesn't entirely answer my question, though... shouldn't chromium's bundled ffmpeg have h264 support?=C2=A0 Google's youtube.com/html5 page suggests that Chrome (and thus chromium?) supports h264.=C2=A0 Is this a licensing issue going to th= e open source build that I've not heard of yet?

Thanks again,

-Andy
--------------070009080109000208040404--