- 25 Oct, 2022 3 commits
-
-
* Add `BitmapLoader` in `MediaSession.Builder` and `MediaLibrarySession.Builder`. * Pass `BitmapLoader` into the constructor of `MediaSession`, `MediaSessionImpl`, `MediaLibrarySession` and `MediaLibrarySessionImpl`. * Add an interface method `loadBitmapFromMetadata(MediaMetadata)` in `BitmapLoader`. * Remove the reference of `BitmapLoader` in `DefaultMediaNotificationProvider`. PiperOrigin-RevId: 483654596 (cherry picked from commit 3f69df72)
tianyifeng committed
- 24 Oct, 2022 2 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 8723e74b)
samrobinson committed
- 31 Oct, 2022 1 commit
-
- 24 Oct, 2022 1 commit
-
- 21 Oct, 2022 3 commits
-
-
* Add `CacheBitmapLoader`. * Add `CacheBitmapLoaderTest`. * Remove the `BitmapLoadRequest` and some bitmap caching logic in `DefaultMediaNotificationProvider` since we moved all of them in `CacheBitmapLoader`. * Modify `DefaultMediaNotificationProviderTest`. PiperOrigin-RevId: 482787445 (cherry picked from commit ca4edff1)
tianyifeng committed
- 24 Oct, 2022 2 commits
-
-
PiperOrigin-RevId: 482490230 (cherry picked from commit d21c9488)
Rohit Singh committed -
PiperOrigin-RevId: 482481703 (cherry picked from commit faa43022)
Rohit Singh committed
-
- 20 Oct, 2022 2 commits
-
-
PiperOrigin-RevId: 482461219 (cherry picked from commit b9c94545)
michaelkatz committed
-
- 19 Oct, 2022 7 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 bb215857)
huangdarwin committed -
The MediaNotficationManager stops the service from the foreground calling Service.stopForeground(boolean) which is deprecated in API 33. This change calls Service.stopForeground(int), which was added in API 24. #minor-release PiperOrigin-RevId: 482190332 (cherry picked from commit 601eaba7)
christosts committed -
`transformationMatrix` is not ambiguous, as there's no other local transformationMatrix variable nearby. PiperOrigin-RevId: 482184602 (cherry picked from commit e39826a8)
huangdarwin committed
- 24 Oct, 2022 1 commit
-
-
PiperOrigin-RevId: 482165983 (cherry picked from commit 1565a2da)
Rohit Singh committed
-
- 19 Oct, 2022 1 commit
-
-
This was originally added in https://github.com/androidx/media/commit/4fd7d777b669f6adacc3737a7e15b04a57f030fb, but it hasn't done anything since https://github.com/androidx/media/commit/98ee159df161c7c8806c0b0490b642738822f6a7 (when the instanceof ExoPlayer check was removed). PiperOrigin-RevId: 482161662 (cherry picked from commit a5b09b8c)
ibaker committed
-
- 18 Oct, 2022 8 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 cce79a70)
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 f850206c)
tonihei committed -
This is the first commit out of two. This change adds the missing event flags for the onEvents() callback when MediaController is connected to a media3 session (see MediaControllerImplBase). I updated the MediaControllerListenerTest and MediaControllerStateMaskingTest with assertions that on onEvents() is called alongside individual Player.Listener callbacks. There will be a follow-up change for the case where a MediaController is connected to a legacy MediaSession (MediaControllerImplLegacy). I've split this in two separate changes to make the size of the commit manageable for reviewing. #minor-release PiperOrigin-RevId: 481933437 (cherry picked from commit 46d5a0e3)
christosts committed -
(Also, make some public methods private) PiperOrigin-RevId: 481912071 (cherry picked from commit 93ee1f48)
huangdarwin committed -
#cleanup PiperOrigin-RevId: 481882181 (cherry picked from commit 7ac7e643)
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 3399f4ec)
kimvde committed
-
- 17 Oct, 2022 1 commit
-
- 14 Oct, 2022 5 commits
-
-
PiperOrigin-RevId: 481143798 (cherry picked from commit f9724e9f)
huangdarwin committed
- 17 Oct, 2022 1 commit
-
-
PiperOrigin-RevId: 481115402 (cherry picked from commit 172cae47)
Marc Baechinger committed
-
- 13 Oct, 2022 2 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 409c9f87)
tonihei committed
-