olly d04fde1a53 Distinguish dense vs sparse tracks for buffering purposes ...

- For audio/video, we should report the minimum largest
  queued timestamp. This ensures that buffering continues
  rather than stops in the case of bad sample interleaving.
- If there are "sparse" tracks then they should be ignored
  for this calculation, otherwise the buffered position can
  end up getting stuck at some small value (e.g. if there's
  a text track containing a single sample with a small
  timestamp).
- In the edge case that there are only "sparse" tracks, we
  probably want to take the maximum largest queued time
  instead.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=130094266

2016-08-31 15:25:05 +01:00

..

src

Distinguish dense vs sparse tracks for buffering purposes

2016-08-31 15:25:05 +01:00

build.gradle

Enable test coverage report generation for library project.

2016-08-31 13:24:06 +01:00