No description
Find a file
olly d88f5f47e6 Turn CacheUtil into stateful CacheWriter
- The new CacheWriter is simplified somewhat
- Blocking on PriorityTaskManager.proceed is moved out of
  CacheWriter and into the Downloader tasks. This is because
  we want to shift only the caching parts of the Downloaders
  onto their Executors, whilst keeping the blocking parts on
  the main Downloader threads. Else we can end up "using"
  the Executor threads indefinitely whilst they're blocked.

Issue: #5978
PiperOrigin-RevId: 313222923
2020-05-27 19:00:53 +01:00
.github/ISSUE_TEMPLATE Remove the content_not_playing issue template 2019-10-08 20:54:59 +01:00
.idea Disable automatic imports for inner classes 2018-07-26 18:27:46 +01:00
demos Enable multidex for demos 2020-05-27 18:59:43 +01:00
extensions Make constants more readable with _ separator 2020-05-27 19:00:36 +01:00
gradle/wrapper Update Gradle plugins. 2020-05-01 19:48:32 +01:00
library Turn CacheUtil into stateful CacheWriter 2020-05-27 19:00:53 +01:00
playbacktests Add Guava dependency to ExoPlayer 2020-05-21 17:08:33 +01:00
testdata Extend WebVTT ruby-position support to include <rt> tags 2020-05-18 22:38:45 +01:00
testutils Make constants more readable with _ separator 2020-05-27 19:00:36 +01:00
.gitignore Add missing AV1 extension path to .gitignore 2020-01-30 19:31:15 +00:00
.hgignore Add jacoco.exec to .hgignore 2020-03-25 13:04:14 +00:00
build.gradle Publish MediaCodec-based renderer tests 2020-05-18 16:13:34 +01:00
constants.gradle Enable multidex for demos 2020-05-27 18:59:43 +01:00
CONTRIBUTING.md Clarify contribution branch 2018-11-23 17:41:06 +00:00
core_settings.gradle Create testdata module 2020-02-11 17:08:45 +00:00
gradle.properties Upgrade gradle plugin to 3.6.0 2020-03-10 10:19:11 +00:00
gradlew Initial drop. 1.0.10. 2014-06-16 12:56:04 +01:00
gradlew.bat Cleanup following #884 2015-10-27 21:03:16 +00:00
javadoc_combined.gradle Add Guava dependency to ExoPlayer 2020-05-21 17:08:33 +01:00
javadoc_library.gradle Add Guava dependency to ExoPlayer 2020-05-21 17:08:33 +01:00
javadoc_util.gradle Make javadoc links point to Android docs for java.* classes 2020-04-01 22:38:01 +01:00
LICENSE Initial drop. 1.0.10. 2014-06-16 12:56:04 +01:00
publish.gradle Add missing file header 2019-07-14 16:23:39 +01:00
README.md Add a cd command to ExoPlayer clone instructions 2019-10-02 21:25:23 +01:00
RELEASENOTES.md Update TrackSelectionDialogBuilder to use androidx compat Dialog. 2020-05-27 18:59:51 +01:00
settings.gradle Add GL demo app 2020-02-11 17:08:53 +00:00

ExoPlayer

ExoPlayer is an application level media player for Android. It provides an alternative to Androids MediaPlayer API for playing audio and video both locally and over the Internet. ExoPlayer supports features not currently supported by Androids 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.