- 25 Sep, 2020 16 commits
-
-
PiperOrigin-RevId: 333485323
kim-vde committed -
PiperOrigin-RevId: 333480727
tonihei committed -
This issue has been observed on a test app stress testing setEndOfStream. The issue has not been observed on ExoPlayer, probably due to timing differences, but it is fixed preventively. #exo-offload PiperOrigin-RevId: 333472136
krocard committed -
This seems to be an exact copy of sample.adts. Update the test to use the same sample but just output to a different dump file. PiperOrigin-RevId: 333469714
ibaker committed -
These are from https://medium.com/google-exoplayer/improved-japanese-subtitle-support-7598fee12cf4 PiperOrigin-RevId: 333296789
ibaker committed -
PiperOrigin-RevId: 333272292
andrewlewis committed -
This allows the player to load the unfinished segment of a low-latency DASH stream. PiperOrigin-RevId: 333077153
tonihei committed -
The shrinking didn't mention that users of the existing ProgressiveMediaSource need to pass in ExtractorsFactory.EMPTY to the SimpleExoPlayer.Builder as well. Also updated the release notes to mention the changed shrinking guidance. Issue: #7937 PiperOrigin-RevId: 333060452
tonihei committed -
PiperOrigin-RevId: 333051018
andrewlewis committed -
We have a workaround for uneven sample stream durarions in playlists that assumes a renderer allows playback if it's reading ahead or waiting for the next stream. https://github.com/google/ExoPlayer/commit/652c2f9c188bf9d9d6e323ff5333e5026454a082 changed this logic to no longer require to wait until the next stream is prepared due to a change in how we advance media periods in the queue. However, the code falsely still requires the next stream to exist (even if it's not prepared). This can cause a stuck buffering state when the difference in the duration of the streams is more than what we buffer ahead because we never create the next stream in such a case. Note: DefaultMediaClock.shouldUseStandaloneClock has roughly the same logic and also doesn't require the next stream to be present. Also fix a test that seemed to rely on this stuck buffering case to test stuck buffering detection. Changed the test to not read the end of stream to ensure it runs into the desired stuck buffering case. Issue:#7943 PiperOrigin-RevId: 333050285
tonihei committed -
This allows to use the same logic from multiple places without duplicating it, encapsulates in its logical place, and allows to change the available segments based on the new availabilityTimeOffset value. The overall effect of this change is a no-op. PiperOrigin-RevId: 333044186
tonihei committed -
PiperOrigin-RevId: 333036751
kim-vde committed -
PiperOrigin-RevId: 333031399
ibaker committed -
https://github.com/google/ExoPlayer/commit/f2c51560c21bdd757c30678223345fa8f59fb82b
PiperOrigin-RevId: 333031301
tonihei committed -
PiperOrigin-RevId: 333029935
tonihei committed -
PiperOrigin-RevId: 333023580
olly committed
-
- 23 Sep, 2020 2 commits
-
-
Add support for schemeIdUri="urn:mpeg:mpegB:cicp:ChannelConfiguration". https://dashif.org/identifiers/audio_source_metadata/ and clause 8.2 in ISO/IEC 23001-8.
ybai001 committed -
Dev v2
ybai001 committed
-
- 21 Sep, 2020 7 commits
-
-
PiperOrigin-RevId: 332940209
olly committed -
We're not using regex so there's no need to use replaceAll() PiperOrigin-RevId: 332865724
ibaker committed -
Without this patch, playback would be frozen indefinitely until the user manually pauses and unpauses it. This has the side effect of disabling offload until the next stop due to the workaround of disabling offload when it encounters a failure. As an audio server crash is considered very infrequent, especially in stable conditions like an audio only playback, it is unlikely that disabling offload is an issue. PiperOrigin-RevId: 332857094
krocard committed -
Issue: #7939 PiperOrigin-RevId: 332838586
bachinger committed -
PiperOrigin-RevId: 332814223
Oliver Woodman committed -
PiperOrigin-RevId: 332416139
kimvde committed -
PiperOrigin-RevId: 332254072
kimvde committed
-
- 20 Sep, 2020 1 commit
-
-
Frieder Bluemle committed
-
- 17 Sep, 2020 3 commits
-
-
PiperOrigin-RevId: 332211266
ibaker committed -
I didn't copy-paste the whole of https://github.com/google/guava/wiki/UsingProGuardWithGuava because this line seems relevant based on our current usage. Lots of that file seems to relate to classes that are strongly discouraged on Android: https://github.com/google/guava/wiki/Android#specifics I've only added this to the `common` module, since everyone that uses ExoPlayer must depend on that. This avoids duplicating this line into every module that has a Guava dependency. Also remove some other warning suppressions that are defined in both `core` and `common`. Issue: #7904 PiperOrigin-RevId: 332203086
ibaker committed -
The character sequence \h is used for "unbreakable space". Replace these sequences with space to avoid strings of \h showing up on screen.
Peter Bennett committed
-
- 16 Sep, 2020 11 commits
-
-
PiperOrigin-RevId: 332015471
olly committed -
PiperOrigin-RevId: 332014290
olly committed -
PiperOrigin-RevId: 332012857
aquilescanta committed -
Since gradle 4.0, CMake imported libraries are bundled in the APK, so manually bundling them causes a duplication which breaks the build. Issue: #7906 PiperOrigin-RevId: 332012375
aquilescanta committed -
PiperOrigin-RevId: 331955966
christosts committed -
This value is needed to figure out the last available segment for low-latency live streaming. It may be present in each BaseURL tag and each SegmentList or SegmentTemplate, with the latter one taking precedence. The value is saved as part of MultiSegmentBase where it will be used to retrieve the last available segment index in future changes. PiperOrigin-RevId: 331809871
tonihei committed -
Issue: #7906 PiperOrigin-RevId: 331775990
olly committed -
Issue: #7902 PiperOrigin-RevId: 331771187
olly committed -
This test is intended to check that DefaultLoadControl will cause playback to fail as "stuck buffering" rather than OOM-ing, in the case that its target buffer size is reached and playback still hasn't started. Unfortunately, the target buffer size is ~130MB, and when running on some setups an OOM actually ends up happening before this much memory is allocated. This change makes the target buffer size much smaller to avoid the problem. PiperOrigin-RevId: 331748208
olly committed -
PiperOrigin-RevId: 331591005
olly committed -
PiperOrigin-RevId: 331539036
christosts committed
-