`ImaAdsLoader` only loads ad media URLs once playback of the preceding ad (if any) has started, and this behavior is likely to be similar for other ad loader implementations due to limits on how long before an ad plays it is meant to be loaded. This is problematic for very short ads followed by an ad because the ad will load to the end but load control may not allow playback to start due to the total buffered duration being low. Fix this by allowing playback to start regardless of load control if we are waiting for an ad media period to prepare. An alternative fix would be to fake the ad progress in the `ImaAdsLoader` to trigger loading the next ad, but this would only allow one ad to load ahead (so the problem would remain for two short ads in a row followed by another ad). Issue: #8492 PiperOrigin-RevId: 353600088 |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| .idea | ||
| demos | ||
| extensions | ||
| gradle/wrapper | ||
| library | ||
| playbacktests | ||
| robolectricutils | ||
| testdata | ||
| testutils | ||
| .gitignore | ||
| .hgignore | ||
| build.gradle | ||
| common_library_config.gradle | ||
| constants.gradle | ||
| CONTRIBUTING.md | ||
| core_settings.gradle | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| javadoc_combined.gradle | ||
| javadoc_library.gradle | ||
| javadoc_util.gradle | ||
| LICENSE | ||
| publish.gradle | ||
| README.md | ||
| RELEASENOTES.md | ||
| settings.gradle | ||
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-v2branch. Pull requests should normally be made to this branch. - The
release-v2branch 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.