49bf83a169
- Applications should generally use DefaultMediaSourceFactory, or their own custom implementation if they need one. Having the media2 extension implement its own version directly doesn't seem that useful. - Remove support for CallbackMediaItem. This type of MediaItem doesn't go cross-process, and it seems like there would never be a use case where an app would need to generate one locally. If an app needs to provide data from a custom source, it should hook into ExoPlayer's way of doing this (i.e., use a UriMediaItem with a custom scheme, and inject a custom DataSource that can handle this scheme). PiperOrigin-RevId: 326914465 |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||
| README.md | ||
ExoPlayer Media2 extension
The Media2 extension provides builders for SessionPlayer and MediaSession.SessionCallback in the Media2 library.
Compared to MediaSessionConnector that uses MediaSessionCompat, this provides finer grained control for incoming calls, so you can selectively allow/reject commands per controller.
Getting the extension
The easiest way to use the extension is to add it as a gradle dependency:
implementation 'com.google.android.exoplayer:extension-media2:2.X.X'
where 2.X.X is the version, which must match the version of the ExoPlayer
library being used.
Alternatively, you can clone the ExoPlayer repository and depend on the module locally. Instructions for doing this can be found in ExoPlayer's top level README.
Using the extension
Using SessionPlayerConnector
SessionPlayerConnector is a SessionPlayer implementation wrapping a given Player.
You can use a SessionPlayer instance to build a MediaSession, or to set the player
associated with a VideoView or MediaControlView
Using SessionCallbackBuilder
SessionCallbackBuilder lets you build a MediaSession.SessionCallback instance given its
collaborators. You can use a MediaSession.SessionCallback to build a MediaSession.
Links
- Javadoc: Classes matching
com.google.android.exoplayer2.ext.media2.*belong to this module.