Closed Bug 1248696 Opened 8 years ago Closed 8 years ago

Audio channel count changes in MSE source buffer throwing decode error

Categories

(Core :: Audio/Video: Playback, defect)

44 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1247138
Tracking Status
firefox44 --- affected

People

(Reporter: prabubio, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.103 Safari/537.36

Steps to reproduce:

1. Create MediaSource
2. Append SourceBuffer with an mp4 audio track with one channel (channel count = 1). This contains ftyp, moov, moof and mdat headers.
3. Audio plays fine if I add chunks of fragmented mp4 (moof/mdat pairs) with same channel count
4. During playback, append a new chunk of audio mp4 with initialization data (ftype, moov, moof & mdat) in same source buffer but with different audio channel count (e.g., channel count = 2)
5. MSE throws decode error



Actual results:

Firefox throws an error: 
Media resource mediasource:http://test.video.yahoo.com/f52f089b-9fdf-7d4d-bf5d-977f35d6c9a2 could not be decoded.


Expected results:

Audio channel switch should have happened without affecting playback.  This is suggested in w3c standard here https://w3c.github.io/media-source/#byte-stream-formats, in the third point under section "The user agent must support the following:".
Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core
prabubio, thanks for reporting this problem? With which version of Firefox do you see the error?
Hi Chris, 

It is 44.0.2.
Appreciate your help on this!
(In reply to Chris Peterson [:cpeterson] from comment #1)
> prabubio, thanks for reporting this problem? With which version of Firefox
> do you see the error?

this is by design. We do not have the appropriate backend to support audio configuration change.
Audio changes were disabled in bug 1185827.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Thanks for the details Jean-Yves! I will look forward for this enhancement.
You need to log in before you can comment on or make changes to this bug.