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

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

--- Comment #12 from Bob Lund <b.lund@cablelabs.com> ---
(In reply to Jon Piesing (HbbTV) from comment #9)
> This is nothing about text tracks or Cues - it's about video and audio
> tracks primarily.
> 
> There are two different cases to address;
> 1) A track whose content is currently being presented by the UA (e.g. the
> currently selected audio track)
> 2) A track whose content is not currently being presented by the UA (e.g. i)
> audio tracks other than the one currently being presented or ii) all audio
> tracks when none are yet being presented)
> 
> I believe this change reasonably addresses the first case.
> However what about the second case?
> 
> 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.

It's not clear what you mean by "fetching data". Are you referring to creating
the track? Or, are you referring to playing the media. In the case of creating
a track, a track isn't created for each representation - only for each
adaptation set or content component. The UA must create a track representation
for each AdaptationSet/ContentComponent in order for the application or user to
select the appropriate ones for rendering.

In any case, this issue is not introduced by the resolution of this bug. This
bug should be closed with the resolution proposed and you should submit a new
if you feel that the discussion of when to create a track should be pursued.

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

Received on Wednesday, 24 September 2014 20:03:32 UTC