1073786 - [meta] Multiple channel support for Cubeb

Status: NEW

Description

[Sebastian_Fisahn]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20140926185533

Steps to reproduce:

see details here: https://support.mozilla.org/en-US/questions/1020526?esab=a&s=&r=0&as=s


Actual results:

see details: https://support.mozilla.org/en-US/questions/1020526?esab=a&s=&r=0&as=s


Expected results:

see details: https://support.mozilla.org/en-US/questions/1020526?esab=a&s=&r=0&as=s

Comment 1

[Greg Ogonowski]

Currently Firefox is now the only major browser not supporting multichannel AAC audio.
Maybe we can get past this problem soon.
We provide high performance high quality streaming audio encoders to many of the largest content providers. We have test HLS streams available upon request. The surround streams unfortunately, play in 2 channels using Firefox. We need multichannel AAC decoding! This would be easy to do now that Firefox is MSE compatible.
Our test multichannel AAC HLS streams currently play using Microsoft Edge, IE for Win 8/10, Safari Mac OS X and iOS, and Google Chrome. It sure would be good to add Firefox to this list.
Please let me know if we can be of assistance to make this happen.
Here are test resources:
https://www2.iis.fraunhofer.de/AAC/
https://www.indexcom.com/products/encoder/

Comment 2

[Chun-Min Chang[:chunmin]]

As per irc conversation with :kinetik, it's better to start from cubeb[0] 
1. [cubeb] Support 5.1 on one backend(OS X, Linux, Windows, Android) and write tests for it
2. [cubeb] Make it work on other platforms
3. [gecko] Integrate it on Gecko side in AudioStream up to AudioConverter

[0] https://github.com/kinetiknz/cubeb

Comment 3

[Maire Reavy [:mreavy] Plz needinfo?]

@cchang -- I'd like to make this bug into a meta bug for adding 5.1 support to cubeb.  Can you spin off bugs for each platform?  I'd love if we could do Windows first because it will have the greatest impact, but I realize it may be faster/easier to do one of the other platforms first.  Do you know if there is a meta bug for 5.1 support in Core:Audio/Video:Playback?  Thanks!

Comment 4

[Chun-Min Chang[:chunmin]]

(In reply to Maire Reavy [:mreavy] from comment #3)
> @cchang -- I'd like to make this bug into a meta bug for adding 5.1 support
> to cubeb.  Can you spin off bugs for each platform?  
OK, I will open new bugs for each platform.
> I'd love if we could do Windows first because it will have the greatest impact, 
> but I realize it may be faster/easier to do one of the other platforms first.
I don't have window in hand. I'd like to do that if I can get one.
> Do you know if there is a meta bug for 5.1 support in Core:Audio/Video:Playback?  Thanks!
I don't find it on bugzilla. Maybe we should open one for it. Bug 706327 is also a meta for Core:Audio/Video:cubeb to support multiple channels. Do we need to set dependency between these two bugs?

Comment 5

[Maire Reavy [:mreavy] Plz needinfo?]

(In reply to Chun-Min Chang[:chunmin] from comment #4)
> (In reply to Maire Reavy [:mreavy] from comment #3)
> > Do you know if there is a meta bug for 5.1 support in Core:Audio/Video:Playback?  Thanks!
> I don't find it on bugzilla. Maybe we should open one for it. Bug 706327 is
> also a meta for Core:Audio/Video:cubeb to support multiple channels. Do we
> need to set dependency between these two bugs?

Actually, I'm going to close Bug 706327 as a dup of this bug.  Can you open a new meta bug in Playback for 5.1 support and make it dependent on this bug?  Thanks so much for working on this!

Comment 7

[Chun-Min Chang[:chunmin]]

(In reply to Maire Reavy [:mreavy] from comment #5)
> Actually, I'm going to close Bug 706327 as a dup of this bug.  Can you open
> a new meta bug in Playback for 5.1 support and make it dependent on this
> bug?  Thanks so much for working on this!
Done. Thanks for your guide :)

Comment 8

[Chun-Min Chang[:chunmin]]

I open a wiki page to track the status
https://wiki.mozilla.org/Media/multichannel

Comment 9

[Bulk Bug Changes for mreavy's org]

Mass change P2->P3 to align with new Mozilla triage process.