Skip to content

SDK / exoplayer

Go to a project
Switch branch/tag
  1. 16 Sep, 2021 4 commits
  3. 11 Aug, 2021 2 commits
  5. 10 Aug, 2021 2 commits
  7. 06 Aug, 2021 1 commit
  9. 05 Aug, 2021 2 commits
  11. 04 Aug, 2021 10 commits
    • Simplify network-related error codes · 17723c08 
      This change removes ERROR_CODE_IO_NETWORK_UNAVAILABLE,
ERROR_CODE_IO_NETWORK_CONNECTION_CLOSED, and ERROR_CODE_IO_DNS_FAILED
in favor of keeping only ERROR_CODE_IO_NETWORK_CONNECTION_FAILED.

PiperOrigin-RevId: 388715972
      aquilescanta committed
    • Merge pull request #9247 from colinbarr:dev-v2-rtsp-fmtp-trailing-semicolon · f23ab8e2 
      PiperOrigin-RevId: 388713101
      Christos Tsilopoulos committed
    • Tweak use of TimestampAdjuster for seeking · ba3f8682 
      - Fix use of getTimestampOffsetUs in TsExtractor where
  getFirstSampleTimestampUs should have been used.
- Don't reset TimestampAdjuster if it's in no-offset mode.
- Improve comment clarity

#minor-release

PiperOrigin-RevId: 388682711
      olly committed
    • Set HlsSampleStreamWrapper.trackType for audio-only playlists · 5689e093 
      For audio-only playlists, when formats are communicated to the app with
AnalyticsListener.onDownstreamFormatChanged(), the passed MediaLoadData
do not indicate this is an audio track and therefore the
PlaybackStatsListener cannot derive audio format-related information.

This change sets the main SampleStreamWrappers track type to AUDIO, if
the master playlist contains only audio variants.

Issue: #9175

#minor-release

PiperOrigin-RevId: 388676060
      christosts committed
    • Change how AnalyticsCollector releases listeners · 5b2b882e 
      The AnalyticsCollector releases listeners lazily so that listener
callbacks triggered on the application looper after
SimpleExoPlayer.release() are still handled. The change in ListenerSet
to post the onEvents callback on the front of the application looper
changed (correctly) how onEvents are propagated, however this made
the AnalyticsCollector deliver onEvents with out-of-order EventTimes.

This change fixes AnalyticsCollector to trigger onPlayerReleased() and
the matching onEvents() event in the correct order.

#minor-release

PiperOrigin-RevId: 388668739
      christosts committed
    • Use AudioTrack.isDirectPlaybackSupported on TVs only · 59324069 
      Issue: #9239

PiperOrigin-RevId: 388437614
      andrewlewis committed
    • Add `font-size` support to WebVTT `CssParser`. · 95dcd896 
      This CL addresses the github issue [#8946](https://github.com/google/ExoPlayer/issues/8964). That issue requests support for `font-size` CSS property in WebVTT subtitle format. This CL:
* Adds support for `font-size` property by extending capabilities of WebVTT `CssParser`. Implementation of `font-size` property value parsing is based on the one in `TtmlDecoder`.
* Adds unit test along with test file containing WebVTT subtitles with all currently supported `font-size` units.

#minor-release

PiperOrigin-RevId: 388423859
      apodob committed
    • HLS: Avoid stuck-buffering issues · 8732f2f0 
      Issue: #8850
Issue: #9153
#minor-release
PiperOrigin-RevId: 388257563
      olly committed
    • Simplify TimestampAdjuster logic · e95c42ef 
      - Use timestampOffsetUs == C.TIME_UNSET directly as the way of
  determining whether the adjuster has determined the offset,
  rather than relying on lastSampleTimestampUs checks for this.
- Remove comment referring to lastSampleTimestampUs as holding
  the "adjusted PTS". Its value may not have originated from a PTS
  timestamp. It's also confusing to refer to it as "adjusted"
  given timestampOffsetUs has not been applied to it.
- Fix PassthroughSectionPayloadReader to make sure it'll never
  output a sample with an unset timestamp.

#minor-release

PiperOrigin-RevId: 388226180
      olly committed
    • Fix resetting TimestampAdjuster with DO_NOT_OFFSET · ff71425d 
      Prior to this change, an initalized TimestampAdjuster that's then
reset with DO_NOT_OFFSET would incorrectly continue to apply the
offset.

Also add a test case for this issue, and for some other simple use
cases.

#minor-release

PiperOrigin-RevId: 388182645
      olly committed
  13. 02 Aug, 2021 7 commits
  15. 29 Jul, 2021 3 commits
  17. 28 Jul, 2021 2 commits
    • Fix parameter names on overridden methods · 9c27cfcd 
      The dokka javadoc generation tool complains when parameter names don't match between a method and its override. This change updates occurrences where there is currently a mismatch.

Notable renamings that might be controversial:
- `onPlaybackStateChanged(int state)` to `onPlaybackStateChanged(int playbackState)` affected a lot of lines but seems more consistent with other '-Changed' methods.
- `handleMessage(int messageType, Object payload)` to `handleMessage(int messageType, Object message)`
- `ExtractorInput` and `DataSource` inherit `DataReader` which had `read(byte[] target, ...`, while data sources normally called the first parameter `buffer`. I have standardized these all to use `buffer` even though it looks out of place in the `ExtractorInput` interface (which has more `read` methods with `target`).

PiperOrigin-RevId: 387290360
      andrewlewis committed
    • Throw IllegalStateException from Util.gzip() instead of AssertionError · 41fe5aa1 
      The documentation on ByteArrayOutputStream and GZIPOutputStream isn't
completely clear that an IOException will *never* happen, so
AssertionError seems a bit strong - but it seems very unlikely, so we
just use IllegalStateException instead.

#minor-release

PiperOrigin-RevId: 387169297
      ibaker committed
  19. 27 Jul, 2021 7 commits