Dears,
早上看到一篇大陸的新聞說 Gecko 將在 Android 上支援 H.264,其來源為此討論串:
http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/fb14de8b9ad84e15/
不過如果你看完整篇,會知道這麼說不太精準:
事實是,Andreas 為了 B2G 專案想來解 bug 714408,以便讓設備具備的解碼能力能為 Firefox 所用。
(也就是說,如果硬體支援 H.264,那 Firefox 就可以用硬解來看 H.264 影片)
這件事情多少會影響到對於 Open Codec 的信念,所以在 dev.platform 上有一番論戰,
很多 @
mozilla.com 跟 @
mozilla.org 的成員提出不同觀點公開討論,
挺有趣的,也可以看到 Mozilla 公開討論的模式。
對 video codec 有興趣的可以去掃一下甚至加入討論,
也歡迎訂閱 dev.platform:
https://lists.mozilla.org/listinfo/dev-platform
附上 bug 714408,這邊是技術面實作上的討論
https://bugzilla.mozilla.org/show_bug.cgi?id=714408
~Bob
--
Po-chiang Chao (:bobchao)
Community Manager, Mozilla Taiwan
+886-2-87861100 ext. 204
https://mozillians.org/zh-TW/u/d86c49721d
---------- Forwarded message ----------
From: Andreas Gal <
g...@mozilla.com>
Date: 3月12日, 下午3時28分
Subject: hardware-accelerated audio/video decoding in Gecko (bug
714408)
To: mozilla.dev.platform
I want to land bug 714408 on mozilla-central as soon as I get review
for it. It adds hardware-accelerated audio/video decoding support to
Gecko using system decoders already present on the system. Android,
for example, ships by default with a number of decoders, and in
particular for such mobile devices we really have to use these
hardware-accelerated decoders for good battery life (and performance).
Initially this will be enabled on Gonk (B2G). In a few weeks we will
add support for Android as well. We will support decoding any video/
audio format that is supported by existing decoders present on the
system, including H.264 and MP3. There is really no justification to
stop our users from using system decoders already on the device, so we
will not filter any formats.
The system decoders are loaded using a plugin framework called MPAPI,
which is currently internal to Gecko, but we might expose it via NPAPI
to external decoder providers as well. MPAPI helps us deal with
incompatibilities in systems decoders (without risking Gecko not
starting up which would happen if we try to link against the system
decoders directly).
Currently MPAPI delivers audio and video frames back to the browser
and fully integrates with our rendering pipeline (CSS and all). On
Android we might have to add a second video path using overlays which
would only work with a small subset of CSS since extracting video
frames isn't supported on all versions of Android (and all devices).
I don't think this bug significantly changes our position on open
video. We will continue to promote and support open codecs, but when
and where existing codecs are already installed and licensed on
devices we will make use of them in order to provide people with the
best possible experience.
Let me know if you have any questions.
Andreas