No description
Find a file
tonihei 2cbf0ef0ab Move playback state, isLoading, and track selector result to PlaybackInfo.
This is a no-op change replacing the local variables in ExoPlayerImplInternal
with the new ones in PlaybackInfo.

***
Use playbackState, isLoading and trackSelectorResult from playbackInfo in ExoPlayerImpl.

***
Move duplicated listener notification in ExoPlayerImpl to new method.

Also split reset method in one parts which creates the new playback info
and one part which notifies the listeners. The increment of the pending
operation counter needs to happen in between.

***
Use only one pending operation counter in ExoPlayerImpl.

This also allows to move onSeekProcessed into the notification chain.

***
Replace playback info changing messages to ExoPlayerImpl by single message type.

As they are all handled in the same way, they can be summarized to one message.

***
Only send playback info change notifications once per playback thread message.

This ensures that all concurrent changes actually reach ExoPlayerImpl concurrently.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=178907165
2017-12-15 12:00:16 +00:00
demos Support non-extractor ads in AdsMediaSource and demo apps 2017-12-12 19:17:58 +00:00
extensions Check if native libraries are available in tests. 2017-12-15 11:57:27 +00:00
gradle/wrapper Upgrade gradle plugin / wrapper 2017-09-05 16:47:38 +01:00
library Move playback state, isLoading, and track selector result to PlaybackInfo. 2017-12-15 12:00:16 +00:00
playbacktests Make DashMediaSource.Builder a factory for DashMediaSources 2017-12-12 19:08:25 +00:00
testutils Fix seek/prepare/stop acks when exception is thrown. 2017-12-13 12:53:39 +00:00
.gitignore Add tv module for USB tuner support + demo app 2017-09-15 23:30:41 +01:00
.hgignore Bump to 2.5.4 2017-10-19 18:10:27 +01:00
build.gradle Update gradle wrapper 2017-11-23 15:06:12 +00:00
constants.gradle Bump target API level to 27 2017-11-21 13:03:28 +00:00
CONTRIBUTING.md Fix broken documentation 2016-08-31 15:25:25 +01:00
core_settings.gradle Allow easier ExoPlayer/Cast integration 2017-08-17 22:56:52 +01:00
gradle.properties Tweak project structure 2016-08-08 11:53:22 +01: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
ISSUE_TEMPLATE Allow late HLS sample queue building 2017-12-12 18:30:00 +00:00
javadoc_combined.gradle Generate combined Javadoc 2017-03-22 19:11:28 +00:00
javadoc_library.gradle Generate combined Javadoc 2017-03-22 19:11:28 +00:00
LICENSE Initial drop. 1.0.10. 2014-06-16 12:56:04 +01:00
publish.gradle Make it easier to use ExoPlayer modules in other projects 2017-06-28 22:26:05 +01:00
README.md Update version strings 2017-11-27 13:51:34 +00:00
RELEASENOTES.md Update release notes for current 2.6.1 feature set 2017-12-13 12:55:25 +00:00
settings.gradle Moved Exo IMA Demo to ExoPlayer. 2017-10-27 15:57:28 +01: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

The easiest way to get started using ExoPlayer is to add it as a gradle dependency. You need to make sure you have the JCenter and Google repositories included in the build.gradle file in the root of your project:

repositories {
    jcenter()
    google()
}

Next add a gradle compile dependency to the build.gradle file of your app module. The following will add a dependency to the full library:

compile 'com.google.android.exoplayer:exoplayer:2.X.X'

where 2.X.X is your preferred version. Alternatively, 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:

compile 'com.google.android.exoplayer:exoplayer-core:2.X.X'
compile 'com.google.android.exoplayer:exoplayer-dash:2.X.X'
compile '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 manaully. 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:

compile project(':exoplayer-library-core')
compile project(':exoplayer-library-dash')
compile 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.