
*** Reason for rollback *** Referential equality was probably the right thing to do, since using .equals breaks track selection in the case that a source exposes two or more tracks whose formats are equal. We should fix the way overrides work instead. *** Original change description *** Fix multi-period transitions with track selection overrides An override applies across periods provided they expose the same track groups according to .equals, but the formats in the override are then compared against the period's formats according to ==. Use .equals consistently to fix. *** ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=130083840
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 to help you get started.
- The class reference documents the ExoPlayer library classes.
- The release notes document the major changes in each release.
Using ExoPlayer
Via jCenter
The easiest way to get started using ExoPlayer is by including the following in
your project's build.gradle
file:
compile 'com.google.android.exoplayer:exoplayer:rX.X.X'
where rX.X.X
is the your preferred version. For the latest version, see the
project's Releases. For more details, see the project on Bintray.
As source
ExoPlayer can also be built from source using Gradle. You can include it as a dependent project like so:
// settings.gradle
include ':app', ':..:ExoPlayer:library'
// app/build.gradle
dependencies {
compile project(':..:ExoPlayer:library')
}
As a jar
If you want to use ExoPlayer as a jar, run:
./gradlew jarRelease
and copy library.jar
to the libs folder of your new project.
Developing ExoPlayer
Project branches
- The project has
dev-vX
andrelease-vX
branches, whereX
is the major version number. - Most development work happens on the
dev-vX
branch with the highest major version number. Pull requests should normally be made to this branch. - Bug fixes may be submitted to older
dev-vX
branches. When doing this, the same (or an equivalent) fix should also be submitted to all subsequentdev-vX
branches. - A
release-vX
branch holds the most recent stable release for major versionX
.
Using Android Studio
To develop ExoPlayer using Android Studio, simply open the ExoPlayer project in the root directory of the repository.