No description
Find a file
olly 3032252fde Use a single message for setting video renderer outputs
Previously, we had separate MSG_SET_SURFACE and
MSG_SET_VIDEO_DECODER_OUTPUT_BUFFER_RENDERER messages for
setting different types of supported output. Use of these
constants to switch between outputs during use of a player
was confusing because not all video renderers support both
message types.

To switch from VideoDecoderOutputBufferRenderer to a Surface,
it was sufficient just to send MSG_SET_SURFACE, since all
video renderers support this and clear any other output that
might be set. Conversely, to switch in the opposite direction,
just sending a MSG_SET_VIDEO_DECODER_OUTPUT_BUFFER_RENDERER was
not sufficient, because not all video renderers handle this
message to clear any previous output. Hence it was necessary to
explicitly clear a previously set surface using a separate
MSG_SET_SURFACE message. Passing two messages to switch the
output may prevent renderers from implementing the output switch
efficiently.

This change passes all outputs using a single message type, and
requires that all renderers treat unsupported outputs as though
null were passed (i.e., they clear any existing output). There
are some other miscellaneous improvements:

1. Non-surface outputs are now passed to onRenderedFirstFrame.
   This fixes a bug in SimpleExoPlayer's onRenderedFirstFrame,
   where previously it could not correctly equality check the
   output corresponding to the event to its current output in
   the VideoDecoderOutputBufferRenderer case.
2. Fix SimpleExoPlayer to report surface size changes for the
   VideoDecoderOutputBufferRenderer case. Even though the
   surface is rendered to indirectly in this case, we can still
   query (and listen to changes to) the surface's size.

PiperOrigin-RevId: 368215850
2021-04-13 18:01:28 +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 Merge pull request #8749 from romanofranz:patch-1 2021-03-24 18:07:35 +00:00
extensions Use MediaItem.DEFAULT_MEDIA_ID as default media ID 2021-04-13 14:59:40 +01:00
gradle/wrapper Rollback of 91b595bd27 2021-02-01 18:09:55 +00:00
library Use a single message for setting video renderer outputs 2021-04-13 18:01:28 +01:00
playbacktests Reduce the diff between different versions of GTS tests 2021-04-09 13:18:37 +01:00
robolectricutils Use Metadata.Entry.toString in PlaybackOutput test logging if possible 2021-04-01 16:05:44 +01:00
testdata Parse DASH forced_subtitle role 2021-04-13 18:01:20 +01:00
testutils Use a single message for setting video renderer outputs 2021-04-13 18:01:28 +01:00
.gitignore Add jacoco.exec files to .gitignore 2021-02-23 16:53:06 +00:00
.hgignore Remove obsolete cronet file references 2021-04-13 14:58:57 +01:00
build.gradle Add back jcenter() to repositories 2021-04-01 16:06:26 +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 Implement Bundleable for Timeline 2021-03-12 10:53:41 +00:00
CONTRIBUTING.md Clarify contribution branch 2018-11-23 17:41:06 +00:00
core_settings.gradle Remove deprecated extension-jobdispatcher module 2021-02-09 13:59:32 +00:00
gradle.properties Upgrade gradle plugin to 3.6.0 2020-03-10 10:19:11 +00: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 Add Guava dependency to ExoPlayer 2020-05-21 17:08:33 +01:00
javadoc_library.gradle Include aidl output directory to generate javadoc 2021-04-12 15:38:59 +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 Update instructions for GMaven releasing 2021-04-01 16:05:53 +01:00
RELEASENOTES.md Parse DASH forced_subtitle role 2021-04-13 18:01:20 +01:00
settings.gradle Add GL demo app 2020-02-11 17:08:53 +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.

Note: old versions of ExoPlayer are available via JCenter. To use them, you need to add jcenter() to your project's root build.gradle repositories block.

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

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