W3C home > Mailing lists > Public > public-html-media@w3.org > April 2014

Re: [MSE] Alternate proposal for resolving Bug 24370

From: Aaron Colwell <acolwell@google.com>
Date: Fri, 25 Apr 2014 07:25:14 -0700
Message-ID: <CAA0c1bA6Sxon=6ta3Y2Xu=0214ma5gT9BzZwVehVZoKCkTv5iQ@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: "<public-html-media@w3.org>" <public-html-media@w3.org>
On Thu, Apr 24, 2014 at 9:46 PM, Silvia Pfeiffer

> On Fri, Apr 25, 2014 at 2:32 PM, Aaron Colwell <acolwell@google.com>
> wrote:
> >
> > No. The web application adds default information to the trackDefaultList
> on
> > the SourceBuffer. The SourceBuffer code consults these defaults when data
> > gets appended that would result in xxxTrack objects getting created (ie
> when
> > the initialization segment received algorithm is invoked.)
> OK, thanks, I get it. Why would .trackDefaults be in every
> SourceBuffer object rather than just in the MediaSource ?

Because different SourceBuffer objects can have byte streams that contain
the same underlying byteStreamTrackID and there would be no way to
differentiate the two.
For example, in the case were a SourceBuffer is used for the audio track
and a different SourceBuffer is used for the video track, it is highly
likely that the track in each byte stream will have a byteStreamTrackID of
'1' because in each case there is only 1 track. Putting the defaults on the
MediaSource would require specifying a SourceBuffer parameter to
TrackDefaultList to disambiguate this case, which seems a little odd to me
since this is really a matter that is internal to the SourceBuffer and not
a MediaSource wide concern.


> Silvia.
Received on Friday, 25 April 2014 14:25:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:48 UTC