- 24 Mar, 2021 26 commits
-
-
PiperOrigin-RevId: 364580585
samrobinson committed -
#minor-release PiperOrigin-RevId: 364561115
kimvde committed -
PiperOrigin-RevId: 364513299
gyumin committed -
Null was an alias for DEFAULT. Remove this for nullness safety in the API. The ExoPlayer implementation still checks for null and replaces it by DEFAULT, so this is ABI compatible. PiperOrigin-RevId: 364370017
krocard committed -
PiperOrigin-RevId: 364363882
Ian Baker committed -
PiperOrigin-RevId: 364324490
gyumin committed -
Comments made after submitting https://github.com/google/ExoPlayer/commit/e14180e5328c10742b84d2a0d8d54cb127f8bc55 PiperOrigin-RevId: 364276495
ibaker committed -
#minor-release PiperOrigin-RevId: 363915106
andrewlewis committed -
Issue: #8718 PiperOrigin-RevId: 363869093
aquilescanta committed -
#minor-release PiperOrigin-RevId: 363859522
kimvde committed -
The methods has been a no-op for while now and can be removed. PiperOrigin-RevId: 363673199
tonihei committed -
The main user of the Util method is the bandwidth meter to set the initial network type. If this is the first call to the NetworkTypeObserver, then we should also allow the first update to a known network type even if no reset on network type is activated. The other uses are analytics listeners that check the network type at certain events. This can just use the lookup method of the NetworkTypeObserver. PiperOrigin-RevId: 363670771
tonihei committed -
- Update the three `HttpDataSource` implementations to use the Content-Range response header to determine when this is the case. The Content-Range header is included when the status code is 416. See [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/416). - Update `ByteArrayDataSource` to conform to the requirement. - Update `DataSourceContractTest` to enforce the requirement. PiperOrigin-RevId: 363642114
olly committed -
This change fixes playback of playlists where segments have the extension and Content-Type of JPEG pictures (although in reality) they are transport streams. File inferrence before this change will cause an exception when assuming the inferred file type is one of the allowed HLS containers. #minor-release Issue: #8733 PiperOrigin-RevId: 363641277
aquilescanta committed -
PiperOrigin-RevId: 363639146
aquilescanta committed -
This brings in a fix for `NullPointerExceptions` within `WebView` callbacks in the IMA SDK. Issue: #8447 PiperOrigin-RevId: 363627446
andrewlewis committed -
PiperOrigin-RevId: 363606255
krocard committed -
PiperOrigin-RevId: 363480412
olly committed -
- SampleQueue.peek is replaced with SampleQueue.read with FLAG_PEEK. This also exposes peek functionality through SampleStream. - Use of DecoderInputBuffer.isFlagsOnly is replaced with FLAG_OMIT_SAMPLE_DATA. This flag can be used with or without FLAG_PEEK, where-as previously the read position would never be advanced for an isFlagsOnly buffer. - formatRequired is replaced with FLAG_FORMAT_REQUIRED. PiperOrigin-RevId: 363460105
olly committed -
The class is just an empty shell around the super class and can be removed. PiperOrigin-RevId: 363386440
tonihei committed -
In order to detect 5G-NSA, we need to remove Util.getNetworkType and replace it with a class that is actively listening to changes. The network type observation in DefaultBandwidthMeter already provides the right framework to integrate this and in order to facilitate further changes we move it to a separate Util class. The overall effect of this change should be a complete no-op. PiperOrigin-RevId: 363384567
tonihei committed -
Knowing the time-to-first-byte allows to update the available allocatable bandwidth to take this into account. PiperOrigin-RevId: 363225573
tonihei committed -
PiperOrigin-RevId: 363188096
bachinger committed -
PiperOrigin-RevId: 363144142
kimvde committed -
#minor-release PiperOrigin-RevId: 363141851
kimvde committed -
PiperOrigin-RevId: 363001266
olly committed
-
- 15 Mar, 2021 9 commits
-
-
PiperOrigin-RevId: 362972550
kimvde committed -
PiperOrigin-RevId: 362906290
kimvde committed -
Assert that opening the DataSource at the end of the resource results in only RESULT_END_OF_INPUT being read. open() and read() are still permitted to throw, although this permissiveness will be removed in subsequent commits. PiperOrigin-RevId: 362905314
olly committed -
This makes HLS playback less liable to become stuck if discontinuity tags are inserted at different times across media playlists. Issue: #8700 Issue: #8372 PiperOrigin-RevId: 362903428
olly committed -
According to the spec (section 8.4.2), high numeric values represent low priorities, so we need to flip this sort. Issue: #8704 #minor-release PiperOrigin-RevId: 362558370
ibaker committed -
`ImaAdsLoader` clears its `AdPlaybackState` when it's released but this could cause `AdsMediaSource` to look up information in the ad playback state that is no longer in bounds. Issue: #8693 #minor-release PiperOrigin-RevId: 362556286
andrewlewis committed -
When comparing stream bitrate with available (allocated) bandwidth, we need to take the playback speed into account. In the current calculation, this can happen on both sides of the equation, but we take the time to first byte into account, we need to move the speed into the available, allocated bandwidth. This change moves the speed adjustment to the bandwidth calculation side in AdaptiveTrackSelection. PiperOrigin-RevId: 362540071
tonihei committed -
PiperOrigin-RevId: 362527505
ibaker committed -
If none of the extractors successfully sniff the content then we will fall back to inferred file types in the following order: - Webvtt if the media comes from a SUBTITLE EXT-X-MEDIA. - The type of media declared in the HTTP "Content-Type" header. - The type of the media according to the file extension. - Transport stream. Issue: #8700 PiperOrigin-RevId: 362519769
aquilescanta committed
-
- 12 Mar, 2021 5 commits
-
-
Issue: #4133 PiperOrigin-RevId: 362478801
ibaker committed -
PiperOrigin-RevId: 362474276
gyumin committed -
Move offload events from Player.EventListener to ExoPlayer.AudioOffloadListener. PiperOrigin-RevId: 362472462
krocard committed -
Part of aligning HttpDataSource behavior will require adding logic that's common across the DataSource implementations. This change establishes a util class to house it, and moves a bit of existing logic that's related and can be easily shared into it. There is one small behavior change in this CL, which is that our handling of Content-Range response headers can now parse the body length if the "document size" part of the Content-Range is unknown, for example "bytes 5-9/*". Previously the pattern we were matching to required the "size" part to be set, for example "bytes 5-9/100", despite the fact we don't need or use it. PiperOrigin-RevId: 362396976
olly committed -
PiperOrigin-RevId: 362388683
olly committed
-