Skip to content
An extensible media player for Android
Java C++ Other
Branch: release-v2
Clone or download

Latest commit

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Remove the content_not_playing issue template Oct 8, 2019
.idea Disable automatic imports for inner classes Aug 1, 2018
demos Update misc dependencies Apr 8, 2020
extensions Update misc dependencies Apr 8, 2020
gradle/wrapper Update Gradle version Oct 13, 2019
library Clean up playWhenReady Apr 8, 2020
playbacktests Add IntDefs for renderer capabilities. Dec 6, 2019
testutils Add tests to validate FLAC decoder output Jan 17, 2020
.gitignore Add missing AV1 extension path to .gitignore Feb 1, 2020
.hgignore Add av1 extension to version control ignores Oct 10, 2019
CONTRIBUTING.md Clarify contribution branch Nov 27, 2018
LICENSE Initial drop. 1.0.10. Jun 16, 2014
README.md Add a `cd` command to ExoPlayer clone instructions Oct 13, 2019
RELEASENOTES.md Revert release note indentation change Apr 8, 2020
build.gradle Fix release notes. Toggle publish to false. Oct 14, 2019
constants.gradle Bump version to 2.11.4 Mar 30, 2020
core_settings.gradle Remove copybara exclusions and add extension to the demo app Oct 10, 2019
gradle.properties Increase gradle heap size May 15, 2019
gradlew Initial drop. 1.0.10. Jun 16, 2014
gradlew.bat Cleanup following #884 Oct 27, 2015
javadoc_combined.gradle Make javadoc links point to Android docs for java.* classes Apr 1, 2020
javadoc_library.gradle Make javadoc links point to Android docs for java.* classes Apr 1, 2020
javadoc_util.gradle Make javadoc links point to Android docs for java.* classes Apr 1, 2020
publish.gradle Add missing file header Jul 14, 2019
settings.gradle Add GL demo app Feb 13, 2020

README.md

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

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.

You can’t perform that action at this time.