An extensible media player for Android
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.idea Disable automatic imports for inner classes Aug 1, 2018
demos Update content url for IMA demo app Nov 27, 2018
extensions Specify a version for the FFmpeg dependency Nov 30, 2018
gradle/wrapper Update Gradle version from 4.1 to 4.4 Mar 29, 2018
library Prevent Cea608Decoder from generating Subtitles with null Cues list. Dec 1, 2018
playbacktests Add ACCESS_NETWORK_STATE permission for MH tests Oct 24, 2018
testutils Add test action to wait for an isLoading change. Oct 31, 2018
testutils_robolectric Support removal of ranges from ShuffleOrders Nov 27, 2018
.gitignore add a PlayerNotificationManager to post media style notifications. Mar 12, 2018
.hgignore Bump to 2.5.4 Oct 19, 2017
CONTRIBUTING.md Clarify contribution branch Nov 27, 2018
ISSUE_TEMPLATE Update issue template to use "Issue #1234" as subject for emails. Mar 2, 2018
LICENSE Initial drop. 1.0.10. Jun 16, 2014
README.md Tweak dev guide / readme Nov 6, 2018
RELEASENOTES.md Fix clearkey DRM UUID passed to MediaCrypto Nov 30, 2018
build.gradle Swap google() and jcenter() in docs and gradle config. Oct 24, 2018
constants.gradle Bump for 2.9.2 Nov 28, 2018
core_settings.gradle Use gradle dependencies for Cronet extension Aug 13, 2018
gradle.properties Tweak project structure Aug 8, 2016
gradlew Initial drop. 1.0.10. Jun 16, 2014
gradlew.bat Cleanup following #884 Oct 27, 2015
javadoc_combined.gradle Fix a bunch of misc analysis warnings Aug 24, 2018
javadoc_library.gradle Don't rely on rootDir for Javadoc gradle files Apr 3, 2018
javadoc_util.gradle Improve Javadoc postprocessing 2 Mar 29, 2018
publish.gradle Update build tools for Android Studio 3.1 Mar 29, 2018
settings.gradle Update moe equivalence Aug 6, 2018

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

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()
}

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. 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
}

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.

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
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.