On 08/17/2010 04:54 AM, Nganon wrote: > > > On 17 August 2010 04:26, Andy Wilkinson <[email protected] > <mailto:[email protected]>> 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
