No description
Find a file
olly 7edcc89421 Fix 1 ErrorProneStyle finding:
* Constructors and methods with the same name should appear sequentially with no other code in between, even when modifiers such as static or private differ between the methods. Please re-order or re-name methods.
  (see http://go/bugpattern/UngroupedOverloads)

This CL looks good? Just LGTM and Approve it!
This CL doesn’t look good? This is what you can do:
* Suggest a fix on the CL (go/how-to-suggest-fix).
* Revert this CL, by replying "REVERT: <provide reason>"
* File a bug under go/error-prone-bug for category ErrorProneStyle if the change looks generally problematic.
* Revert this CL and not get a CL that cleans up these paths in the future by
replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
opt out the respective paths in your CL Robot configuration instead:
go/clrobot-opt-out.

This CL was generated by CL Robot - a tool that cleans up code findings
(go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/java/com/google/android/libraries/media/METADATA which is reachable following include_presubmits from //depot/google3/third_party/java_src/android_libs/media/METADATA.
Anything wrong with the signup? File a bug at go/clrobot-bug.

#codehealth

PiperOrigin-RevId: 384877648
2021-07-15 13:22:18 +01:00
.github/ISSUE_TEMPLATE Make issue templates shorter 2020-12-14 10:14:03 +00:00
.idea Disable automatic imports for inner classes 2018-07-26 18:27:46 +01:00
demos Bump dependency versions 2021-06-30 13:53:01 +01:00
docs Use the content URI as well as mediaId for the auto-generated ad ID 2021-07-09 08:52:51 +01:00
extensions Rename previous/next to seekToPrevious/NextWindow in Player 2021-07-14 12:17:15 +01:00
gradle/wrapper Bump dependency versions 2021-06-30 13:53:01 +01:00
library Fix 1 ErrorProneStyle finding: 2021-07-15 13:22:18 +01:00
playbacktests Correctly remove package-info.java from empty packages 2021-05-13 12:09:17 +01:00
robolectricutils Remove @DoNotInstrument from test classes 2021-07-09 08:58:38 +01:00
testdata Signal container MIME type for JPEGs 2021-06-30 13:19:00 +01:00
testutils Move TYPE definition out from DataSourceException. 2021-07-13 10:03:01 +01:00
.gitignore Add jacoco.exec files to .gitignore 2021-02-23 16:53:06 +00:00
build.gradle Re-add jcenter() for now 2021-06-03 20:08:06 +01:00
common_library_config.gradle Update Robolectric dependency from 4.5-SNAPSHOT to 4.5-alpha-3 2020-12-17 11:25:54 +00:00
constants.gradle Add comments to constants.gradle about 'external' version limitations 2021-07-13 09:55:25 +01:00
CONTRIBUTING.md Clarify contribution branch 2018-11-23 17:41:06 +00:00
core_settings.gradle Gradle cleanup #3 2021-05-21 12:04:15 +01:00
gradle.properties Update Gradle jetifier config to use non-deprecated option 2021-07-09 09:07:03 +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
javadoc_combined.gradle Fix search links in generated Javadoc 2021-05-12 13:55:08 +01:00
javadoc_library.gradle Fix search links in generated Javadoc 2021-05-12 13:55:08 +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 Update instructions for GMaven releasing 2021-04-01 16:05:53 +01:00
README.md Align README and helloworld documentation 2021-06-03 13:56:56 +01:00
RELEASENOTES.md Implement a DefaultMediaDescriptionAdapter that uses MediaMetadata. 2021-07-14 21:16:20 +01:00
SECURITY.md Add security policy 2021-06-03 20:00:49 +01:00
settings.gradle Gradle cleanup #3 2021-05-21 12:04:15 +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 the Google Maven repository. It's also possible to clone the repository and depend on the modules locally.

From the Google Maven repository

1. Add ExoPlayer module dependencies

The easiest way to get started using ExoPlayer is to add it as a gradle 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 only 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 ExoPlayer 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-rtsp: Support for RTSP content.
  • exoplayer-smoothstreaming: Support for SmoothStreaming content.
  • exoplayer-transformer: Media transformation functionality.
  • exoplayer-ui: UI components and resources for use with ExoPlayer.

In addition to library modules, ExoPlayer has extension modules that depend on external libraries to provide additional functionality. Some extensions are available from the Maven repository, 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 can be found on the Google Maven ExoPlayer page.

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

3. Enable multidex

If your Gradle minSdkVersion is 20 or lower, you should enable multidex in order to prevent build errors.

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