1 |
On 08/17/2010 04:54 AM, Nganon wrote: |
2 |
> |
3 |
> |
4 |
> On 17 August 2010 04:26, Andy Wilkinson <drukargin@×××××.com |
5 |
> <mailto:drukargin@×××××.com>> wrote: |
6 |
> |
7 |
> I've noticed that ebuilds of chromium at and later than 6.0.472.33 |
8 |
> no longer use the system-provided ffmpeg, and seem to lose support |
9 |
> for h264 videos (test any non-webm, html5 video at youtube; it |
10 |
> will never load). |
11 |
> |
12 |
> I've tried doctoring the ebuild to use the system-provided ffmpeg, |
13 |
> which does not fix h264 video and causes crashes on webm videos: |
14 |
> probably why we went back to the bundled ffmpeg. |
15 |
> |
16 |
> Has anyone else noticed this? Is there a straightforward |
17 |
> work-around beyond going back to 6.0.472.14ish? |
18 |
> |
19 |
> Thanks, |
20 |
> |
21 |
> -Andy |
22 |
> |
23 |
> |
24 |
> Using system-ffmpeg is commented as TODO in the ebuild refering to [1]. |
25 |
> There is also bug report[2] related to this. Seems like it maybe fixed |
26 |
> in a never branch than 472. |
27 |
> |
28 |
> [1] http://crbug.com/50678 |
29 |
> [2] http://bugs.gentoo.org/show_bug.cgi?id=329641 |
30 |
> |
31 |
Thanks for the info. That doesn't entirely answer my question, |
32 |
though... shouldn't chromium's bundled ffmpeg have h264 support? |
33 |
Google's youtube.com/html5 page suggests that Chrome (and thus |
34 |
chromium?) supports h264. Is this a licensing issue going to the open |
35 |
source build that I've not heard of yet? |
36 |
|
37 |
Thanks again, |
38 |
|
39 |
-Andy |