- From: Eric Carlson <eric.carlson@apple.com>
- Date: Tue, 21 Jan 2014 08:05:53 -0800
- To: Philip Jägenstedt <philipj@opera.com>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Aaron Colwell <acolwell@google.com>, public-html <public-html@w3.org>
On Jan 17, 2014, at 6:38 PM, Philip Jägenstedt <philipj@opera.com> wrote: > I hadn't thought about those case either. It would be nice (simple) to > just say that for all in-band tracks, when the buffered ranges are > updated, evict all cues which now do not overlap the buffered ranges. > Is that going to break something? > That does seem like the simplest (to implement and understand)) solution to this issue. I don’t know of anything that it will break. eric > > On Sat, Jan 18, 2014 at 3:56 AM, Eric Carlson <eric.carlson@apple.com> wrote: >> >> On Jan 16, 2014, at 6:17 PM, Philip Jägenstedt <philipj@opera.com> wrote: >> >> How about every time the buffered >> ranges change in MSE, all cues for in-band tracks which do not overlap >> with the new buffered ranges are thrown out? (Out-of-band and >> script-created tracks would best be left alone I think.) >> >> >> Would we only want to do this for MSE? What about live streams or very >> long downloaded files, where we may end up with a huge number of cues in >> memory for time ranges which are no longer buffered? >> >> eric >> >>
Received on Tuesday, 21 January 2014 16:06:23 UTC