
We currently have the following logic to update renderers during period transitions: 1. Wait for the currently reading period to finish reading all its streams. a. Advance reading period. b. Set all streams that can't be replaced to final. c. If streams can be replaced, replace them now. 2. Wait until playback position reaches the transition point a. Disable all unneeded renderers (or those that need re-enabling). b. Advance playing period. c. Enable all new renderers (i.e. all except the ones where we replaced streams directly in step 1c. This logic causes delays because steps 2a and 2c can easily happen before 2b. Doing this allows a smooth transition for cases where renderers change or where they need to be re-enabled. The new order after this change is: 1. Wait for currently reading period to finish reading. a. Advance reading period. b. Set all streams that can't be replaced to final. 2. Update reading renderers iteratively. a. If streams can be replaced, replace them asap. b. If renderes need to be disabled, do so as soon as the respective renderer ended. c. Once step b is fully finished, enable or re-enable all new renderers. 3. Wait unril playback position reaches the transition point AND all tasks in step 2 are done (i.e. all renderers are set up for the playing period). a. Advance playing period. As a nice side effect, decoder enabled and disabled events are now always reported for the reading period, which is more consistent with other renderer callbacks. PiperOrigin-RevId: 300526983
ExoPlayer
ExoPlayer is an application level media player for Android. It provides an alternative to Android’s MediaPlayer API for playing audio and video both locally and over the Internet. ExoPlayer supports features not currently supported by Android’s MediaPlayer API, including DASH and SmoothStreaming adaptive playbacks. Unlike the MediaPlayer API, ExoPlayer is easy to customize and extend, and can be updated through Play Store application updates.
Documentation
- The developer guide provides a wealth of information.
- The class reference documents ExoPlayer classes.
- The release notes document the major changes in each release.
- Follow our developer blog to keep up to date with the latest ExoPlayer developments!
Using ExoPlayer
ExoPlayer modules can be obtained from JCenter. It's also possible to clone the repository and depend on the modules locally.
From JCenter
1. Add repositories
The easiest way to get started using ExoPlayer is to add it as a gradle
dependency. You need to make sure you have the Google and JCenter repositories
included in the build.gradle
file in the root of your project:
repositories {
google()
jcenter()
}
2. Add ExoPlayer module dependencies
Next add a dependency in the build.gradle
file of your app module. The
following will add a dependency to the full library:
implementation 'com.google.android.exoplayer:exoplayer:2.X.X'
where 2.X.X
is your preferred version.
As an alternative to the full library, you can depend on only the library modules that you actually need. For example the following will add dependencies on the Core, DASH and UI library modules, as might be required for an app that plays DASH content:
implementation 'com.google.android.exoplayer:exoplayer-core:2.X.X'
implementation 'com.google.android.exoplayer:exoplayer-dash:2.X.X'
implementation 'com.google.android.exoplayer:exoplayer-ui:2.X.X'
The available library modules are listed below. Adding a dependency to the full library is equivalent to adding dependencies on all of the library modules individually.
exoplayer-core
: Core functionality (required).exoplayer-dash
: Support for DASH content.exoplayer-hls
: Support for HLS content.exoplayer-smoothstreaming
: Support for SmoothStreaming content.exoplayer-ui
: UI components and resources for use with ExoPlayer.
In addition to library modules, ExoPlayer has multiple extension modules that depend on external libraries to provide additional functionality. Some extensions are available from JCenter, whereas others must be built manually. Browse the extensions directory and their individual READMEs for details.
More information on the library and extension modules that are available from JCenter can be found on Bintray.
3. Turn on Java 8 support
If not enabled already, you also need to turn on Java 8 support in all
build.gradle
files depending on ExoPlayer, by adding the following to the
android
section:
compileOptions {
targetCompatibility JavaVersion.VERSION_1_8
}
Locally
Cloning the repository and depending on the modules locally is required when using some ExoPlayer extension modules. It's also a suitable approach if you want to make local changes to ExoPlayer, or if you want to use a development branch.
First, clone the repository into a local directory and checkout the desired branch:
git clone https://github.com/google/ExoPlayer.git
cd ExoPlayer
git checkout release-v2
Next, add the following to your project's settings.gradle
file, replacing
path/to/exoplayer
with the path to your local copy:
gradle.ext.exoplayerRoot = 'path/to/exoplayer'
gradle.ext.exoplayerModulePrefix = 'exoplayer-'
apply from: new File(gradle.ext.exoplayerRoot, 'core_settings.gradle')
You should now see the ExoPlayer modules appear as part of your project. You can depend on them as you would on any other local module, for example:
implementation project(':exoplayer-library-core')
implementation project(':exoplayer-library-dash')
implementation project(':exoplayer-library-ui')
Developing ExoPlayer
Project branches
- Development work happens on the
dev-v2
branch. Pull requests should normally be made to this branch. - The
release-v2
branch holds the most recent release.
Using Android Studio
To develop ExoPlayer using Android Studio, simply open the ExoPlayer project in the root directory of the repository.