c2ac33af1b
PlayerWrapper throws Exception if getters is called in the STATE_IDLE. In that case, log may print 50+ lines of stack traces. It's verbose and can be considered as serious issue. This CL include folloing changes - Change to use ExoPlayer's log class - Adjust log level, because it would be consumed by caller - Leave log when the debug flag is turned on. Another CL will remove exceptions between PlayerWrapper and and SessionPlayerConnector, not to use Exception for ordinary control flow as the Effective Java suggests. PiperOrigin-RevId: 326614559 |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||
| proguard-rules.txt | ||
| 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.