- 25 Oct, 2022 2 commits
-
- 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
-
- 14 Oct, 2022 5 commits
-
-
PiperOrigin-RevId: 481143798 (cherry picked from commit 026699ba)
huangdarwin committed
- 20 Oct, 2022 1 commit
-
-
PiperOrigin-RevId: 481115402 (cherry picked from commit 9861f88f)
Marc Baechinger committed
-
- 13 Oct, 2022 4 commits
-
-
We already have logic to end all session except the current one if the current one doesn't have a MediaPeriodId yet. This is assuming that this only happens after a seek on the app side where the player doesn't have detailled knowledge about the MediaPeriodIds yet. Currently this logic isn't triggered if the window we are coming from doesn't have its MediaPeriodId either as we run into another check that keeps sessions around until we have a valid windowSequenceNumber. Swapping both conditions fixes this case without breaking any of the other known transition scenarios. Issue: androidx/media#180 PiperOrigin-RevId: 480866465 (cherry picked from commit 6070d911)
tonihei committed
-
- 12 Oct, 2022 3 commits
-
-
When debugging and fixing Issue: google/ExoPlayer#10666 I wanted to write a regression test, but needed to add a test first... This is just a small bit of coverage to start with. It checks the field/channel filtering works correctly, but doesn't check any styling info. It also doesn't test 'pop on' subtitles (i.e. when the subtitle isn't shown until a 'end of subtitle' signal is received). PiperOrigin-RevId: 480644568 (cherry picked from commit 6052212c)
ibaker committed -
Most demo videos aren't very long, and the default demo video is only 10 seconds. Shorten the maximum trim duration to 10 seconds, to demonstrate transformer functionality more easily, and allow this to be used more easily when trimming short sections of a longer video (ex. to make test clips) PiperOrigin-RevId: 480602037 (cherry picked from commit 3142a212)
huangdarwin committed -
Player controls are somewhat distracting when showing the difference between the input and output video, as they obscure and darken the video players. PiperOrigin-RevId: 480597804 (cherry picked from commit 91a61cec)
huangdarwin committed
-
- 11 Oct, 2022 1 commit
-
-
Before, slider values were read as `floor()`'ed `longValue()`s, so that trimming to intervals less than one second would be interpreted as a request for a zero- duration trim. Also, rename `radiusRange` references here to `trimRange`, since this is not a radius range. PiperOrigin-RevId: 480401556 (cherry picked from commit 6c59f9ec)
huangdarwin committed
-