Closed Bug 914408 Opened 11 years ago Closed 11 years ago

Support AAC outside of MP4 container

Categories

(Core :: Audio/Video, defect)

Product:
Core
Component:
Audio/Video
Version:
24 Branch
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: nick, Unassigned)

Details

On Firefox OS, we have support for audio/mpeg MIME types.  We also have support for audio/mp4 MIME types.  MP4 may contain AAC, which is supported on device.  When AAC is not in the MP4 container, and is served with the MIME type 'audio/aac', an error is raised:

[16:37:52.098] HTTP "Content-Type" of "audio/aac" is not supported. Load of media resource http://mp3.radiohamburg.c.nmdn.net/radiohamburg/livestream64.aac failed. @ file:///Users/Nicholas/mozilla/playlist/javascript-playlist-parser/index.html

It would be helpful for TuneIn, an internet radio streaming app, to have support for this MIME type and container; 13% of their streams are served with the MIME type 'audio/aac' and they do not have the power to change that.

Also, I don't know for sure, but I do not believe that 'audio/aac' is the same as 'audio/aac-adts' which is why I don't think this bug is related to #809186 or #807361, but please correct me if I'm wrong.
blocking-b2g: --- → koi?
Marketplace is low on music apps and this feature functionality is useful to many streaming apps in addition to Tune In.
If we have wide OS support for decoding those types of files I'm not opposed.
As it stands we would have circa 57% of TuneIn streams supported.
100% - AAC - WMA = 100% - 13% - 26% = 57%.

Adding AAC would bring us in the 70% ballpark which is about the bare minimum acceptable for them.

It is super important for a number of our carrier partners as well as ourselves to land TuneIn.
I don't know for sure, but I do not believe that 'audio/aac' is the same as 'audio/aac-adts' which is why I don't think this bug is related to #809186 or #807361, but please correct me if I'm wrong.
Looks like no one else supports AAC outside of MP4 containers. [0]

[0] http://html5doctor.com/html5-audio-the-state-of-play/#containers
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
blocking-b2g: koi? → ---
Google Crhome does now support AAC-ADTS.
Update: all our AAC decoders now support playing an ADTS stream, and it would be a rather small change to support a .aac file (which are using an ADTS format)
Maybe we can revisit the decision to wontfix, since have support for ICY protocol streams (many are aac containers & aac-adts codecs)?
Flags: needinfo?(roc)
...since *many internet audio stream* have support...
If all other browsers support it, and all our platforms support it, I guess it's hard to object.
Flags: needinfo?(roc)
Hello,

Any update on AAC-ADTS support? 
Firefox is the only browser not supporting it, *ALL* other browsers do.

And frankly, MP4 containers are very bad for AAC audio live streaming.
We do support AAC-ADTS since bug 1169212 (November 2015), it wasn't working with webaudio until bug 1355933.

We no not support AAC in ADTS for MSE however, with no plan of supporting it at this stage.
You need to log in before you can comment on or make changes to this bug.