Google Groups

Re: hardware-accelerated audio/video decoding in Gecko (bug 714408)

Andreas Gal Mar 12, 2012 11:44 AM
Posted in group:
Google pledged many things they didn't follow through with and our users and our project are paying the price. H.264 wont go away. Holding out just a little longer buys us exactly nothing.

We can't license decodes and ship those. That would bar others from shipping Firefox without entering into the same deals. All we are talking about is using existing accelerated decoders that already are licensed and available on the system.


Sent from Mobile.

On Mar 12, 2012, at 10:57 AM, Daniel Cater <> wrote:

> On Monday, March 12, 2012 5:40:30 PM UTC, Doug Turner wrote:
>> On Mar 12, 2012, at 10:34 AM, Justin Dolske wrote:
>>> On 3/12/12 7:29 AM, Joe Drew wrote:
>>> \
>>>>> This is great. We really need this on Android where many mobile sites
>>>>> only use h.264 video.
>>>> I don't see why this matters. At the time we shipped Theora (and WebM),
>>>> most _desktop_ sites only supported h.264 (mostly through Flash).
>>> To put it another way:
>>> We had these exact same discussions back when we first shipped Theora, including the issue of H264 on mobile (then with Fennec-on-Nokia).
>>> Rather that just rehashing the same arguments, I'd like to ask what's changed such that we need to reopen this issue?
>> I guess nothing has changed.  The market didn't adopt any new codec.  h.264 video content is what continues to be used everywhere and our browser just falls down there.
>> Doug
> shows a fair few supporters of WebM including Opera, Chrome, Firefox, Android, Adobe, Nvidia, AMD, ARM, Broadcom, Qualcomm, Texas Instruments, Nvidia, Rockchip, YouTube, Skype and Logitech.
> Also Google had pledged to remove H.264 support from Chrome but hasn't yet done so:
> _______________________________________________
> dev-platform mailing list