[Bug 26921] [InbandTracks] DASH trackId

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

Bob Lund <b.lund@cablelabs.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Bob Lund <b.lund@cablelabs.com> ---
(In reply to Cyril Concolato from comment #6)
> (In reply to Bob Lund from comment #5)
> > This is a good introduction. The wording suggest that track objects are
> > created differently in the two cases, however. 
> Well, they are not exactly created in the same way: in one case it's the UA
> that does it all by itself; in the other case, it's done by the UA using to
> MSE and with instructions from the Web Application. I've tried rewording it.
> 
> > The following  is a slight
> > modification.
> > 
> >  [[MPEGDASH]] defines formats for a media manifest, called MPD (Media
> > Presentation Description), which references media containers, called media
> > segments based on [[MPEG2TS]] or [[ISOBMFF]]. 
> In the initial text I meant to say that MPEG-DASH defines formats for some
> media segments not all. I've clarified that.
> 
> > The user agent 
> Ok, I've changed "browser" to "user agent".
> 
> > or the Web
> > application (using MSE [[MSE]]) may process the media manifests and fetch
> > media segments. 
> Strictly speaking, the Web application does not process the media manifests
> and fetch the segments using MSE. That's done using XML parsing and XHR.
> 
> > When the user agent processes the MPD and fetches media
> > segments, it creates HTML track objects based on media segment and MPD data.
> I think the hint about the adaptive handling by the UA is important as it
> indicates that representations as such won't be exposed.
> 
> > When the Web application processes the MPD and fetches media segments, the
> > user agent also creates HTML track objects using data in media segments 
> > passed to it by the Web application. The Web application may set default
> > track attributes from MPD data, using the trackDefaults object, that will be
> > used by the user agent to set attributes not set from initialization segment
> > data.
> > 
> > Please update the PR if this is agreeable.
> I've update the PR. Hope this is fine with you.

PR has been merged.

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

Received on Thursday, 30 October 2014 21:15:55 UTC