No description
Find a file
olly 7fcd6b6d65 Minimal fix for non-default cenc name prefixes in DASH manifests
For now, just allow any prefix (and don't check the namespace).
Checking the namespace requires turning on the XmlPullParser
namespace awareness feature, but this can only be done before
parsing, and I think requires us to specify the namespace when
querying other attributes. This would also risk breaking services
who currently don't set namespaces correctly.

It's possible we'll run into similar issues with the few other
tags (e.g. mspr:pro). We should revisit enabling namespace
awareness if/when we see this.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=207526883
2018-08-06 13:25:33 +01:00
.idea Disable automatic imports for inner classes 2018-07-26 18:27:46 +01:00
demos Add MetadataRetriever demo. 2018-08-06 11:29:27 +01:00
extensions Upgrade IMA dependency 2018-08-06 11:37:15 +01:00
gradle/wrapper Update Gradle version from 4.1 to 4.4 2018-03-28 01:00:17 +01:00
library Minimal fix for non-default cenc name prefixes in DASH manifests 2018-08-06 13:25:33 +01:00
playbacktests Add GTS test that enumerates decoders 2018-08-06 11:35:48 +01:00
testutils Add supports for Seeking in ADTS format using a constant bitrate seekmap. 2018-08-06 11:33:06 +01:00
testutils_robolectric [third_party] Avoid saving Robolectric shadow instances; instead, save the real framework object, and get its shadow when needed using Shadows.shadowOf(). Call Android framework methods directly on the framework object instead of its shadow whenever possible. 2018-08-06 11:21:13 +01:00
.gitignore add a PlayerNotificationManager to post media style notifications. 2018-03-12 15:12:09 +00:00
.hgignore Bump to 2.5.4 2017-10-19 18:10:27 +01:00
build.gradle Update build tools for Android Studio 3.1 2018-03-29 13:49:03 +01:00
constants.gradle Update release notes + bump version 2018-07-23 15:57:51 +01:00
CONTRIBUTING.md Fix broken documentation 2016-08-31 15:25:25 +01:00
core_settings.gradle Move extension tests to Robolectric. 2018-02-27 11:03:50 +00: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 Update issue template to use "Issue #1234" as subject for emails. 2018-03-02 09:23:09 +00:00
javadoc_combined.gradle Don't rely on rootDir for Javadoc gradle files 2018-04-03 15:39:02 +01:00
javadoc_library.gradle Don't rely on rootDir for Javadoc gradle files 2018-04-03 15:39:02 +01:00
javadoc_util.gradle Improve Javadoc postprocessing 2 2018-03-29 21:34:42 +01:00
LICENSE Initial drop. 1.0.10. 2014-06-16 12:56:04 +01:00
publish.gradle Update build tools for Android Studio 3.1 2018-03-29 13:49:03 +01:00
README.md Restore equivalence 2018-02-27 13:57:18 +00:00
RELEASENOTES.md Fix freezing playing multi-period DASH with EventStreams 2018-08-06 11:38:33 +01:00
settings.gradle Remove demo-retriever from settings.gradle 2018-08-06 11:34:21 +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 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. 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:

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.