On Tuesday, 11 December 2012 14:32:44 UTC+5:30, Chris Double wrote:
> On Tue, Dec 11, 2012 at 9:19 PM, <[email protected]> wrote:
>
> > Hi, If anybody there kindly to help me to brief about the media frame work
> > being used in B2G.
>
>
>
> We use Gecko's internal media framework (the same as used in Firefox)
>
> and decoders for open formats like WebM, Opus, Theora, etc. For
>
> formats like H.264 and AAC we use Android's libstagefright framework.
>
> This requires the device to have decoder binary blobs provided by the
>
> device creator to do hardware/software decoding of these formats. The
>
> libstagefright backend plugs into Gecko's media framework and exposes
>
> it using normal HTML <video> and <audio> elements. So apps can use any
>
> of the HTML media API's to playback these formats.
>
>
>
> Chris.
>
> --
>
> http://www.bluishcoder.co.nz
Thanks Chris,
I have a concern about media server also, What is its role? Is architecture
of gecko's media framework similar to one Android has? I think media server
code has been reused from Android. Please clarify me these, and I would be
blessed if you could give me a brief idea about the b2g media architecture
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
