No description
Find a file
andrewlewis 05d3652443 Increase GL release timeout to 500 ms
Based on 1000 test runs an emulator, with the current timeout releasing
fails (even with no custom effects) about one percent of the time.
Releasing normally completes in about 30 ms but occasionally
`eglTerminate` took up to 200 ms (and even releasing an effect
took up to 80 ms in one case).

With the new timeout of 500 ms, we still catch stuck effects reasonably
quickly but the number of flaky test failures should be less than one in
ten thousand.

PiperOrigin-RevId: 512690715
2023-03-01 17:34:49 +00:00
.github/ISSUE_TEMPLATE Version bump for ExoPlayer 2.18.3 & media3-1.0.0-rc01 2023-02-14 13:49:22 +00:00
.idea Disable automatic imports for inner classes 2018-07-26 18:27:46 +01:00
demos Add missing variant to package transformations 2023-02-24 11:36:43 +00:00
docs Indicate that SCTE-35 metadata in not supported with HLS 2023-02-24 10:00:05 +00:00
extensions Map PLAYER_STATE_LOADING to STATE_BUFFERING 2023-02-24 09:18:11 +00:00
gradle/wrapper Update the Gradle Wrapper and Android Gradle Plugin 2022-05-30 20:42:51 +00:00
library Increase GL release timeout to 500 ms 2023-03-01 17:34:49 +00:00
playbacktests Fix instrumentation tests not working via Gradle 2022-10-19 22:54:45 +00:00
robolectricutils Rollback of c566b77449 2022-12-21 16:36:23 +00:00
testdata Add Muxer end to end tests 2023-02-27 19:04:32 +00:00
testutils Add FakeMultiPeriodLiveTimeline and test case 2023-03-01 17:30:52 +00:00
.gitignore Add JSyn library build instructions for the MIDI module 2022-10-19 17:31:44 +00:00
build.gradle Update the Gradle Wrapper and Android Gradle Plugin 2022-05-30 20:42:51 +00:00
common_library_config.gradle Enfore minCompileSdk version when depending on ExoPlayer/Media3 libs 2022-11-01 16:22:55 +00:00
constants.gradle Version bump for ExoPlayer 2.18.3 & media3-1.0.0-rc01 2023-02-14 13:49:22 +00:00
CONTRIBUTING.md Tighten the wording for sending a pull request. 2022-10-31 16:47:57 +00:00
core_settings.gradle Map lib-effect from androidx to exoplayer2 2022-10-20 03:15:38 +00:00
gradle.properties Update Gradle jetifier config to use non-deprecated option 2021-07-09 09:07:03 +01:00
gradlew Update the gradle wrapper scripts 2022-03-01 09:39:29 +00:00
gradlew.bat Update the gradle wrapper scripts 2022-03-01 09:39:29 +00:00
javadoc_combined.gradle Remove @hide javadoc annotation from ExoPlayer GitHub 2022-11-21 15:12:52 +00: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
media3-migration.sh Update migration script 2023-02-17 14:18:23 +00:00
missing_aar_type_workaround.gradle Wrap expression in paranthesis 2022-01-28 09:40:37 +00:00
publish.gradle Add workaround for missing <type>aar</type> tags in POM 2022-01-04 12:37:22 +00:00
README.md Remove unecessary git checkout command from README 2022-03-01 09:53:25 +00:00
RELEASENOTES.md Update release notes for ExoPlayer 2.18.3 2023-02-13 17:15:42 +00:00
SECURITY.md Update security mailing list 2021-11-05 11:44:08 +00:00
settings.gradle Disable publishing block when media3 included in another build. 2022-11-08 14:17:43 +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 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'

When depending on individual modules they must all be the same version.

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:

git clone https://github.com/google/ExoPlayer.git
cd ExoPlayer

Next, add the following to your project's settings.gradle file, replacing path/to/exoplayer with the path to your local copy:

gradle.ext.exoplayerModulePrefix = 'exoplayer-'
apply from: file("path/to/exoplayer/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.