Skip to content

SDK / exoplayer

Go to a project
Switch branch/tag
  1. 04 Aug, 2021 4 commits
    • 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
  3. 02 Aug, 2021 7 commits
  5. 29 Jul, 2021 3 commits
  7. 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
  9. 27 Jul, 2021 17 commits
  11. 23 Jul, 2021 7 commits