- 31 Oct, 2022 3 commits
-
-
If an app sets a compileSdkVersion that is lower than the one used to create AARs of its dependencies, the build process may produce invalid outputs, for example by stripping methods from the APK that are only called when the app is running on a new API version. To avoid this issue, we can enforce that the compileSdk of apps or libraries depending on ExoPlayer/Media3 is at least the same as the one we used for compilation when creating the AAR. Issue: google/ExoPlayer#10684 PiperOrigin-RevId: 485100067 (cherry picked from commit 23d39cae)
tonihei committed
-
- 28 Oct, 2022 3 commits
-
-
PiperOrigin-RevId: 484512661 (cherry picked from commit 2390322a)
samrobinson committed -
#minor-release PiperOrigin-RevId: 484483080 (cherry picked from commit fc1eca10)
andrewlewis committed
- 27 Oct, 2022 3 commits
-
-
This change makes adding ad events in live streams more robust by allowing ad groups to grow in number of ads if more ad events are received than initially announced by the SDK. With the IMA prefetch feature, an AdPod can grow in size in certain conditions like from initially 2 ads to 4 ads being part of the ad group. With this change, if an additional ad event arrives while the ad group is still being played, the ad group is expanded. If the event arrives late and the ad group is already completed, a new group is created for the remaining ads. This also covers the case where we join the live stream while an ad is being played and we missed at least one LOADED event from the SDK. Ads of the group before the first LOADED event are ignored in such a case. PiperOrigin-RevId: 484214760 (cherry picked from commit 136addf6)
bachinger committed
- 26 Oct, 2022 3 commits
-
-
PiperOrigin-RevId: 483983486 (cherry picked from commit c9585d01)
samrobinson committed -
From ANSI-CTA-608-E R-2014 section 8.4: > When closed captioning is used on line 21, field 2, it shall conform > to all of the applicable specifications and recommended practices as > defined for field 1 services with the following differences: > 1. The non-printing character of the miscellaneous control-character > pairs that fall in the range of 0x14, 0x20 to 0x14, 0x2F in field 1, > shall be replaced with 0x15, 0x20 to 0x15, 0x2F when used in field > 2. > 2. The non-printing character of the miscellaneous control-character > pairs that fall in the range of 0x1C, 0x20 to 0x1C, 0x2F in field > 1, shall be replaced with 0x1D, 0x20 to 0x1D, 0x2F when used in > field 2. This basically means that `cc1=0x15` in field 2 should be interpreted as `cc1=0x14` in field 1, and same for `0x1D -> 0x1C`. The `isMiscCode` method above already handles this by ignoring the LSB (the only difference between `0x14` and `0x15`, and `0x1C` and `0x1D`) by AND-ing with `0xF6` instead of `0xF7`. This change uses the same trick in `isServiceSwitchCommand`. Issue: google/ExoPlayer#10666 #minor-release PiperOrigin-RevId: 483927506 (cherry picked from commit 7c6d492f)
ibaker committed
-
- 25 Oct, 2022 4 commits
-
-
Split inner interface into separate file, which will go in common module. The old interface will be deprecated and extends the new. #cleanup PiperOrigin-RevId: 483732226 (cherry picked from commit ad52b68c)
samrobinson committed -
PiperOrigin-RevId: 483699606 (cherry picked from commit dda17db2)
samrobinson committed
-
- 24 Oct, 2022 3 commits
-
-
Although it can be useful to check the output format, it's not required or needed. For some AudioProcessor implementations, it is stated/obvious that the output format will match the input, in which case there is no a need to check the return value. #cleanup PiperOrigin-RevId: 483403679 (cherry picked from commit a7bfa12e)
samrobinson committed
- 21 Oct, 2022 1 commit
-
- 24 Oct, 2022 2 commits
-
-
PiperOrigin-RevId: 482490230 (cherry picked from commit fd2ba37b)
Rohit Singh committed -
PiperOrigin-RevId: 482481703 (cherry picked from commit a413b478)
Rohit Singh committed
-
- 20 Oct, 2022 2 commits
-
-
PiperOrigin-RevId: 482461219 (cherry picked from commit 0eb30eac)
michaelkatz committed
-
- 19 Oct, 2022 5 commits
-
-
Make it easier to support use of RGBA_101012 rather than RGBA_8888 for EGL contexts, displays, and surfaces. This tangentially supports adding HDR tests, by slightly simplifying the color selection logic we'd have to add in HDR tests. PiperOrigin-RevId: 482219428 (cherry picked from commit 9e1adee4)
huangdarwin committed -
`transformationMatrix` is not ambiguous, as there's no other local transformationMatrix variable nearby. PiperOrigin-RevId: 482184602 (cherry picked from commit c698ec51)
huangdarwin committed
- 20 Oct, 2022 1 commit
-
-
PiperOrigin-RevId: 482165983 (cherry picked from commit 405455b0)
Marc Baechinger committed
-
- 19 Oct, 2022 1 commit
-
-
This was originally added in https://github.com/google/ExoPlayer/commit/4fd7d777b669f6adacc3737a7e15b04a57f030fb, but it hasn't done anything since https://github.com/google/ExoPlayer/commit/98ee159df161c7c8806c0b0490b642738822f6a7 (when the instanceof ExoPlayer check was removed). PiperOrigin-RevId: 482161662 (cherry picked from commit 7d5f1a24)
ibaker committed
-
- 18 Oct, 2022 7 commits
-
-
Before, they used `width` and `height`, which was inconsistent with other pixel tests, and less descriptive. Refactoring change only. No functional change intended. PiperOrigin-RevId: 481970243 (cherry picked from commit 620d8c94)
huangdarwin committed -
Currently, repeating the same item (via seekNext/Previous) implicitly results in a seek to the default position of the current item, which looks exactly the same as a direct seek. As a result, we don't send onMediaItemTransition as we would for every other seekNext/Previous call. This can be fixed by explicitly marking the repeat case in the internal BasePlayer/ExoPlayerImpl methods, so that the callback can be triggered. Issue: google/ExoPlayer#10667 PiperOrigin-RevId: 481951788 (cherry picked from commit 76ce0cc6)
tonihei committed -
(Also, make some public methods private) PiperOrigin-RevId: 481912071 (cherry picked from commit a404fde4)
huangdarwin committed -
#cleanup PiperOrigin-RevId: 481882181 (cherry picked from commit b6bd3586)
samrobinson committed -
- The naming DefaultMuxer is more consistent with the rest of Transformer codebase (e.g. DefaultEncoderFactory). - By hiding the implementation details of DefaultMuxer, the transition to in-app Muxer will be seamless for apps using DefaultMuxer. - The current plan is that DefaultMuxer will become the in-app muxer. PiperOrigin-RevId: 481838790 (cherry picked from commit b4d7f066)
kimvde committed
-
- 17 Oct, 2022 2 commits
-