Skip to content

SDK / exoplayer

Go to a project
Switch branch/tag
  1. 08 Jun, 2021 1 commit
  3. 03 Jun, 2021 16 commits
  5. 02 Jun, 2021 8 commits
  7. 01 Jun, 2021 2 commits
    • Remove fully qualified package in link tag to avoid reformatting · 2fb61b8a 
      PiperOrigin-RevId: 376932836
      bachinger committed
    • Keep secure MediaCodec instances when disabling the renderer · 58e307c6 
      A renderer is disabled (without being reset) in two situations:
* When transitioning into a period that starts with a discontinuity
* When stopping the player with setForegroundMode(true)

Before this change the behaviour of `MediaCodecRenderer` when disabled
(but not reset) depended on whether the content being decoded had an
associated `DrmSession`:
* For content without an associated DRM session the MediaCodec instance
  was kept alive.
* For content with an associated DRM session, the MediaCodec instance
  was released. This was to prevent the DRM session from staying alive
  and continuing to make license refresh network requests while the
  player was stopped in 'foreground mode'.

This change removes the second bullet, and keeps MediaCodec instances
alive in both the secure and insecure case. This will result in the
DRM machinery making occasional license refresh network requests (at
a frequency defined by the license policy) while the player is stopped
and in 'foreground mode'. This network usage is considered to be a
'limited resource' as described by the `ExoPlayer#setForegroundMode`
javadoc.

This means that switches between secure content (or between secure and
clear content when `MediaItem.drmConfiguration.sessionForClearTypes`
indicates a secure decoder should be used for clear content) should
keep the same video decoder, thus avoiding the 'black flash' that occurs
on some devices when switching the surface away from a secure decoder.

Issue: #8842

#minor-release

PiperOrigin-RevId: 376825501
      ibaker committed
  9. 27 May, 2021 13 commits