[Bug 26718] [InbandTracks] Container information vs. Manifest information

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26718

--- Comment #10 from Cyril Concolato <cyril.concolato@telecom-paristech.fr> ---
(In reply to Jon Piesing (HbbTV) from comment #9)
> Suppose a DASH MPD has 5 audio adaptation sets, 3 for different languages
> and 2 for accessibility and only one of the 5 is being presented.
> 
> If the UA is to create an AudioTrack for each of these 5 adaptation sets
> then the change made would require it to fetch data for each of the 4
> adaptation sets not being presented. I believe that is wrong.
Why? In many cases, you can't know for sure that the track will be playable
until you've downloaded the initialization segment anyway, so you shouldn't
expose it. In GPAC, when we build the GUI for selecting a track we base the
information on the MP4 not the MPD. For MSE-based implementations in browsers I
would wait for the SourceBuffers to be created and initialized too. You can
decide to expose the tracks based on the MPD information only, in this case,
make sure your UI can be changed when the real data arrives.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 24 September 2014 15:15:39 UTC