840082 - [MMS][User Story] Image, audio and video format support

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::SMS, defect, P1)

Description

[Peter Dolanjski [:pdol]]

UCID: Messages-012

User Story:
As a user, I can send, receive, and view MMS messages with JPEG images, AMR-NB, H.263 & AMR so that I can view content that is commonly exchanged via MMS.

Comment 1

[Joe Cheng [:jcheng] (please needinfo)]

CJ, can you re-assign as needed? thanks

Comment 2

[Casey Yee]

Sounds more like a technical requirement.

UX is defined in bug #840044

Comment 3

[Joe Cheng [:jcheng] (please needinfo)]

Multimedia format compliance will be checked against OMA-TS-MMS-CONF-V1_3-20110913-A section 7, and Appendix C.1.2

Comment 4

[cajbir (:cajbir)]

If AMR is required for B2G please ensure that it only works for internal B2G applications and not on the "web platform" via the browser.

Comment 5

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

Attachment: implement WBMP decoder

Implementation is referenced from bug 182621. I can wrap these modification with compile option if we only want support WBMP on Firefox OS.

Comment 6

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

Comment on attachment 721569 [details] [diff] [review]
implement WBMP decoder

sorry, wrong bug.

Comment 7

[Kai-Chih Hu [:khu]]

As far as I know, Firefox OS does not support H.263 yet, right?

Comment 8

[Dietrich Ayala (:dietrich)]

Per partner and release-driver discussions, marking blocking- until all MMS functionality in bug 849867 is complete, allowing it all to be uplifted at once to avoid SMS bustage.

Comment 9

[Joe Cheng [:jcheng] (please needinfo)]

http://technical.openmobilealliance.org/Technical/release_program/docs/MMS/V1_2-20050429-A/OMA-MMS-CONF-V1_2-20050301-A.pdf

for minimum conformance on MM Content Classes, only need to support Text and Image Basic

For Video/Audio/Image, only these are mentioned:
Baseline JPEG,
GIF87a,
GIF89a,
WBMP, 
AMR-NB or 13K

Comment 10

[Robert O'Callahan (:roc) (email my personal email if necessary)]

It's important that Gecko support for legacy non-Web formats be restricted as much as possible to the use-cases where they're absolutely needed. In particular we don't want Web developers or non-MMS app developers using them either on purpose or accidentally.

When performance isn't too much of a concern, one way would be to implement support for the format in JS in the app itself. This should work for most image formats using JS to decode to canvas. This also has the technical advantage that the image decoding is effectively sandboxed.

Once we have Web Audio implemented (not on the 18 branch) it would probably work for audio formats such as SP-MIDI, although it would be more work.

Comment 11

[Joe Cheng [:jcheng] (please needinfo)]

what's the latest on this bug? thanks

Comment 12

[Shih-Chiang Chien [:schien] (UTC+8) (use ni? plz)]

This bug is mostly like a meta bug which has splitted into 3 bugs for supporting WBMP/AMR-NB/SP-MIDI.
Patches for WBMP and AMR-NB were ready in b2g18, and per our previous discussion SP-MIDI will be excluded from the v1.1 scope. We can mark this bug as resolved IMO.

Comment 13

[Joe Cheng [:jcheng] (please needinfo)]

per comment 12, mark as resolved and waiting for verification