1. 04 Aug, 2016 1 commit
  2. 29 Jul, 2016 5 commits
  3. 26 Jul, 2016 1 commit
  4. 25 Jul, 2016 4 commits
  5. 21 Jul, 2016 5 commits
  6. 20 Jul, 2016 1 commit
  7. 15 Jul, 2016 2 commits
  8. 30 Jun, 2016 1 commit
  9. 29 Jun, 2016 1 commit
  10. 20 Jun, 2016 1 commit
  11. 09 Jun, 2016 3 commits
  12. 08 Jun, 2016 2 commits
  13. 06 Jun, 2016 1 commit
  14. 02 Jun, 2016 4 commits
  15. 31 May, 2016 3 commits
  16. 27 May, 2016 2 commits
  17. 26 May, 2016 3 commits
    • jrivera committed
    • Segment durations are defined in the spec as being less than or equal to target-duration
      Jon-Carlos Rivera committed
    • * Fudge segments that are reported as having a zero-second duration
        * The fetcher logic basically ignores segments with a duration of zero. Give them a tiny duration so that the fetcher will "see" these segments.
      * Added tests for and fixed getSegmentBufferedPercent_ calculations
      * Now returns the percent buffered of the entire segment duration instead of the "adjusted" duration
      * Handles segments reported as having a zero-duration
      * Reduced the number of segments that we will attempt to "timeCorrect" when the segment chosen by `checkBuffer_` is already more than 90% buffered to 1
      * No longer trigger errors from `timeCorrection_` handling, returning to the previous behavior
      * Use the tech's setCurrentTime function in segment loaders
      * Moved getSegmentBufferedPercent to `Ranges` module
      * Moved correction for zero-duration segments from parse-stream to parser proper
      Jon-Carlos Rivera committed