Skip to content

SDK / exoplayer

Go to a project
Switch branch/tag
  1. 02 Jul, 2019 22 commits
  3. 21 Jun, 2019 9 commits
  5. 19 Jun, 2019 4 commits
  7. 18 Jun, 2019 5 commits
    • Update release notes for 2.10.2 cherrypicks · 9308ff26 
      PiperOrigin-RevId: 253808562
      olly committed
    • Prevent negative renderer timestamps when seeking back. · 9ed7b42a 
      We are currently queuing periods in a way such that the new start position
lines up with the end of the previous period (to ensure continuous playback).
However, if the start position of the new period is larger than the total of
all previously played period durations, we may end up with negative renderer
timestamps when seeking back to the beginning of this new period. Negative
timestamps should be avoided as most decoders have problems handling them
correctly.

This change forces a renderer reset if we detect such a seek to a negative
renderer time and also resets the renderer offset to 0 every time all
renderers are disabled, as this is the only time where we can savely change
the offset of an existing media period.

Also, if playback starts with an ad, we choose the content position as
renderer offset to prevent the whole issue from occurring for the seek-behind-
midroll case.

Issue:#6009
Issue:#5323
PiperOrigin-RevId: 253790054
      tonihei committed
    • Let AudioTrack write headers on SDK_INT >= 26 · 38000b87 
      Issue: #6031
PiperOrigin-RevId: 253784986
      olly committed
    • Fix application of maxAudioBitrate for adaptive audio track groups · 5aeaa6e8 
      Issue:#6006
PiperOrigin-RevId: 253781533
      aquilescanta committed
    • Prevent negative total buffered duration at the point where it is calculated. · b89dc8fb 
      In some edge cases the renderer position may be slightly ahead of the
buffered position and the total buffered duration is thus negative. We already
filter that in ExoPlayerImpl for the publicly accessible value. However, we
forward the unfiltered value to other components like the LoadControl, which
may be confusing.

Issue:#6015
PiperOrigin-RevId: 253780460
      tonihei committed